From: "Eric S. Raymond" <esr@thyrsus.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Kernel lockups on dual-Athlon board -- help wanted
Date: Sat, 11 Aug 2001 06:23:49 -0400 [thread overview]
Message-ID: <20010811062349.A1769@thyrsus.com> (raw)
Gary Sandine of Los Alamos Computers and I are attempting to qualify
Linux on a Tyan 2462 K7 Thunder motherboard -- dual Athlon 1200 MP
chips supported by an AMD 760 chipset. We have been seeing mysterious
lockups during commands to build things from source, like kernels and X.
We've been trying to track down the problem for about sixteen hours
and have gathered quite a bit of data, but don't have a theory to explain
it.
First, we have established that this is a real kernel hang, not just a
bad device state:
A. Lockups can be induced in either console or X mode. A reliable way to
induce them is to run `make clean' on an X tree (any sufficiently
long-running command seems to do it).
B. We logged in over the network, started a top(1) in the network
session, induced the hang on the console, and watch top(1) freeze.
So
C. The magic AltSysRq command is ineffective when the lockups happen.
Here's what we know about it:
1. Lockups never occur under a uniprocessor kernel.
2. Configuring APM and ACPI out of the kernel does not prevent the lockups.
Disabling ACPI and power management doesn't stop them either.
3. Changing kernels from 2.4.3 to 2.4.7 doesn't prevent the lockups.
4. The SMP kernel built for either PII or AMD (no APM, no ACPI) locks up.
5. There is an undocumented BIOS setting "Use PCI Interrupt Entries in
MP table." By default it is on. Turning it off doesn't prevent the
lockups.
6. Here's a weird one. When the kernel is running, the power switch
has to be pressed down for 4 seconds to power down the machine. But
during a lockup it powers down the machine instantly.
What we're seeing suggests some bad interaction between the SMP
support and the hardware. But item 7 hints that power management
could be involved, even though we have it configured out.
Anybody have a brilliant insight? Suggestions for further tests?
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Government should be weak, amateurish and ridiculous. At present, it
fulfills only a third of the role.
-- Edward Abbey
next reply other threads:[~2001-08-11 10:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-11 10:23 Eric S. Raymond [this message]
2001-08-11 10:46 ` Kernel lockups on dual-Athlon board -- help wanted 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
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=20010811062349.A1769@thyrsus.com \
--to=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 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.