public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@argo.co.il>
To: Ian Kent <raven@themaw.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: AGPGART: unable to get memory for graphics translation table.
Date: Thu, 22 Jun 2006 21:11:19 +0300	[thread overview]
Message-ID: <449ADD47.6000809@argo.co.il> (raw)
In-Reply-To: <1150997663.4372.8.camel@raven.themaw.net>

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.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2006-06-22 18:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 14:00 AGPGART: unable to get memory for graphics translation table Avi Kivity
2006-06-22 17:34 ` Ian Kent
2006-06-22 18:11   ` Avi Kivity [this message]
2006-06-23  1:37     ` Ian Kent
  -- 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=449ADD47.6000809@argo.co.il \
    --to=avi@argo.co.il \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raven@themaw.net \
    /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