From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>, netdev@vger.kernel.org
Cc: "afleming@freescale.com" <afleming@freescale.com>,
"macro@linux-mips.org" <macro@linux-mips.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: drivers/net/phy/phy.c issue
Date: Wed, 8 Feb 2012 11:30:20 -0800 [thread overview]
Message-ID: <1328729420.2261.329.camel@groeck-laptop> (raw)
In-Reply-To: <CACW_hTY41xZV6d0W2Z2kRfKOfa+RSQ-A-BoZsZwNXSQmeF_6Gg@mail.gmail.com>
Copying netdev.
On Wed, 2012-02-08 at 09:31 -0500, Frans Meulenbroeks wrote:
> Hi
>
> I found an issue with drivers/net/phy/phy.c
> As I could not identify a maintainer for this file I decided to mail
> it to the above addressees.
> Apologies upfront if it is inappropriate.
>
> The issue:
>
> My network interface was configured as 10Mbit, full duplex, autonegotiate off.
> If the cable is unplugged after 10 seconds or so the interface drops
> to half duplex and the message:
> Trying 10/HALF
> is printed. This message comes (if I am correct from the function
> phy_force_reduction in drivers/net/phy/phy.c
>
> Maybe this is still ok, however if I reconnect my network cable the
> interface remains configured as 10 Mbit, half duplex.
> I had expected/assumed that it would go back to 10 Mbit, full duplex.
>
> If I try the same with a 1Gbit full duplex link with autonegotiate on,
> the link also drops to half duplex whenever the cable is
> disconnected. However reconnecting the cable then brings the interface
> back to full duplex again.
>
> Not sure what is wrong (if the interface should not be dropped to half
> or get back to full) and even less an idea how to fix it,
> but wanted to report it anyway, in the hope someone can shed a light
> on this and/or fix it.
>
What is your kernel version ? No idea if it makes a difference, but I
strongly suspect people will need to know.
Guenter
> Best regards, Frans.
>
> PS: I'm not on lkml (way too much mails for me), so please keep me on Cc
next prev parent reply other threads:[~2012-02-08 19:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 14:31 drivers/net/phy/phy.c issue Frans Meulenbroeks
2012-02-08 19:30 ` Guenter Roeck [this message]
2012-02-08 20:00 ` Frans Meulenbroeks
2012-02-08 21:05 ` guenter
2012-02-09 8:12 ` Frans Meulenbroeks
2012-02-09 13:06 ` Guenter Roeck
2012-02-09 14:13 ` Frans Meulenbroeks
2012-02-08 19:34 ` Andy Fleming
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=1328729420.2261.329.camel@groeck-laptop \
--to=guenter.roeck@ericsson.com \
--cc=afleming@freescale.com \
--cc=fransmeulenbroeks@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.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;
as well as URLs for NNTP newsgroup(s).