On Sun, 2005-07-31 at 10:40 +1000, Dave Airlie wrote: > > 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. > > run memtest on it... you might have bad RAM.. >
Already swapped it out, but I'll try memtest. Any idea why printk_ratelimit does not work? I set it to 1000 (per the docs this should limit to 1 printk per second) and burst to 1 but I still get screenfuls of text flying by. 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/
