Skip to contentSkip to conversation

Simple question re: oops

DISCUSSION Lee Revell 5 participants 10 messages Jul 30, 2005 – Aug 2, 2005

lore
Share & tools
lore

Lee Revell

author
#0 lore raw

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?

Lee

author
#1 lore raw
Quoted 6 lines · Lee Revell

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?

Never mind, /proc/sys/kernel/panic_on_oops should do it.

Lee

#2 lore raw
In reply to Lee Revell
Quoted 6 lines · 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.

author
#3 lore raw
Quoted 6 lines · Alexander Nyberg
Quoted 4 lines · 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".

Quoted 8 lines
Quoted 2 lines

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.

2.6.10 (whatever comes with Ubuntu Hoary). It's a demo install for a client on cobbled together hardware. First I suspected the bleeding edge GeForce video card, then we swapped it which didn't help. Now I suspect the hard drive (or a kernel bug).

And I was wrong, it wasn't more Oopses, it was "scheduling while atomic" messages that forced the interesting stuff offscreen.

Lee

author
#4 lore raw
In reply to Alexander Nyberg
Quoted 6 lines · Alexander Nyberg
Quoted 4 lines · 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".

Quoted 8 lines
Quoted 2 lines

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

#5 lore raw
Quoted 6 lines

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..

Dave.

author
#6 lore raw
Quoted 9 lines · Dave Airlie
Quoted 6 lines

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

#7 lore raw

ECC Support in Linux

I have had a fair amount of trouble with the limited support for ecc reporting on higher end dual and quad cpu servers as the reporting is pretty weak.

On the opterons I can tell which cpu gets errors, but mcelog does not isolate things down to the dimm level properly, is
there a way to do this sort of thing? I am talking about most
of the whitebox type motherboards.

On the newer Intels I have not found any useable ECC support is there any in the kernels?

I can test a variety of hardware if someone needs it, and can probably even come up with some test memory that will generate ecc errors.

Roger

#8 lore raw

Re: ECC Support in Linux

Quoted 3 lines · Roger Heflin

On the newer Intels I have not found any useable ECC support is there any in the kernels?

For ia32, not in kernel now, see http://bluesmoke.sf.net
For ia64, kernel already have support.

Quoted 5 lines

I can test a variety of hardware if someone needs it, and can probably even come up with some test memory that will generate ecc errors.

Good! bluesmoke now has many advanced server support, you can help to test those drivers. Pls subscribe bluesmoke's ML.

thanks
-zhen

author
#9 lore raw

SOLVED - Re: Simple question re: oops

In reply to Dave Airlie
Quoted 8 lines · Dave Airlie
Quoted 6 lines

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..

This was some kind of (ACPI related?) kernel bug. I upgraded from Hoary (2.6.11) to Breezy (2.6.12) and the problem which had been 100% reproducible went away.

One strange thing I noticed was some strange APM/ACPI related messages in the logs when starting X (APM: overridden by ACPI or something). Now I don't get these and the X log just says /dev/apm_bios: No such device.

Oh well, it's working now.

Lee