From: Jonathan Sambrook <jonathan@dsvr.net>
To: Klaus Muth <muth@hagos.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel panic with 2.4.26
Date: Wed, 16 Feb 2005 15:16:36 +0000 [thread overview]
Message-ID: <421363D4.5050209@dsvr.net> (raw)
In-Reply-To: <200502161402.33666.muth@hagos.de>
Klaus Muth wrote:
> Am Mittwoch, 16. Februar 2005 12:14 schrieb Jonathan Sambrook:
> Server oopsed again 10 minutes ago. Same symptoms.
<sigh> schade
> The kernel upgrade did not
> help... Would an update to an 2.6 kernel help or should I better turn
> hyperthreading off?
My experience is running _modified_ 2.4 kernels. Turning HT off solved
the problem here. Of course YMMV if the root cause is different.
I have no experience of running HT on 2.6. My hunch would be that more
HT users run 2.6 than 2.4 nowadays, so the problem would've been raised
by now? If so your choice depends on whether the joint benefits of HT
and of 2.6 outweigh any effort of moving to 2.6.
Jonathan
next prev parent reply other threads:[~2005-02-16 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 6:15 kernel panic with 2.4.26 Klaus Muth
2005-02-11 9:15 ` Klaus Muth
2005-02-16 11:14 ` Jonathan Sambrook
2005-02-16 13:02 ` Klaus Muth
2005-02-16 15:16 ` Jonathan Sambrook [this message]
2005-02-21 11:06 ` Klaus Muth
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=421363D4.5050209@dsvr.net \
--to=jonathan@dsvr.net \
--cc=linux-kernel@vger.kernel.org \
--cc=muth@hagos.de \
/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