Re: 2.6.17 hangs during boot on ASUS M2NPV-VM motherboard

[Andrew Morton <akpm@osdl.org>]

On Thu, 13 Jul 2006 08:56:01 +0100
"Andy Chittenden" <AChittenden@bluearc.com> wrote:

> > On Wed, 12 Jul 2006 08:58:52 +0100
> > "Andy Chittenden" <AChittenden@bluearc.com> wrote:
> > 
> > > I tried to install the linux-image-2.6.17-1-amd64-k8-smp 
> > debian package
> > > on a ASUS M2NPV-VM motherboard based system and it hung 
> > during boot. The
> > > last message on the console was:
> > > 
> > >  io scheduler cfq registered
> > 
> > Suggest you add initcall_debug to the kernel boot command 
> > line.  That'll
> > tell us which initcall got stuck.
> 
> I was only able to scrounge 5 minutes on this system this morning.
> Here's the last few messages output with initcall_debug on:
> 
> Calling initcall .... init+0x0/0xc()
> Calling initcall .... noop_init+0x0/0xc()
> io scheduler noop registered
> Calling initcall .... as_init+0x0/0x4f()
> io scheduler anticipatory registered (default)
> Calling initcall .... deadline_init+0x0/0x4f()
> io scheduler deadline registered
> Calling initcall .... cfq_init+0x0/0xcc()
> io scheduler cfq registered
> Calling initcall .... pci_init+0x0/0x2b()
> 
> What other info can I grab? (Although I have to fit in with that
> system's production schedule so I may not be able to come back with that
> until later on today/tomorrow).

Seems one of the quirks has gone bad.  The below should tell us which one. 
You'll need to correlate it with the machine's lspci output please.


--- a/drivers/pci/pci.c~a
+++ a/drivers/pci/pci.c
@@ -925,6 +925,7 @@ static int __devinit pci_init(void)
 	struct pci_dev *dev = NULL;
 
 	while ((dev = pci_get_device(PCI_ANY_ID, PCI_ANY_ID, dev)) != NULL) {
+		printk("%s: fix up %s\n", __FUNCTION__, pci_name(dev));
 		pci_fixup_device(pci_fixup_final, dev);
 	}
 	return 0;
_

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