> Hmm, you state the watchdog works from time to time and the log you
> provided confirms the statement -- it reports:
> > ..TIMER: vector=49 pin1=2 pin2=0
> > activating NMI Watchdog ... done.
Yes, but I reach this message only once of 10 trials to boot. The other nine
trials I just reach
activating NMI Watchdog ...
followed by no "done" (and not followed by anything else).
> What chipset do you use (check with lspci)?
00:00.0 Host bridge: VIA Technologies, Inc. VT82C691 [Apollo PRO] (rev c4)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3 AGP]
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 40)
00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 06)
00:04.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 16)
00:04.3 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 16)
00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
40)
00:09.0 Network controller: AVM Audiovisuelles MKTG & Computer System GmbH A1
ISDN [Fritz] (rev 02)
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
00:0b.0 Multimedia audio controller: Creative Labs SB Live! EMU10000 (rev 07)
00:0b.1 Input device controller: Creative Labs SB Live! (rev 07)
01:00.0 VGA compatible controller: nVidia Corporation NV15 (Geforce2 GTS)
(rev a3)
> In any case the code should not hang there in any case -- it the watchdog
> appears stuck, it reports it and goes on. A hang almost surely means
> hardware locked up.
Yes, but why only with the 2.4.x kernels. I am using a 2.2.17 smp kernel
without problems.
Regards,
Matthias
-
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/