From: "Andre Tomt" <andre@tomt.net>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: 2.4.1 crashing every other day
Date: Sat, 3 Mar 2001 18:14:02 +0100 [thread overview]
Message-ID: <OPECLOJPBIHLFIBNOMGBGECCDGAA.andre@tomt.net> (raw)
In-Reply-To: <OPECLOJPBIHLFIBNOMGBIEHEDBAA.andre@tomt.net>
> > Looks like you were bitten by either the RAID 1 bugs or the
> > elevator bugs.
> > Try a 2.4.2-pre4 or an 2.4.1-ac18 kernel. Should solve it.
>
> Just installed 2.4.2pre4, seems to be stable for now (testing it
> ATM, running dnetc, several kernel compiles etc.). On 2.4.1 even
> su segfault'd if the server were loaded. But, the problems have
> never appeared before after one or two days uptime, so we'll just
> have to see what happens later on.
>
> As the BIOS settings are the same on both servers, and the CPU
> temperature peaked at +43.5C on the crashing server, I might just
> think it's a software bug. Well, time will tell :-)
>
> Thanks for the input
PS: I'm replying to my own message.
We have solved this problem, it was a CPU fault. It gave all sort of strange
behaviour, like failing pop3 auth, random crashes, files just getting lost
etc. After changing the motherboard and CPU for new ones, this server has
been running flawlessly ever since on 2.4.2-pre4.
Now all I need is some OpenWall'ish patch for 2.4.x that works ;)
Great work guys :-)
--
Regards,
Andre Tomt
prev parent reply other threads:[~2001-03-03 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 1:46 2.4.1 crashing every other day Andre Tomt
2001-02-18 5:31 ` Mordechai Ovits
2001-02-18 13:04 ` Ingo Molnar
2001-02-18 13:47 ` Andre Tomt
2001-03-03 17:14 ` Andre Tomt [this message]
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=OPECLOJPBIHLFIBNOMGBGECCDGAA.andre@tomt.net \
--to=andre@tomt.net \
--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 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.