From: "Eric S. Raymond" <esr@thyrsus.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel lockups on dual-Athlon board -- help wanted
Date: Sat, 11 Aug 2001 12:32:00 -0400 [thread overview]
Message-ID: <20010811123200.F6024@thyrsus.com> (raw)
In-Reply-To: <20010811062349.A1769@thyrsus.com> <E15VYfw-0002bu-00@the-village.bc.nu>
In-Reply-To: <E15VYfw-0002bu-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sat, Aug 11, 2001 at 02:19:36PM +0100
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.
2. Do you know of anyone else successfully running 2.4 over an AMD 760
support chipset?
3. Which components do you think are likely to be implicated? Bad memory
is an obvious guess, I suppose.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
"Both oligarch and tyrant mistrust the people,
and therefore deprive them of arms."
--Aristotle
next prev parent reply other threads:[~2001-08-11 16:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-11 10:23 Kernel lockups on dual-Athlon board -- help wanted 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 [this message]
2001-08-11 16:44 ` Johannes Erdfelt
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=20010811123200.F6024@thyrsus.com \
--to=esr@thyrsus.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.