Messages in this thread | | | Subject | Re: CPU Lockup with 2.4.21 and 2.4.22-pre | From | Michael Troß <> | Date | 22 Jul 2003 12:24:24 +0200 |
| |
Am Mon, 2003-07-21 um 16.17 schrieb Udo A. Steinberg: > On Mon, 21 Jul 2003 16:12:26 +0200 Udo A. Steinberg (UAS) wrote: > > UAS> We have a Dual-Xeon machine with Hyperthreading which keeps locking > up hard, > UAS> so that not even Sysrq works anymore. I have captured such a lockup > using the > UAS> NMI oopser. Below you'll find the lockup fed through ksymoops. Note > that > UAS> after CPU3 locked up, CPU2 did too. But that lockup couldn't be > captured > UAS> anymore. Kernel is a monolithic 2.4.22-pre6. Problem also happened > on > UAS> plain 2.4.21. I can provide more information wrt. hardware, config > etc. > UAS> on request.
Would be really useful if you do so.
> Sorry, I used the wrong System.map. Below is the fixed decode. Looks > like > the lockup is caused by the 3rd party Compushack FDDI driver.
What makes you believe this? There is no matching code sequence like the one from your dump in the driver, to be exact: in a driver compiled with gcc 3.3 and kernel 2.4.21.
> Regards, > -Udo.
Regards, Michael
- 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/
| |