On Thu, 2007-12-20 at 19:14 +0100, Hemmann, Volker Armin wrote:
> It is just.. I could be the hardware - but I should have seen the
> same 'problem' with earlier kernels - and the 'almost daily oops' only
> started with 2.6.23.
Nonetheless, the oopsen _suggest_ hardware. If it were my box, I'd move
ram modules as a first step. It costs about two minutes to eliminate
that possibility, but you seem reluctant to take that step. Heck, I'd
_hope_ it's something as simple bad ram, because otherwise, quest for
stability could become a time consuming and/or expensive undertaking...
If that didn't change anything, I'd go back and stress test a previously
stable configuration to gain confidence in my hardware. If 'uhoh, not
as stable as I thought' happened, and nothing is getting obviously hot
[1], I'd pray that it's an electrically noisy power supply, because
that's also easy and cheap. In any case, once I was very very confident
that my hardware was indeed sound, I'd move on to an agonizingly tedious
bisection, with no out of tree modules ever loaded, to narrow down when
this memory corruption that nobody else appears to be hitting appeared.
-Mike
1. Crappy heatsink compound can dry out and fracture, leaving hot chip
under a relatively cool heatsink. This is exactly what I found when I
disassembled my suddenly unstable under heavy load P4 box a while back.
--
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
