From: Ian Kent <raven@themaw.net>
To: Avi Kivity <avi@argo.co.il>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: AGPGART: unable to get memory for graphics translation table.
Date: Fri, 23 Jun 2006 09:37:10 +0800 [thread overview]
Message-ID: <1151026630.2623.1.camel@raven.themaw.net> (raw)
In-Reply-To: <449ADD47.6000809@argo.co.il>
On Thu, 2006-06-22 at 21:11 +0300, Avi Kivity wrote:
> Ian Kent wrote:
> >
> > On Thu, 2006-06-22 at 17:00 +0300, Avi Kivity wrote:
> > > Ian Kent <raven <at> themaw.net> writes:
> > >
> > > >
> > > > On Sat, 17 Jun 2006, Dave Jones wrote:
> > > >
> > > > > On Sat, Jun 17, 2006 at 01:24:58PM +0800, Ian Kent wrote:
> > > > >
> > > > > > Linux raven.themaw.net 2.6.16-1.2289_FC6xen #1 SMP Thu Jun 15
> > > 14:48:53 EDT
> > > > > ^^^
> > > > >
> > > > > I'll bet xen is to blame. Can you try it on a plain kernel.org
> > kernel?
> > > >
> > > > I tell a lie.
> > > >
> > > > Standard kernel now works.
> > > > All I noticed between the dmesg files was that the init of the
> > > agpgart is
> > > > somewhat later with the xen kernel.
> > >
> > > I'm getting this too. Were you able to resolve this somehow?
> > >
> >
> > Not yet.
> >
> I've chased it a bit, it's indeed a bug in xen-linux. May have a fix soon.
That would be great.
Ian
next prev parent reply other threads:[~2006-06-23 1:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 14:00 Avi Kivity
2006-06-22 17:34 ` Ian Kent
2006-06-22 18:11 ` Avi Kivity
2006-06-23 1:37 ` Ian Kent [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-17 3:32 Ian Kent
2006-06-17 3:46 ` Dave Jones
2006-06-17 4:02 ` Ian Kent
2006-06-17 4:46 ` Dave Jones
2006-06-17 5:18 ` Ian Kent
2006-06-17 5:24 ` Ian Kent
2006-06-17 5:43 ` Dave Jones
2006-06-17 9:05 ` Ian Kent
2006-06-17 10:29 ` Ian Kent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1151026630.2623.1.camel@raven.themaw.net \
--to=raven@themaw.net \
--cc=avi@argo.co.il \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®