Since I know various people archive problem reports on 2.0.3x, I thought
I'd mention that the 2.0.33 crashes I reported could well be due to bad
hardware. At the same time the kernel was upgraded from 2.0.32, we did a
bit of hardware juggling too.
I have since downgraded to 2.0.32 (previously rock solid) and have got a
few very exotic oopses. One of them was "invalid opcode"!! Almost a sure
sign of a frying processor and/or dodgy memory/cache.
Cheers
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu