Re: x86 git tree broken (bisected)

From: Rafael J. Wysocki
Date: Sun Apr 13 2008 - 19:42:00 EST


On Monday, 14 of April 2008, Yinghai Lu wrote:
> On Sun, Apr 13, 2008 at 3:10 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote:
> >
> > On Monday, 14 of April 2008, Yinghai Lu wrote:
> > > On Sun, Apr 13, 2008 at 9:12 AM, Rafael J. Wysocki <rjw@xxxxxxx> 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@albercik:~> 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

Well, unfortunately current x86.git doesn't even boot on the affected box.
It 'cannot open root device "md1" or unknown-block (0,0)' (Ingo, any ideas?).

Today I have to take some sleep, so I'll try to debug it tomorrow, unless
someone else does it earlier.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/