From: Eduard Bloch <edi@gmx.de>
To: "Brown, Len" <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: not fixed in 2.4.23-rc3 (was: Re: 2.4.22 SMP kernel build for hyper threading P4)
Date: Sun, 23 Nov 2003 21:45:33 +0100 [thread overview]
Message-ID: <20031123204532.GA6093@zombie.inka.de> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0CC886F@hdsmsx402.hd.intel.com>
#include <hallo.h>
* Brown, Len [Sun, Nov 23 2003, 03:16:11PM]:
> > weird 1+2xHT mode.
>
> Re: BIOS disables CPUSs.
> It would be good to verify that 2.4.21 still works properly on this box
> to verify the hardware isn't hosed. Also, if your BIOS CMOS has error
It does work fine with 2.4.21, the last part of the log on the mentioned
URL is few hours old. The hardware looks okay, the box was running for
more than 14 months without any hardware trouble.
> logs, it might be good to read them to see what it is thinking.
I could not find any error logs till now, the BIOS help only says that a
CPU is turned off when a severe error occured.
> Also, does the same 3-cpu configuration result when you boot 2.6?
I cannot promise when I have a chance to test 2.6 there, it's a
production system.
Mfg,
Eduard.
--
Eine Freude vertreibt hundert Sorgen.
next prev parent reply other threads:[~2003-11-23 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 20:16 not fixed in 2.4.23-rc3 (was: Re: 2.4.22 SMP kernel build for hyper threading P4) Brown, Len
2003-11-23 20:45 ` Eduard Bloch [this message]
2003-11-24 6:19 ` Len Brown
2003-11-24 7:00 ` William Lee Irwin III
2003-11-24 16:49 ` Len Brown
2003-11-24 22:55 ` William Lee Irwin III
2003-11-30 9:28 ` Eduard Bloch
-- strict thread matches above, loose matches on Subject: below --
2003-11-15 15:40 2.4.22 SMP kernel build for hyper threading P4 Job 317
2003-11-15 16:40 ` Eduard Bloch
2003-11-23 15:06 ` not fixed in 2.4.23-rc3 (was: Re: 2.4.22 SMP kernel build for hyper threading P4) Eduard Bloch
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=20031123204532.GA6093@zombie.inka.de \
--to=edi@gmx.de \
--cc=len.brown@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).