From: Charles Cazabon <linux-kernel@discworld.dyndns.org>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel lockups on dual-Athlon board -- help wanted
Date: Sat, 11 Aug 2001 10:08:58 -0600 [thread overview]
Message-ID: <20010811100858.A11219@qcc.sk.ca> (raw)
In-Reply-To: <20010811062349.A1769@thyrsus.com>
In-Reply-To: <20010811062349.A1769@thyrsus.com>; from esr@thyrsus.com on Sat, Aug 11, 2001 at 06:23:49AM -0400
Eric S. Raymond <esr@thyrsus.com> wrote:
>
> 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).
This sounds like bad hardware.
> 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.
This is normal for ATX machines. There's usually a BIOS setting
controlling whether the power switch is instant or delayed, but once the
software isn't running any more, it's always instant.
I really do think it's bad hardware -- CPU, mainboard, power supply, or
some combination of the above.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <linux@discworld.dyndns.org>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
next prev parent reply other threads:[~2001-08-11 16:09 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
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 [this message]
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=20010811100858.A11219@qcc.sk.ca \
--to=linux-kernel@discworld.dyndns.org \
--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®