From: "Ethan C. Baldridge" <BaldridgeE@cadmus.com>
To: linux-kernel@vger.kernel.org
Subject: hardware lock-up with 2.4.0-test10
Date: Fri, 03 Nov 2000 15:35:01 -0500 [thread overview]
Message-ID: <3A032175.C2DDFFFA@cadmus.com> (raw)
on my box at work, which is a Pentium 200 with 64 megs of ram.
no strange messages in /var/log/messages, no commonality I've found
between the lockups. This doesn't happen if I go back to 2.2.16 (which
I'm in right now).
Twice the lock-up occurred while initscripts were running on boot-up (at
different places in the initscripts). Twice now it has happened while
I've been away from my computer for a while, both times apparently after
the screensaver has come on (black screen).
I'm running with DevFS and devfsd, IDE hard drive (Intel 82371SB PIIX3
controller), 3com 3C905 ethernet card, Intel 82439HX Triton II chipset
motherboard, Pentium with F00F bug.
Has anyone else seen this, and can you give me any suggestions?
Thanks,
Ethan Baldridge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-11-03 19:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A032175.C2DDFFFA@cadmus.com \
--to=baldridgee@cadmus.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