Skip to contentSkip to conversation

lockups with 2.4.20 (tg3? net/core/dev.c|deliver_to_old_ones)

DISCUSSION Pete Zaitcev 1 participant 1 message Feb 14, 2003 1 message not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive
Quoted 7 lines

Since sometime in December two systems we have on site using P4 HT (one Dell 2650 and one Dell 4600, both dual CPU, both ht/mce capable) have been locking up without any kernel output and without sysrq keys working (the keyboard is locked solid).
[...]
Using nmi_watchdog I've managed to get a stack track and ran ksymoops over it (attached).

Good report. To tell the truth, I know that this lockup exists, there's an RH issue-tracker item against me on this. It is different from the old "porkchop" lockup, which DaveM and Jeff Garzik fixed.

The stumbling block is that NMI oopser catches a thread which gets stuck because of the lock, but this does not explain how the lock was taken.

I think the best resolution would be an instrumentation patch which records lock takers, and prints them when the thing is forcefuly oopsed. I should come with it eventually, if someone does not beat me to it (I wish they did, actually :-)

-- Pete