From: "Bradley M. Kuhn" <bkuhn@ebb.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 10682] New: (net 8139too) dual ethernet system, any reasonable network causes: NETDEV WATCHDOG: ethN: transmit timed out
Date: Tue, 13 May 2008 10:35:26 -0400 [thread overview]
Message-ID: <87y76enufl.fsf@hughes.sflc-vpn> (raw)
In-Reply-To: <20080512151142.067b98d2.akpm@linux-foundation.org> (Andrew Morton's message of "Mon\, 12 May 2008 15\:11\:42 -0700")
Alex (quoted below) must have seen my bug ticket regarding the 8319too
WATCHDOG bug and replied to me privately. I include his message below
primarily for posterity on the bug ticket and mailing list archives. He's
confirming 2.6.23 fails in the same way as well on this particular box
with the two 8139too cards in it.
I expect to try the older kernel versions Andrew suggested in the next few
days and will report back when I have.
Meanwhile, I have vague and more-or-less unfounded theory that this bug is
specific to having two of the same style card in the same box. Would it
be useful, assuming that I can't make an older kernel work, to try seeing
if I can physically unwire one of the ethernet cards to see if the problem
occurs with only one card wired up? (This may be undoable without
breaking something on this tiny box, but I'm willing to have a go if folks
think it might help.)
#########################################################################
Date: Tue, 13 May 2008 16:40:46 +0800
To: bkuhn@ebb.org
Subject: Re: (net 8139too) dual ethernet system, any reasonable network causes: NETDEV
From: "Alex REDACTED" <redacted@example.com>
We're using an ebox 4852/4853 with debian linux kernel 2.6.23.
Today during testing, we found the exact problem that you're reporting -
NETDEV WATCHDOG timeouts when any reasonable network load is placed on
routing between the ethernet ports.
We're using the 8139too driver too, version 0.9.28.
No solutions yet, we will probably look into it as time permits.
Just thought you might appreciate another kernel version data point.
Cheers,
--
Alex.
#########################################################################
--
-- bkuhn
next prev parent reply other threads:[~2008-05-13 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10682-10286@http.bugzilla.kernel.org/>
2008-05-12 4:10 ` [Bugme-new] [Bug 10682] New: (net 8139too) dual ethernet system, any reasonable network causes: NETDEV WATCHDOG: ethN: transmit timed out Andrew Morton
[not found] ` <20080512214014.GB27236@ebb.org>
2008-05-12 22:11 ` Andrew Morton
2008-05-13 14:35 ` Bradley M. Kuhn [this message]
2008-05-19 2:05 ` Bradley M. Kuhn
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=87y76enufl.fsf@hughes.sflc-vpn \
--to=bkuhn@ebb.org \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@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