From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: almost daily Kernel oops with 2.6.23.9 - and now 2.6.23.11 as well
Date: Fri, 21 Dec 2007 13:54:36 +0100 [thread overview]
Message-ID: <200712211354.36460.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <1198223236.3797.108.camel@homer.simson.net>
On Freitag, 21. Dezember 2007, Mike Galbraith wrote:
> 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...
>
It costs a little bit more, but it will be part of the 'past holiday special'.
As an intermediate step I incresed the voltages of the ram - looks good so
far.
> If that didn't change anything, I'd go back and stress test a previously
> stable configuration to gain confidence in my hardware.
you mean like playing ut2004 with reduced fans or several instances of
cpuburn, or compiling something big like kdepim with kdeenablefinal? Done all
that ...
> 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.
yeah, it would be the least annoying variant. After one PSU ate two computers,
this one is just two and a half month old - I had my share of bad PSUs.
That is why I increased the voltages. Maybe it helps.
> 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.
still this would show up with the temps. And the temps are ok.
Glück Auf,
Volker
next prev parent reply other threads:[~2007-12-21 12:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 0:06 almost daily Kernel oops with 2.6.23.9 Hemmann, Volker Armin
2007-12-17 14:59 ` almost daily Kernel oops with 2.6.23.9 - and now 2.6.23.11 as well Hemmann, Volker Armin
2007-12-17 15:47 ` Hugh Dickins
2007-12-17 19:44 ` Hemmann, Volker Armin
2007-12-20 2:13 ` Hemmann, Volker Armin
2007-12-20 3:50 ` Scott
2007-12-20 5:53 ` Hemmann, Volker Armin
2007-12-20 14:38 ` David Newall
2007-12-20 18:37 ` Hemmann, Volker Armin
2007-12-20 21:48 ` Pekka Enberg
2007-12-20 22:13 ` Ingo Molnar
[not found] ` <1198134579.4429.10.camel@homer.simson.net>
2007-12-20 18:14 ` Hemmann, Volker Armin
2007-12-21 7:47 ` Mike Galbraith
2007-12-21 12:54 ` Hemmann, Volker Armin [this message]
2007-12-20 15:25 ` Stefan Richter
2007-12-20 18:12 ` Hemmann, Volker Armin
2007-12-20 19:04 ` Ingo Molnar
2007-12-20 20:29 ` Hemmann, Volker Armin
2007-12-21 2:09 ` Hemmann, Volker Armin
2007-12-21 11:19 ` Ingo Molnar
2007-12-29 23:03 ` Hemmann, Volker Armin
2007-12-20 19:06 ` Stefan Richter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200712211354.36460.volker.armin.hemmann@tu-clausthal.de \
--to=volker.armin.hemmann@tu-clausthal.de \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox