linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Madden <jmadden@ivy.tec.in.us>
To: linux-kernel@vger.kernel.org
Subject: 2.2.19: eepro100 and cmd_wait issues
Date: Tue, 12 Jun 2001 13:00:41 -0500	[thread overview]
Message-ID: <01061109303910.16602@ycn013> (raw)

I'm having trouble on one machine out of about 20 that run with eepro100's. 
This one in particular happens to be a dual port.  I searched through the
archives for this, but I didn't find any definite solutions (one thread, on
"2.2.18 and laptop problems," provided a patch that doesn't seem to make any
difference).

After roughly 30 days of uptime, I get a lot of kernel messages like the
following:

kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)!
kernel: eepro100: cmd_wait for(0x10) timedout with(0x10)!

I'd like to assume that this is bad hardware, but since the problem only
happens every 30 days or so (and every 30 days or so), I wanted to check here to
make sure it wasn't a driver issue.

The only solution I've found that works is to reboot, and since this is
probably the most production machine I'm responsible for (couldn't be any other
one, right?), I'd like to make sure I don't have to schedule a reboot every 29
days or something. :)

More info: 
Kernel 2.2.19 SMP, 
lspci: 
01:04.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 05)
        Subsystem: Intel Corporation EtherExpress PRO/100+ Dual Port Adapter
        Flags: bus master, medium devsel, latency 32, IRQ 10
        Memory at fafff000 (32-bit, prefetchable)
        I/O ports at ece0
        Memory at fcf00000 (32-bit, non-prefetchable)
        Expansion ROM at fd000000 [disabled]
        Capabilities: [dc] Power Management version 1

01:05.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 05)
        Subsystem: Intel Corporation EtherExpress PRO/100+ Dual Port Adapter
        Flags: bus master, medium devsel, latency 32, IRQ 5
        Memory at faffe000 (32-bit, prefetchable)
        I/O ports at ecc0
        Memory at fce00000 (32-bit, non-prefetchable)
        Expansion ROM at fd000000 [disabled]
        Capabilities: [dc] Power Management version 1

dmesg:
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/driv
ers/eepro100.html
eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31 Modified by Andrey V. Savochkin <s
aw@saw.sw.com.sg> and others
eepro100.c: VA Linux custom, Dragan Stancevic <visitor@valinux.com> 2000/11/15


Thanks!

John


-- 
John Madden
UNIX Systems Engineer
Ivy Tech State College
jmadden@ivy.tec.in.us

             reply	other threads:[~2001-06-12 18:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 18:00 John Madden [this message]
2001-06-12 18:51 ` 2.2.19: eepro100 and cmd_wait issues Florin Andrei
2001-06-12 19:20   ` Ken Brownfield
2001-06-13  0:51     ` Ben Greear
2001-06-13  0:03       ` David Lang
2001-06-13  1:52         ` Ben Greear
2001-06-13 11:16           ` Henning P. Schmiedehausen
2001-06-14 17:12     ` Florin Andrei
2001-06-13 21:30 Jason Murphy

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=01061109303910.16602@ycn013 \
    --to=jmadden@ivy.tec.in.us \
    --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;
as well as URLs for NNTP newsgroup(s).