[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200804142221.19606.rjw@sisk.pl>
Date: Mon, 14 Apr 2008 22:21:18 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: "Yinghai Lu" <yhlu.kernel@...il.com>
Cc: "Ingo Molnar" <mingo@...e.hu>,
"Andrew Morton" <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
"Pavel Machek" <pavel@....cz>,
"Thomas Gleixner" <tglx@...utronix.de>, "H. Anvin" <hpa@...or.com>,
"Arjan van de Ven" <arjan@...radead.org>
Subject: Re: x86 git tree broken (bisected)
On Monday, 14 of April 2008, Yinghai Lu wrote:
> On Sun, Apr 13, 2008 at 5:19 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> >
> > On Monday, 14 of April 2008, Yinghai Lu wrote:
> > > On Sun, Apr 13, 2008 at 3:10 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > > >
> > > > On Monday, 14 of April 2008, Yinghai Lu wrote:
> > > > > On Sun, Apr 13, 2008 at 9:12 AM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > > > > ...
> > > > > > > can you try to apply the patch i sent to you about agp bridge order
> > > > > > > reading for buggy silicon?
> > > > > > >
> > > > > > > Please boot kernel with "debug"...
> > > > > > >
> > > > > > > I want to verify if you can get
> > > > > > >
> > > > > > > "
> > > > > > > Aperture conflicts with PCI mapping.
> > > > > > > "
> > > > > > >
> > > > > > > in your boot log...
> > > > > >
> > > > > > It's not present in there:
> > > > > >
> > > > > > rafael@...ercik:~> grep Aperture failing-with-patch-dmesg.log
> > > > > > Aperture too small (32 MB)
> > > > > > Aperture from AGP @ de000000 size 4096 MB (APSIZE 0)
> > > > > > Aperture too small (0 MB)
> > > > > > agpgart: Aperture pointing to RAM
> > > > > > agpgart: Aperture from AGP @ de000000 size 4096 MB
> > > > > > agpgart: Aperture too small (0 MB)
> > > > > >
> > > > > > Full dmesg output attached.
> > > > >
> > > > > please check attached debug patch. and check if you can change GART
> > > > > size in your BIOS setup to 64M instead of 32M
> > > >
> > > > Hm, what tree am I supposed to apply it too:
> > > > (1) current x86 git
> > > > (2) current x86 git w/ some of your previous patches (which ones in this case)
> > > > (3) failing (old) x86 git
> > > > (4) failing (old) x86 git w/ some of your previous patches (which ones in this
> > > > case)?
> > >
> > > (1) current x86.git
> >
> > Attached is dmesg output from current x86.git with debug_gart_checking.patch
> > applied.
>
> please test the final one ... ...
>
> You should get back 64M memory back.
Tested (current x86.git), dmesg output attached.
Thanks,
Rafael
View attachment "dmesg.log" of type "text/x-log" (24898 bytes)
Powered by blists - more mailing lists