Skip to contentSkip to conversation

Dianogsing a hard lockup

DISCUSSION Robert Hancock 2 participants 3 messages Dec 17, 2005 – Jan 2, 2006 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 7 lines · Jan Engelhardt

Hi list,

some time after I load drivers (any, rt2500 or via ndiswrap) for a rt2500-based wlan card, the box locks up hard. Sysrq does not work, so I suppose it is during irq-disabled context. How could I find out where this happens?

Jan Engelhardt

Try nmi_watchdog=1 on the kernel command line. That may get you a stack trace for the lockup.

Signature · 3 lines
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
#2 lore raw

Hi,

Quoted 2 lines

Try nmi_watchdog=1 on the kernel command line. That may get you a stack trace for the lockup.

That does not seem to work.
APIC is enabled, but the kernel reports "No local APIC present or hardware disabled". /proc/interrupts only lists XT PICs, and the NMI counter in interrupts is also 0.

Jan Engelhardt

#3 lore raw
Quoted 9 lines

Hi,

Quoted 2 lines

Try nmi_watchdog=1 on the kernel command line. That may get you a stack trace for the lockup.

That does not seem to work.
APIC is enabled, but the kernel reports "No local APIC present or hardware disabled". /proc/interrupts only lists XT PICs, and the NMI counter in interrupts is also 0.

So, here's a potential answer to my own problem: the mainboard is crap. 0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04)
0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] (rev 23)

Jan Engelhardt