From: Mika Liljeberg <Mika.Liljeberg@welho.com>
To: pavel@md5.ca
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel changes
Date: Sat, 29 Sep 2001 10:25:23 +0300 [thread overview]
Message-ID: <3BB57763.1D8F3C25@welho.com> (raw)
In-Reply-To: <20010928143205.B3669@md5.ca>
Pavel Zaitsev wrote:
> Now I don't trust 2.4 line
> kernel to work *at all*, so cautiously keep all old kernels in the /boot,
> when upgrading.
Well, it's a good idea to always keep a few old kernels in /boot but I
certainly identify with your point. I like to run the bleeding edge
kernels at home but lately I've been having doubts. I've been looking
for a stable kernel since 2.4.0-test9. While 2.4.0-test9 is not exactly
bug free either, any later kernel either reboots at random (all later
test versions and early 2.4.x versions) or locks up hard on my SMP
machine. This does not appear to have anything to do with load, indeed
it often happens with the machine completely idle. It can take hours or
days before this occurs but sooner or later it does. Of course, nothing
ever gets written to the logs. With 2.4.8 I almost thought I had hit
paydirt, but no such luck. 2.4.9 crashed right off the bat. 2.4.10 seems
more unstable than most. Enough so that I finally patched in ext3 and
installed journals on my file systems just to give them a semblance of
stability (and to speed up the random reboots).
That said, I might just have a hardware problem. However, something in
the new kernels seems to touch it off. Any ideas and tools to track this
down, besides intuition and brute force, would be appreciated. [Right
now I'm running with swap disabled, on somebody's suggestion. Let's see
what happens.]
Regards,
Mika Liljeberg
next prev parent reply other threads:[~2001-09-29 7:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 21:32 kernel changes Pavel Zaitsev
2001-09-28 22:04 ` Mark Frazer
2001-09-28 22:31 ` Ben Greear
2001-09-28 22:33 ` Alan Cox
2001-10-01 9:07 ` Paul Larson
2001-09-28 22:06 ` Alan Cox
2001-09-29 13:43 ` Andrew Ebling
2001-09-29 7:25 ` Mika Liljeberg [this message]
2001-09-29 10:19 ` Ville Herva
2001-09-29 16:45 ` John Alvord
2001-09-29 17:23 ` arjan
2001-09-30 8:17 ` John Alvord
2001-10-01 17:07 ` Martin J. Bligh
[not found] <fa.b97kd6v.8j2vhi@ifi.uio.no>
[not found] ` <fa.hmvo4bv.l2gsaj@ifi.uio.no>
2001-09-29 7:29 ` Dan Maas
2001-10-04 0:36 ` bill davidsen
2001-10-04 9:43 ` John Alvord
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=3BB57763.1D8F3C25@welho.com \
--to=mika.liljeberg@welho.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@md5.ca \
/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.