Oops counter (was Re: ntfs OOPS (2.5.63))

Oops counter (was Re: ntfs OOPS (2.5.63))

Post by Szakacsits Szabolc » Sat, 08 Mar 2003 00:00:41



Quote:> | > ==> Mar  1 13:35:44 midway kernel: Oops: 0002
> | >
> | > This means oops counter is 2. So there were two oopses before with
> | > counter value 0 and 1.
> |
> | I just checked, this is not true (I could dig up the false source
> | of information if interested).

I didn't have to: Google listed it in the top 5 hits searching for
"oops counter" ...

Quote:> However, such an oops counter could be useful...

I believed immediately this feature was added, it looked so good idea.

        Szaka

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. 2.5.63 accesses below %esp (was: Re: ntfs OOPS (2.5.63))

I don't think gcc 2.96 had that problem. I've not seen it there, but
gcc 3.0.x certainly does and a gcc 3.0.x early 3.1.x built kernels seems
to explode randomly under load probably for this reason.

I've also not seen any problemd with this on gcc 3.2. Valgrind has some
notes on affected compilers as the valgrind app also picks up this
violation by the compiler.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Streams ANSI after an execX()

3. telnet into PPP (help)

4. ntfs OOPS (2.5.63)

5. Whats port #5?

6. How to reopen stdin after ^D?

7. oops Re: 2.5.63-mm2

8. Oops in tulip op ppc on 2.5.62 and 2.5.63

9. Oops:2.5.63 accessing software raid5 volume

10. rootfs on nfs : oops 2.5.63

11. oops in 2.5.63: kernel BUG at drivers/usb/storage/usb.c:972