From: "Martin J. Bligh" <mbligh@google.com>
To: netdev@vger.kernel.org
Subject: via-rhine driver stalls with: PHY status 786d, resetting...
Date: Sat, 03 Nov 2007 11:30:12 -0700 [thread overview]
Message-ID: <472CBE34.1040405@google.com> (raw)
Linux 2.6.23
http://bugzilla.kernel.org/show_bug.cgi?id=9300
Under any sort of traffic load (recursive scp from another box of a
bunch of mp3s, for instance), I get continuous stalls. Recovers every
time, but is dog slow.
NETDEV WATCHDOG: eth2: transmit timed out
eth2: Transmit timed out, status 0000, PHY status 786d, resetting...
eth2: link up, 100Mbps, full-duplex, lpa 0xCDE1
driver is via-rhine.
Google search indicates this has been a problem since at least 2.4.19
and 2002 ... can we not fix this somehow? I have an e1000 card in this
box too, but that has similar issues ;-(
reply other threads:[~2007-11-03 18:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=472CBE34.1040405@google.com \
--to=mbligh@google.com \
--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;
as well as URLs for NNTP newsgroup(s).