From: Michael Buesch <mbuesch@freenet.de>
To: Michael Frank <mhf@linuxmail.org>
Cc: Chris Stromsoe <cbs@cts.ucla.edu>, linux-kernel@vger.kernel.org
Subject: Re: lock up with 2.4.23
Date: Thu, 12 Feb 2004 19:27:18 +0100 [thread overview]
Message-ID: <200402121927.25426.mbuesch@freenet.de> (raw)
In-Reply-To: <200402130119.58662.mhf@linuxmail.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 12 February 2004 18:19, you wrote:
> You say your drivers are not that bad, OK, the kernel is not
> that bad too.
Yea, I know. :) It ran months over months without
problems, now.
> Now, please consider that this mainboard is about 10 years old.
> How old is the PSU?
PSU? What's that?
> Consider whether the ambient temperature was higher than average
> at time of lockup.
>
> Please check:
>
> 1) CPU heatsink contaminated
> 2) CPU fan bad
> 3) PSU fan bad or contaminated (also PSU slots/fins)
> 4) Power supply instabel due to capacitors drying out
> 5) Mainboard CPU voltage instable due to capacitors drying out
> 6) Bad contacts at memory modules
> 7) Coroded PSU or other connectors
>
> ... Just some of the things I have encountered
>
> Bottom line: its HW!
Yes, it could be. We'll see. I try to catch the next
oops (if there is one).
> Your mail is helpful ;)
Sorry for my bad english. ;)
> Michael
- --
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAK8WMFGK1OIvVOP4RAn5LAKCKt+nb/rdAk/x25lFpbZQdGxD/HwCcDxAK
vZImv3Jz4da1gKzUtOf4/Rk=
=8elT
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-02-12 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 5:18 lock up with 2.4.23 Chris Stromsoe
2004-02-12 15:34 ` Michael Buesch
2004-02-12 17:19 ` Michael Frank
2004-02-12 18:27 ` Michael Buesch [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 21:03 Xose Vazquez Perez
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=200402121927.25426.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--cc=cbs@cts.ucla.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.