mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Andy Chittenden" <AChittenden@bluearc.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.17 hangs during boot on ASUS M2NPV-VM motherboard
Date: Thu, 13 Jul 2006 03:15:23 -0700	[thread overview]
Message-ID: <20060713031523.0ab0c4cb.akpm@osdl.org> (raw)
In-Reply-To: <89E85E0168AD994693B574C80EDB9C27043F5DEE@uk-email.terastack.bluearc.com>

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;
_


  reply	other threads:[~2006-07-13 10:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13  7:56 Andy Chittenden
2006-07-13 10:15 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-14 15:54 Andy Chittenden
2006-07-14 16:30 ` Andrew Morton
2006-07-14 19:37   ` David Brownell
     [not found] <AcamZU83D6YFwDlPRZGLtXEmxZel2wAJqNMg>
2006-07-13 14:58 ` Andy Chittenden
2006-08-24 15:55   ` Zhen Zhou
2006-08-24 16:04     ` Prakash Punnoor
2006-07-12  7:58 Andy Chittenden
2006-07-12  9:26 ` Andrew Morton
2006-07-12 12:47 ` James Oakley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060713031523.0ab0c4cb.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=AChittenden@bluearc.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome