From: Ben Greear <greearb@candelatech.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: r8169 doesn't report link state correctly.
Date: Wed, 20 Apr 2011 14:56:46 -0700 [thread overview]
Message-ID: <4DAF569E.1040507@candelatech.com> (raw)
In-Reply-To: <20110420191403.GC18805@electric-eye.fr.zoreil.com>
On 04/20/2011 12:14 PM, Francois Romieu wrote:
> François Romieu<romieu@fr.zoreil.com> :
>> On Mon, Apr 11, 2011 at 01:09:19PM -0700, Ben Greear wrote:
>>> I notice that in kernel 2.6.38-wl, the realtek 8169 NIC doesn't
>>> report link down when in fact there is no cable connected. Instead,
> [...]
>> Thanks for the report. I'll try it tomorrow or friday.
>
> I have not been able to notice it with a current kernel.
>
> I'd welcome the XID of the 8169 NIC (see dmesg) and a short explanation
> (no cable from boot ? cable removed after ifconfig up ? brand / ability
> of the switch / hub ?).
Well, as luck would have it, my system will boot today's upstream
kernel (39-rc4+). And, I no longer see the problem in that release,
so it seems it is fixed (or harder to reproduce that I thought).
Basically, I was seeing it claim to have link in 'ethtool' output
when there was no cable connected. It did go to 10Mbps/half duplex
link speed when un-plugged. It showed full 1Gbps link when plugged
in.
I'll let you know if I see this again.
Thanks,
Ben
>
> Thanks.
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-04-20 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 20:09 r8169 doesn't report link state correctly Ben Greear
2011-04-13 17:48 ` François Romieu
2011-04-20 19:14 ` Francois Romieu
2011-04-20 21:56 ` Ben Greear [this message]
2011-04-21 15:55 ` Dan Williams
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=4DAF569E.1040507@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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.