From: Colin Walters <walters@cis.ohio-state.edu>
To: linux-kernel@vger.kernel.org
Subject: eepro100 (PCI ID 82820) lockups/failure
Date: Sat, 04 Aug 2001 02:06:10 -0400 [thread overview]
Message-ID: <87elqs2wbx.church.of.emacs@space-ghost.verbum.org> (raw)
I have an ia32 motherboard (MSI 815EM Pro) with an integrated Intel
ethernet controller, about which lspci -v has to say:
01:08.0 Ethernet controller: Intel Corporation 82820 820 (Camino 2) Chipset Ethernet (rev 01)
Subsystem: Intel Corporation: Unknown device 3013
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at d5001000 (32-bit, non-prefetchable) [size=4K]
I/O ports at ac00 [size=64]
Capabilities: [dc] Power Management version 2
And /proc/pci says:
Bus 1, device 8, function 0:
Ethernet controller: Intel Corporation 82801BA(M) Ethernet (rev 1).
IRQ 10.
Master Capable. Latency=32. Min Gnt=8.Max Lat=56.
Non-prefetchable 32 bit memory at 0xd5001000 [0xd5001fff].
I/O at 0xac00 [0xac3f].
I'm using the 2.4.7 eepro100 driver, and the machine consistently
locks up under any kind of heavy network load. I've tried
2.4.8-pre{1,2,3} with the same results. A message sometimes printed
to syslog before the machine locks completely is:
Aug 3 20:56:17 debian kernel: eepro100: wait_for_cmd_done timeout!
Aug 3 21:01:22 debian kernel: eepro100: wait_for_cmd_done timeout!
Aug 3 21:01:29 debian kernel: eepro100: wait_for_cmd_done timeout!
Sometimes it's just the network that goes down, but usually the
machine will lock not long thereafter.
I noticed a patch posted to this mailing list:
<URL:http://mailman.real-time.com/pipermail/linux-kernel/Week-of-Mon-20010618/041187.html>
But it doesn't seem to have been applied.
Anyone have any advice?
next reply other threads:[~2001-08-04 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-04 6:06 Colin Walters [this message]
2001-08-06 9:27 ` Andrey Savochkin
2001-08-06 15:48 ` Joseph Cheek
2001-08-07 10:48 ` Andrey Savochkin
2001-08-07 16:35 ` Joseph Cheek
2001-08-06 18:39 ` Colin Walters
2001-08-06 19:00 ` Richard B. Johnson
2001-08-07 10:24 ` Andrey Savochkin
2001-08-07 12:11 ` Richard B. Johnson
2001-08-06 19:14 ` Alan Cox
2001-08-07 10:46 ` Andrey Savochkin
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=87elqs2wbx.church.of.emacs@space-ghost.verbum.org \
--to=walters@cis.ohio-state.edu \
--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®