public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel R. Warner" <drwarner@mail.myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 8139too on ABIT BP6 causes "eth0: transmit timed out"
Date: Mon, 29 Oct 2001 00:32:42 -0500	[thread overview]
Message-ID: <3BDCE9FA.7040101@mail.myrealbox.com> (raw)
In-Reply-To: <16095.1004308212@nice.ram.loc>

Raphael Manfredi wrote:

> Specifically, I get:
> 
>  NETDEV WATCHDOG: eth0: transmit timed out
>  eth0: Tx queue start entry 32190531  dirty entry 32190527.
>  eth0:  Tx descriptor 0 is 00002000.
>  eth0:  Tx descriptor 1 is 00002000.
>  eth0:  Tx descriptor 2 is 00002000.
>  eth0:  Tx descriptor 3 is 00002000. (queue head)
>  eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 45e1.
> 
> and then the machine is dead, network-wise.  I have to reboot (reset).

I have this problem when I compile the driver with PIO mode, except it 
is that way as soon as the card is initalized. The only way for me to 
use PIO is to put the Becker driver in its place.

-D



  parent reply	other threads:[~2001-10-29  5:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-28 22:30 8139too on ABIT BP6 causes "eth0: transmit timed out" Raphael Manfredi
2001-10-28 23:11 ` APM disable broken (was -> Re: 8139too on ABIT BP6 causes "eth0: transmit timed out" ) erich
2001-10-29  0:12   ` victor
2001-10-29  2:43   ` Oden Eriksson
2001-10-29  5:32 ` Daniel R. Warner [this message]
     [not found] ` <039901c1600b$b33fe3a0$0201a8c0@HOMER>
2001-10-29 13:43   ` 8139too on ABIT BP6 causes "eth0: transmit timed out" Raphael Manfredi

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=3BDCE9FA.7040101@mail.myrealbox.com \
    --to=drwarner@mail.myrealbox.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