From: Mark Symonds <mark@symonds.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.23 hard lock, 100% reproducible.
Date: Sat, 6 Dec 2003 18:36:50 -0800 [thread overview]
Message-ID: <20031207023650.GA772@symonds.net> (raw)
Hi,
I've got a machine here that is locking hard under
2.4.23. Normally would suspect it's a hardware problem
but it runs fine on 2.4.22 and also 2.2 series kernels.
In a bit of a quandry here since that box has shell
users...
I'm getting no oopses on the monitor nor in the logs -
this is a hard, instantaneous crash. No kbd, no nothing,
good night.
I've got a kernel compiling right now with hacking
support, but none of the additional hacking options
are enabled.
Wondering if anyone else has seen this? lspci output is
below, will wait until requested before dumping a bunch
of crap about my hardware onto the list.
Anything I can do from userland, let me know.
--
Mark
-----------------------
symonds:~# lspci
00:00.0 Host bridge: Intel Corp. 82810 GMCH [Graphics
Memory Controller Hub] (rev 03)
00:01.0 VGA compatible controller: Intel Corp. 82810 CGC
[Chipset Graphics Controller] (rev 03)
00:1e.0 PCI bridge: Intel Corp. 82801AA PCI Bridge (rev
02)
00:1f.0 ISA bridge: Intel Corp. 82801AA ISA Bridge (LPC)
(rev 02)
00:1f.1 IDE interface: Intel Corp. 82801AA IDE (rev 02)
00:1f.2 USB Controller: Intel Corp. 82801AA USB (rev 02)
00:1f.3 SMBus: Intel Corp. 82801AA SMBus (rev 02)
01:09.0 Multimedia audio controller: Cirrus Logic
Crystal CS4281 PCI Audio (rev 01)
01:0b.0 Ethernet controller: D-Link System Inc RTL8139
Ethernet (rev 10)
01:0d.0 Ethernet controller: VIA Technologies, Inc.
VT86C100A [Rhine 10/100] (rev 06)
01:0e.0 Ethernet controller: Lite-On Communications Inc
LNE100TX (rev 20)
symonds:~#
next reply other threads:[~2003-12-07 2:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 2:36 Mark Symonds [this message]
2003-12-07 3:30 ` 2.4.23 hard lock, 100% reproducible Philippe Troin
2003-12-07 4:34 ` Mark Symonds
2003-12-07 18:32 ` Chris Frey
2003-12-07 18:49 ` James Bourne
2003-12-07 19:21 ` David Rees
2003-12-07 20:19 ` James Bourne
-- strict thread matches above, loose matches on Subject: below --
2003-12-07 6:50 Alex Davis
2003-12-07 6:55 ` William Lee Irwin III
[not found] ` <046a01c3bca1$267ba5e0$7a01a8c0@gandalf>
2003-12-07 9:07 ` William Lee Irwin III
2003-12-07 9:16 ` Keith Owens
2003-12-07 9:36 ` William Lee Irwin III
2003-12-08 16:34 ` Oliver Teuber
2003-12-07 10:01 ` Mark Symonds
2003-12-07 11:34 ` Martin Josefsson
2003-12-07 14:40 ` Marcelo Tosatti
2003-12-07 23:18 ` Mark Symonds
2003-12-08 4:53 ` William Lee Irwin III
2003-12-08 7:12 ` Tim Timmerman
2003-12-08 11:06 ` Marcelo Tosatti
2003-12-09 6:29 ` Tim Timmerman
2003-12-08 10:17 ` Marcelo Tosatti
2003-12-08 15:54 ` Stephan von Krawczynski
2003-12-08 16:15 ` Marcelo Tosatti
2003-12-08 16:31 ` Jeff Garzik
2003-12-08 16:55 ` Stephan von Krawczynski
2003-12-08 19:56 ` Mark Symonds
2003-12-07 7:33 ` Mark Symonds
2003-12-07 16:24 ` Alex Davis
2003-12-08 17:06 Xose Vazquez Perez
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=20031207023650.GA772@symonds.net \
--to=mark@symonds.net \
--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