From: "Andre Tomt" <andre@tomt.net>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Cc: "Mordechai Ovits" <movits@ovits.net>
Subject: RE: 2.4.1 crashing every other day
Date: Sun, 18 Feb 2001 14:47:12 +0100 [thread overview]
Message-ID: <OPECLOJPBIHLFIBNOMGBIEHEDBAA.andre@tomt.net> (raw)
In-Reply-To: <20010218003125.A25564@ovits.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
--
Regards,
Andre Tomt
next prev parent reply other threads:[~2001-02-18 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 1:46 Andre Tomt
2001-02-18 5:31 ` Mordechai Ovits
2001-02-18 13:04 ` Ingo Molnar
2001-02-18 13:47 ` Andre Tomt [this message]
2001-03-03 17:14 ` Andre Tomt
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=OPECLOJPBIHLFIBNOMGBIEHEDBAA.andre@tomt.net \
--to=andre@tomt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=movits@ovits.net \
/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
all inboxes | Powered by JetHome®