From: Philippe Troin <phil@fifi.org>
To: Mark Symonds <mark@symonds.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.23 hard lock, 100% reproducible.
Date: 06 Dec 2003 19:30:08 -0800 [thread overview]
Message-ID: <87he0ds3sv.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <20031207023650.GA772@symonds.net>
Mark Symonds <mark@symonds.net> writes:
> 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.
Not even sysrq?
> 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.
Same for me.
2.4.23 locks up hard. 2.4.22 worked perfectly (save the random usb
oops).
I was not able to capture a register trace or a process dump with
sysrq because this box has a usb keyboard and usb seems to get
shot. I've plugged a ps/2 keyboard to get more details the next
lock-up. If this fail, I might try the NMI oopser.
lspci:
00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] (rev 23)
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 10)
00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 11)
00:07.3 Host bridge: VIA Technologies, Inc. VT82C596 Power Management (rev 30)
00:0f.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08)
00:0f.1 Input device controller: Creative Labs SB Live! (rev 08)
00:10.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]
00:12.0 SCSI storage controller: Adaptec 7892A (rev 02)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04)
Phil.
next prev parent reply other threads:[~2003-12-07 3:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 2:36 2.4.23 hard lock, 100% reproducible Mark Symonds
2003-12-07 3:30 ` Philippe Troin [this message]
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
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=87he0ds3sv.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@symonds.net \
/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;
as well as URLs for NNTP newsgroup(s).