From: Andrew Morton <akpm@osdl.org>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Transmit timeout with 3c395, 2.4.19, 2.4.22
Date: Mon, 27 Oct 2003 11:18:27 -0800 [thread overview]
Message-ID: <20031027111827.07b04891.akpm@osdl.org> (raw)
In-Reply-To: <20031027141358.GA26271@gamma.logic.tuwien.ac.at>
Norbert Preining <preining@logic.at> wrote:
>
> Hi Andrew, hi list!
>
> Suddenly, after 160 days of running, our bridged firewall started to
> spit out this:
> NETDEV WATCHDOG: eth1: transmit timed out
>
> ...
>
> This always happened with eth1, so we think it *may* a hardware error
> creeping in. I would like to know wether this can be the case, or
> wether there is something else (switches on the other side, ...) which
> may have produced these errors.
Yes, a bad cable might explain this. Or another host which is babbling
away all the time (on a half-duplex setup).
next prev parent reply other threads:[~2003-10-27 19:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 14:13 Transmit timeout with 3c395, 2.4.19, 2.4.22 Norbert Preining
2003-10-27 19:18 ` Andrew Morton [this message]
2003-10-28 6:49 ` Norbert Preining
2003-10-30 17:50 ` Stian Jordet
2004-03-27 16:41 ` Oops with md/ext3 on 2.4.25 on alpha architecture Norbert Preining
2004-03-27 16:41 ` Norbert Preining
2004-03-28 16:02 ` md raid oops on 2.4.25/alpha Norbert Preining
2004-03-28 16:02 ` Norbert Preining
2004-03-28 17:30 ` Thomas Steudten
2004-03-28 16:45 ` Ross Dickson
2004-03-28 20:32 ` Norbert Preining
2004-03-28 20:32 ` Norbert Preining
2004-03-28 18:30 ` Ivan Kokshaysky
2004-03-29 10:41 ` Thomas Steudten
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=20031027111827.07b04891.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/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.