Messages in this thread | | | Date | Tue, 21 Feb 2006 10:29:49 -0500 | From | Benjamin LaHaise <> | Subject | Re: 2.4.31 hangs, no information on console or serial port |
| |
On Tue, Feb 21, 2006 at 10:23:56AM -0500, David Golombek wrote: > Any suggestions as to how we might debug this or possible causes would > be greatly appreciated.
Have you tried turning on the NMI watchdog (nmi_watchdog=1)? It should be able to kick the machine out of the locked state, as these symptoms would hint at a spinlock deadlock with interrupts disabled. Also, try to reproduce on the latest 2.4.33pre. That said, for an io intensive workload like you're running, 2.6 is much better, especially for systems using highmem.
-ben -- "Ladies and gentlemen, I'm sorry to interrupt, but the police are here and they've asked us to stop the party." Don't Email: <dont@kvack.org>. - 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/
| |