On Fri, Aug 29, 2008 at 3:31 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > On Friday, 29 of August 2008, Yinghai Lu wrote: >> On Fri, Aug 29, 2008 at 12:57 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: >> > On Friday, 29 of August 2008, Rafael J. Wysocki wrote: >> >> On Friday, 29 of August 2008, Linus Torvalds wrote: >> >> > >> >> > Another week (my weeks do seem to be eight days, don't they? Very odd), >> >> > another -rc. >> >> > >> >> > The dirstat pretty much says it all: >> >> > >> >> > 43.0% arch/arm/configs/ >> >> > 43.9% arch/arm/ >> >> > 25.5% arch/powerpc/configs/ >> >> > 26.8% arch/powerpc/ >> >> > 73.9% arch/ >> >> > 4.4% drivers/usb/musb/ >> >> > 5.4% drivers/usb/ >> >> > 4.0% drivers/watchdog/ >> >> > 16.0% drivers/ >> >> > 3.5% fs/ >> >> > >> >> > yeah, the bulk of it is all config updates, and with arm and powerpc >> >> > leading the pack. >> >> >> >> Doesn't boot on my quad core test box, apparently because of an AHCI failure. >> >> >> >> Bisecting ... >> > >> > Bisection turned up commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd as the culprit: >> > >> > commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd >> > Author: Yinghai Lu <yhlu.kernel@xxxxxxxxx> >> > Date: Mon Aug 25 00:56:08 2008 -0700 >> > >> > x86: fix HPET regression in 2.6.26 versus 2.6.25, check hpet against BAR, v3 >> > >> > Reverting this commit helps. >> > >> >> can i get whole bootlog with "debug"? > > http://www.sisk.pl/kernel/debug/mainline/2.6.27-rc5/broken.log > pci 0000:00:00.0: BAR has MMCONFIG at e0000000-ffffffff pci 0000:00:12.0: BAR 5: can't allocate resource pci 0000:00:13.0: BAR 0: can't allocate resource pci 0000:00:13.1: BAR 0: can't allocate resource pci 0000:00:13.2: BAR 0: can't allocate resource pci 0000:00:13.3: BAR 0: can't allocate resource pci 0000:00:13.4: BAR 0: can't allocate resource pci 0000:00:13.5: BAR 0: can't allocate resource pci 0000:00:14.2: BAR 0: can't allocate resource your mmconf in BAR is broken.... after forcibly insert that block all others... YH -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
