From: Thomas Lange <thomas@corelatus.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: NETDEV WATCHDOG: eth0: transmit timed out
Date: Sun, 10 Aug 2003 22:40:57 +0200 [thread overview]
Message-ID: <3F36ADD9.5010205@corelatus.com> (raw)
In-Reply-To: 3F33470A.6070100@imc-berlin.de
Yes, we received these warnings until we enabled MII on our 860.
Without MII, kernel does not know that network is down and
you get timeout when packet never gets delivered, but not until
all transmit buffers are full (IIRC).
/Thomas
Steven Scholz wrote:
>
> Hi there,
>
> on my MPC855T based board I get loads of
>
> NETDEV WATCHDOG: eth0: transmit timed out
>
> when unplugging the network while some transfer is going on.
>
> ./Documentation/networking/e1000.txt states
>
> CAUTION:
> When setting RxIntDelay to a value other than 0, adapters may
> hang (stop transmitting) under certain network conditions. If
> this occurs a NETDEV WATCHDOG message is logged in the system
> event log. In addition, the controller is automatically reset,
> restoring the network connection. To eliminate the potential for
> the hang ensure that RxIntDelay is set to 0.
>
> Is it the same with the MPC8xx FEC ???
> Has the value of RxIntDelay something to do with it under MPC8xx ethernet?
>
> Thanks,
>
> Steven
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-08-10 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F33470A.6070100@imc-berlin.de>
2003-08-10 20:40 ` Thomas Lange [this message]
2007-12-14 13:48 NETDEV WATCHDOG: eth0: transmit timed out José Luís
-- strict thread matches above, loose matches on Subject: below --
2006-08-01 9:18 gpio Interrupt handling for omap5912 Arnold
2006-08-01 10:25 ` NETDEV WATCHDOG: eth0: transmit timed out Arnold
2001-03-01 16:59 Caleb Epstein
2001-03-01 23:01 ` Andrew Morton
2001-01-13 2:24 Darryl Miles
2000-12-28 11:26 Manfred
2000-12-28 11:36 ` David Ford
2000-12-29 0:30 ` idalton
2000-12-28 10:43 David Ford
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=3F36ADD9.5010205@corelatus.com \
--to=thomas@corelatus.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.