On Sun, 2005-07-31 at 02:11 +0200, Alexander Nyberg wrote: > On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote: > > > I have a machine here that oopses reliably when I start X, but the > > interesting stuff scrolls away too fast, and a bunch more Oopses get > > printed ending with "Aieee, killing interrupt handler". > > > > How do I get the output to stop after the first Oops? > > > > set /proc/sys/kernel/panic_on_oops to 1 > > What version of the kernel is that? It shouldn't do recursive oopses > (of the same task) any more. >
panic_on_oops has no effect, a bunch of stuff flies past and the last thing I see is "gam_server: scheduling while atomic" then a stack trace of the core dump path then "Aiee, killing interrupt handler". I am starting to suspect the hard drive, does that sound plausible? It's as if it locks up when it hits a certain disk block. Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
