From: Johannes Erdfelt <johannes@erdfelt.com>
To: "Eric S. Raymond" <esr@thyrsus.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel lockups on dual-Athlon board -- help wanted
Date: Sat, 11 Aug 2001 12:44:09 -0400 [thread overview]
Message-ID: <20010811124409.Y3126@sventech.com> (raw)
In-Reply-To: <20010811062349.A1769@thyrsus.com> <E15VYfw-0002bu-00@the-village.bc.nu> <20010811123200.F6024@thyrsus.com>
In-Reply-To: <20010811123200.F6024@thyrsus.com>; from esr@thyrsus.com on Sat, Aug 11, 2001 at 12:32:00PM -0400
On Sat, Aug 11, 2001, Eric S. Raymond <esr@thyrsus.com> wrote:
> Alan Cox <alan@lxorguk.ukuu.org.uk>:
> > Try a completely different board and components. There are folks
> > running rock solid 2.4 on dual Athlons. I speculate yours is perhaps
> > marginal somewhere.
>
> OK...
>
> 1. By "different board" do you mean different instance of the same design, or
> different design? Because the K7 Thunder is, AFAIK, the only dual-Athlon
> 1200 board that exists right now.
I suspect he means same design, different physical hardware.
> 2. Do you know of anyone else successfully running 2.4 over an AMD 760
> support chipset?
I am.
I have had some cooling problems with some of the hardware in the past.
> 3. Which components do you think are likely to be implicated? Bad memory
> is an obvious guess, I suppose.
Cooling most likely. What kind of system is this? Rackmount? Desktop
case?
JE
next prev parent reply other threads:[~2001-08-11 16:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-11 10:23 Eric S. Raymond
2001-08-11 10:46 ` Alex Buell
2001-08-11 16:22 ` Eric S. Raymond
2001-08-11 13:19 ` Alan Cox
2001-08-11 16:32 ` Eric S. Raymond
2001-08-11 16:44 ` Johannes Erdfelt [this message]
2001-08-11 16:50 ` Eric S. Raymond
2001-08-11 10:09 ` John Heil
2001-08-11 17:22 ` Eric S. Raymond
2001-08-11 10:30 ` John Heil
2001-08-11 17:57 ` Charles Cazabon
2001-08-11 19:31 ` Ben LaHaise
2001-08-11 16:08 ` Charles Cazabon
2001-08-11 16:17 ` Eric W. Biederman
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=20010811124409.Y3126@sventech.com \
--to=johannes@erdfelt.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=esr@thyrsus.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
all inboxes | Powered by JetHome®