> On Fri, 23 Feb 2007 13:35:50 -0000 (GMT) "Andrew" <andrew@xxxxxxxxxxx> wrote: > Hi, > > 2.6.21-rc1 fails to boot on my machine. As soon as I switch > from grub the screen turns and remains black with no sign > of Tux or any output. > > I've run a git-bisect between 2.6.20 (which works fine) and > 2.6.21-rc1 and found the first bad commit to be > #59b8175c771040afcd4ad67022b0cc80c216b866 which seems bizarre > to me since this is a mostly an ARM commit. > > I haven't tried to revert this commit because frankly I don't > know where to go from there with a multi-parent commit. > > I'm running on on a Asus A8N-VM CSM motherboard with a single > core AMD64 processor, with a nVidia GPU in the PCI-ex slot > using the standard VESA frame buffer driver. > > Relevant config's can be found here: > http://homepage.ntlworld.com/anelless/linux/2.6.21-rc1/ > and, later, > I have just discovered 2.6.21-rc1 boots with > pci=noacpi ... Presumably this regression was caused by the ACPI merge. Are you able to capture the dmesg output from the 2.6.20-rc1 boot? netconsole might be useful here, thanks. (You get added to the post-2.6.20 regression list, so you'll be hearing from us quite a lot for the next month. Sorry ;)) - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
