* Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Tue, 5 Jun 2007 11:11:51 +0200 Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> > hm, mm1 hangs during bootup on one of my boxes:
> >
> > Calling initcall 0xc0628d39: pci_mmcfg_late_insert_resources+0x0/0x44()
> > initcall 0xc0628d39: pci_mmcfg_late_insert_resources+0x0/0x44() returned 0.
> > initcall 0xc0628d39 ran for 0 msecs:
> > pci_mmcfg_late_insert_resources+0x0/0x44()
> > Calling initcall 0xc062abd1: tcp_congestion_default+0x0/0xf()
> > initcall 0xc062abd1: tcp_congestion_default+0x0/0xf() returned 0.
> > initcall 0xc062abd1 ran for 0 msecs: tcp_congestion_default+0x0/0xf()
> >
> > it usually hangs in different places.
>
> In my experience that means that it wedged in a timer tick. Often the
> first one.
yeah. I tried !hres and !dynticks too and that doesnt make any
difference to the end result - so my guess is on the NMI watchdog
re-programming thing on K8 CPUs (running the 32-bit kernel), which is
done in every NMI tick. check_watchdog() for some reason thought there's
no NMI, and later on an NMI still arrived? Something like that.
vanilla kernel works fine.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
