From: Matthew Costello <mattc@san.rr.com>
To: alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.19 & 2.4.20 hang without oops...
Date: Fri, 10 Jan 2003 22:35:33 -0800 [thread overview]
Message-ID: <3E1FBB35.10305@san.rr.com> (raw)
My motherboard is a Supermicro P6DBE with the 440BX chipset,
2 x P3 (Katmai) at 450MHz, 512MB RAM.
The output of lspci:
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
(rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge
(rev 03)
00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:0f.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
00:10.0 SCSI storage controller: Adaptec AHA-2940U2/U2W
00:12.0 PCI bridge: Hint Corp HB1-SE33 PCI-PCI Bridge (rev 13)
00:14.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
01:08.0 USB Controller: NEC Corporation USB (rev 41)
01:08.1 USB Controller: NEC Corporation USB (rev 41)
01:08.2 USB Controller: NEC Corporation USB 2.0 (rev 02)
01:0b.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394
Controller (Link)
02:00.0 VGA compatible controller: nVidia Corporation RIVA TNT2 Model 64
(rev 15)
Also two ISA cards:
Adaptec AHA1542C
Digiboard PC/8i
I'd be happy to help track the hang down. If not I'll have to backport
the firewire changes in 2.4.19/20 to 2.4.18 since the WD firewire drive
is not recognized correctly in 2.4.20.
--- Matthew Costello <mattc@san.rr.com>
next reply other threads:[~2003-01-11 6:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 6:35 Matthew Costello [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-07 16:25 Matthew Costello
2003-01-07 6:52 Charlton Harrison
2003-01-08 14:45 ` Alan Cox
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=3E1FBB35.10305@san.rr.com \
--to=mattc@san.rr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
Powered by JetHome