From: Jeff Lightfoot <jeffml@pobox.com>
To: jgarzik@mandrakesoft.com (Jeff Garzik),
"Manuel A. McLure" <mmt@unify.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: NETDEV WATCHDOG: eth0: transmit timed out on LNE100TX 4.0, kernel2.4.2-ac11 and earlier.
Date: Tue, 20 Mar 2001 20:09:45 -0700 [thread overview]
Message-ID: <01032020094500.03835@earth> (raw)
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C134@pcmailsrv1.sac.unify.com> <3AB7CFF1.FFC17E31@mandrakesoft.com>
In-Reply-To: <3AB7CFF1.FFC17E31@mandrakesoft.com>
On Tuesday 20 March 2001 14:58, Jeff Garzik wrote:
> > With all the above kernel revisions/drivers, my network card
> > hangs at random (sometimes within minutes, other times it takes
> > days). To restart it I need to do an ifdown/ifup cycle and it
> > will work fine until the next hang. I upgraded to 2.4.2-ac11
> > because of the documented tulip fixes, but after a few days got
> > this again. The error log shows:
>
> In Alan Cox terms, that's a long time ago :)
>
> Can you please try 2.4.2-ac20? It includes fixes specifically for
> this problem.
I started having the same problem with my LNE100TX and switched it
out with another LNE100TX and had the same problem. Figured it was
my BP6 SMP motherboard and ordered a new computer. Doh. :-)
Using 2.4.2-ac20.
Current LNE100TX having problems (other is different Rev):
Lite-On Communications Inc LNE100TX (rev 20)
The first card would get "unexpected IRQ trap at vector d0" before
dying whereas the second one didn't give that indication. It would
just freeze and the traditional "NETDEV WATCHDOG: eth0: transmit
timed out" message.
prev parent reply other threads:[~2001-03-21 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-20 21:14 NETDEV WATCHDOG: eth0: transmit timed out on LNE100TX 4.0, kernel 2.4.2-ac11 and earlier Manuel A. McLure
2001-03-20 21:47 ` NETDEV WATCHDOG: eth0: transmit timed out on LNE100TX 4.0, kernel2.4.2-ac11 " Jeff Garzik
2001-03-21 3:09 ` Jeff Lightfoot [this message]
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=01032020094500.03835@earth \
--to=jeffml@pobox.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmt@unify.com \
/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