From: Ben Hutchings <ben@decadent.org.uk>
To: Jay Cliburn <jcliburn@gmail.com>,
Chris Snook <chris.snook@gmail.com>,
Jie Yang <jie.yang@atheros.com>
Cc: luca boncompagni <lbonco@gmail.com>,
616081@bugs.debian.org, netdev <netdev@vger.kernel.org>
Subject: atl1c fails to force 100 full duplex
Date: Wed, 30 Mar 2011 23:10:45 +0100 [thread overview]
Message-ID: <1301523045.10056.94.camel@localhost> (raw)
In-Reply-To: <AANLkTi=JDec_BTNLEX5AFnK6+BvjDPEN5PZw=QJ3M5XG@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
On Wed, 2011-03-02 at 12:46 +0100, luca boncompagni wrote:
> I can't get more 100FD from my network card when running on 2.6.37, if
> I boot on 2.6.32 it works fine.
>
> If i try to use mii-tool eth1 -F 100baseTx-FD I get the warning at the
> end of dmesg.
This is the usual TX watchdog warning.
> If I try to use ethtool I get no warning but it does not set full duplex.
[...]
Luca later reported that this is still broken in 2.6.38. His full bug
report is at <http://bugs.debian.org/616081>.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
parent reply other threads:[~2011-03-30 22:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <AANLkTi=JDec_BTNLEX5AFnK6+BvjDPEN5PZw=QJ3M5XG@mail.gmail.com>]
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=1301523045.10056.94.camel@localhost \
--to=ben@decadent.org.uk \
--cc=616081@bugs.debian.org \
--cc=chris.snook@gmail.com \
--cc=jcliburn@gmail.com \
--cc=jie.yang@atheros.com \
--cc=lbonco@gmail.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