public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Raphael Manfredi <Raphael_Manfredi@pobox.com>
To: linux-kernel@vger.kernel.org
Subject: 8139too on ABIT BP6 causes "eth0: transmit timed out"
Date: Sun, 28 Oct 2001 23:30:12 +0100	[thread overview]
Message-ID: <16095.1004308212@nice.ram.loc> (raw)

I'm running:

	Linux nice 2.4.12-ac3 #1 SMP Sat Oct 20 16:21:24 MEST 2001 i686 unknown

but this problem is not specific to that kernel.  I've been having
it for a looong time.

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).

Note that I am on an ABIT BP6 board, and I do get a lot of APIC errors
under heavy network traffic, which is what raises the above.
By heavy network traffic, I mean a 7 Mb/s full duplex (it's a 100 Mb/s
LAN).

I suspect that somewhere, the APIC gets hosed and looses an interrupt,
and then the ethernet driver no longer processes its queue.
Is there anything that can be done to reset the hardware state more
fully when this occurs?

Raphael

             reply	other threads:[~2001-10-28 22:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-28 22:30 Raphael Manfredi [this message]
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 ` 8139too on ABIT BP6 causes "eth0: transmit timed out" Daniel R. Warner
     [not found] ` <039901c1600b$b33fe3a0$0201a8c0@HOMER>
2001-10-29 13:43   ` 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=16095.1004308212@nice.ram.loc \
    --to=raphael_manfredi@pobox.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