public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dionysius Wilson Almeida <dwilson@technolunatic.com>
To: linux-kernel@vger.kernel.org
Subject: eepro100: wait_for_cmd_done timeout
Date: Wed, 20 Jun 2001 16:31:34 -0700	[thread overview]
Message-ID: <20010620163134.A22173@technolunatic.com> (raw)

Hi,

I'm running Linux 2.4.5 from kernel.org on my Sony VAIO PCG-FX140 notebook.
I'm runing it on Debian Sid.  The problem i'm facing is that the ethernet card
hangs after every 2 minutes or so and this is consistent.  I've to bring down
the interface and bring it back up and then it works for another 2 minutes 
before freezing.

When i run Redhat 7.1 using redhat supplied intel's e100 driver, everything
works fine.  I tried compiling and loading this driver under Debian, but it
does not work (i.e. does not recognize any adapter).

I tried downloading the e100 driver from Intel site and loading that too..
but that too loads but does not find my adapter.  Further the sources which
came with redhat 7.1 does not compile under Debian Sid.

I tried looking for specific info but i've not been sucessful so far.

Here's what lspci outputs :
00:00.0 Host bridge: Intel Corporation: Unknown device 1130 (rev 11)
00:02.0 VGA compatible controller: Intel Corporation: Unknown device 1132 (rev 11)
00:1e.0 PCI bridge: Intel Corporation: Unknown device 2448 (rev 03)
00:1f.0 ISA bridge: Intel Corporation: Unknown device 244c (rev 03)
00:1f.1 IDE interface: Intel Corporation: Unknown device 244a (rev 03)
00:1f.2 USB Controller: Intel Corporation 82820 820 (Camino 2) Chipset USB (Hub A) (rev 03)
00:1f.3 SMBus: Intel Corporation 82820 820 (Camino 2) Chipset SMBus (rev 03)
00:1f.4 USB Controller: Intel Corporation 82820 820 (Camino 2) Chipset USB (Hub B) (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation: Unknown device 2445 (rev 03)
00:1f.6 Modem: Intel Corporation: Unknown device 2446 (rev 03)
01:00.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8021 (rev 02)
01:02.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
01:02.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
01:08.0 Ethernet controller: Intel Corporation 82820 820 (Camino 2) Chipset Ethernet (rev 03)


And this is the log when the card hangs :
=========================================
Jun 20 16:10:18 debianlap kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jun 20 16:10:18 debianlap kernel: eth0: Transmit timed out: status 0050  0c80 at 314/342 command 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0: Tx ring dump,  Tx queue 342 / 314:
Jun 20 16:10:18 debianlap kernel: eth0:     0 200c0000.
Jun 20 16:10:18 debianlap kernel: eth0:     1 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:     2 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:     3 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:     4 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:     5 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:     6 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:     7 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:     8 200c0000.
Jun 20 16:10:18 debianlap kernel: eth0:     9 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    10 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    11 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    12 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    13 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    14 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    15 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    16 200c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    17 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    18 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    19 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    20 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    21 400c0000.
Jun 20 16:10:18 debianlap kernel: eth0:   =22 000ca000.
Jun 20 16:10:18 debianlap kernel: eth0:    23 000ca000.
Jun 20 16:10:18 debianlap kernel: eth0:    24 200ca000.
Jun 20 16:10:18 debianlap kernel: eth0:    25 000ca000.
Jun 20 16:10:18 debianlap kernel: eth0:  * 26 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    27 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    28 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    29 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    30 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0:    31 000c0000.
Jun 20 16:10:18 debianlap kernel: eth0: Printing Rx ring (next to receive into 977, dirty index 977).
Jun 20 16:10:18 debianlap kernel: eth0:     0 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:     1 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:     2 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:     3 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:     4 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:     5 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:     6 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:     7 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:     8 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:     9 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    10 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    11 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    12 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    13 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    14 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    15 00000001.
Jun 20 16:10:18 debianlap kernel: eth0: l  16 c0000001.
Jun 20 16:10:18 debianlap kernel: eth0:  *=17 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    18 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    19 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    20 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    21 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    22 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    23 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    24 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    25 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    26 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    27 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    28 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    29 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    30 00000001.
Jun 20 16:10:18 debianlap kernel: eth0:    31 00000001.
Jun 20 16:14:07 debianlap kernel: eepro100: wait_for_cmd_done timeout!
Jun 20 16:14:38 debianlap last message repeated 5 times

-Wilson

-- 
We'll try to cooperate fully with the IRS, because, as citizens, we feel
a strong patriotic duty not to go to jail.
		-- Dave Barry

             reply	other threads:[~2001-06-20 23:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-20 23:31 Dionysius Wilson Almeida [this message]
2001-06-20 23:51 ` eepro100: wait_for_cmd_done timeout Andrey Savochkin
2001-06-21  0:02   ` Dionysius Wilson Almeida
2001-06-21 13:46     ` Rafael Martinez
2001-06-22  1:36     ` Dionysius Wilson Almeida
2001-06-22 13:31       ` Andrey Savochkin
2001-06-22 20:06         ` Dionysius Wilson Almeida
2001-06-21 14:19 ` Masaru Kawashima
2001-06-21 14:37   ` John Madden
2001-06-22  1:27     ` Masaru Kawashima
2001-06-21 16:28   ` Masaru Kawashima
  -- strict thread matches above, loose matches on Subject: below --
2003-02-27 16:56 Paul Rolland
2003-02-27 20:30 ` Andrey Nekrasov
2003-02-28  6:50   ` Paul Rolland
2003-03-28 11:42 Chris Bacott
2003-03-28 17:59 ` Jeff Garzik

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=20010620163134.A22173@technolunatic.com \
    --to=dwilson@technolunatic.com \
    --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