From: rc@zarq.dhs.org
To: kees <kees@schoen.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NETDEV WATCHDOG with 2.4.5
Date: Thu, 28 Jun 2001 08:52:03 -0400 [thread overview]
Message-ID: <20010628085203.B744@zarq.dhs.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0106261924220.10865-100000@schoen3.schoen.nl>
In-Reply-To: <Pine.LNX.4.21.0106261924220.10865-100000@schoen3.schoen.nl>
On Tue, Jun 26, 2001 at 07:28:23PM +0200, kees wrote:
> Hi,
>
> I tried 2.4.5 but after a couple of hours I lost all network connectivety.
> The log shows:
>
>
> Jun 25 19:34:17 schoen3 kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Jun 25 19:34:17 schoen3 kernel: eth0: Tx timed out, lost
> interrupt? TSR=0x3, ISR=0Jun 25 19:34:19 schoen3 kernel: NETDEV
> WATCHDOG: eth0: transmit timed out
> Jun 25 19:34:19 schoen3 kernel: eth0: Tx timed out, lost
> interrupt? TSR=0x3, ISR=0Jun 25 19:34:21 schoen3 kernel: NETDEV
> WATCHDOG: eth0: transmit timed out
> Jun 25 19:34:21 schoen3 kernel: eth0: Tx timed out, lost
> interrupt? TSR=0x3, ISR=0/tmp/NETDEV
Known bug, been there since at least 2.4.0-test11. There was a patched
2.4.2 that worked well here, as well as 2.4.5-ac17 (Though I haven't tested
2.4.5-ac17 as long as the patched 2.4.2).
R C
next prev parent reply other threads:[~2001-06-28 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-26 17:28 NETDEV WATCHDOG with 2.4.5 kees
2001-06-27 5:23 ` Tim Timmerman
2001-06-27 5:59 ` Andrew Morton
2001-06-27 15:44 ` kees
2001-06-27 15:57 ` Andrew Morton
2001-06-28 5:26 ` Tim Timmerman
2001-06-29 5:29 ` Tim Timmerman
2001-06-28 12:52 ` rc [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-28 4:58 G. Hugh Song
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=20010628085203.B744@zarq.dhs.org \
--to=rc@zarq.dhs.org \
--cc=kees@schoen.nl \
--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