From: Tom Rini <trini@kernel.crashing.org>
To: Eirik Overby <ltning@anduin.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.x SMP issues on 440LX (?)
Date: Mon, 30 Apr 2001 08:04:08 -0700 [thread overview]
Message-ID: <20010430080408.B18828@opus.bloom.county> (raw)
In-Reply-To: <20010430062932Z133116-409+1416@vger.kernel.org>
In-Reply-To: <20010430062932Z133116-409+1416@vger.kernel.org>; from ltning@anduin.net on Mon, Apr 30, 2001 at 08:29:40AM +0100
On Mon, Apr 30, 2001 at 08:29:40AM +0100, Eirik Overby wrote:
> As another person (Aaron M. Folmsbee, 28.04.01-22:32) in here reported
> earlier, there seems to be problems
> with Intel 440LX chipsets with dual CPU's and the Linux 2.4 kernel series.
> Simply stated, this just plain doesn't work right. When sticking in only one
> CPU, the system boots fine, but I
> see "random" hangs and kernel panics. Watching boot messages and doing a cat
> /proc/cpuinfo gives the
> correct information; I have one Intel Pentium II installed.
> However, when sticking in both CPU's, one of two things happen:
What Mobo/CPUs? I have a Tyan Tiger SD1692DL (I _think_ that's the model, I
haven't checked in ages tho) with 2 P2/333 (Deschutes). 2.4.0,2.4.1,2.4.2 and
2.4.3-pre3 (reiserfs patches) have worked great for me. 2.4.3-pre3 was
up for 16days before I rebooted into 2.4.4 (and power killed another 10+ day
uptime).
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2001-04-30 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 7:29 Eirik Overby
2001-04-30 15:04 ` Tom Rini [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=20010430080408.B18828@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltning@anduin.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®