Bug#561843: ethtool/mii-tool report incorrect/missing values on Marvell 88E1011
Kurt Roeckx
Version: 2.6.32-2
Hi,
I get this:
# ethtool eth0 |grep -i pause
Advertised pause frame use: No
Link partner advertised pause frame use: No
# ethtool -a eth0
Pause parameters for eth0:
Autonegotiate: on
RX: on
TX: on
Those seem to conflict with each other. I assume this is a kernel
bug.
It also reports:
Link partner advertised link modes: Not reported
It would be nice that it could report it and that atleast seems
to be supported with other cards. As I understand this, this
should be supported since a 2.6.31 kernel.
It also ways:
Link partner advertised auto-negotiation: No
Auto-negotiation: on
Those also seem to conflict and it really should advertise it.
But it might be related to not reporting the link modes and
ethtool should show that instead?
On the other hand, mii-tool reports this:
# mii-tool -v
eth0: negotiated 100baseTx-FD flow-control, link ok
product info: Yukon 88E1011 rev 5
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
link partner: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
The link partner is only a 100 mbit switch, so it shouldn't
advertise 1000. It looks like the 2 last lines are switched.
lspci -v says:
00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
Subsystem: ASUSTeK Computer Inc. Marvell 88E8001 Gigabit Ethernet Controller (Asus)
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17
Memory at fdd00000 (32-bit, non-prefetchable) [size=16K]
I/O ports at b000 [size=256]
Expansion ROM at fdc00000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Kernel driver in use: skge
Kurt
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Kurt Roeckx
> On the other hand, mii-tool reports this:
> # mii-tool -v
> eth0: negotiated 100baseTx-FD flow-control, link ok
> product info: Yukon 88E1011 rev 5
> basic mode: autonegotiation enabled
> basic status: autonegotiation complete, link ok
> capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
> advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
> link partner: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
>
> The link partner is only a 100 mbit switch, so it shouldn't
> advertise 1000. It looks like the 2 last lines are switched.
This part is part is probably #511395
Ben Hutchings
> Source: linux-2.6
> Version: 2.6.32-2
>
> Hi,
>
> I get this:
> # ethtool eth0 |grep -i pause
> Advertised pause frame use: No
> Link partner advertised pause frame use: No
> # ethtool -a eth0
> Pause parameters for eth0:
> Autonegotiate: on
> RX: on
> TX: on
>
> Those seem to conflict with each other. I assume this is a kernel
> bug.
Driver bug. A lot of drivers do not report specific pause frame
auto-negotiation flags.
> It also reports:
> Link partner advertised link modes: Not reported
>
> It would be nice that it could report it and that atleast seems
> to be supported with other cards. As I understand this, this
> should be supported since a 2.6.31 kernel.
It depends on the driver. I provided patches for the generic MII code
but many drivers do not use that and do not yet provide any information
about link partner advertising.
> It also ways:
> Link partner advertised auto-negotiation: No
> Auto-negotiation: on
>
> Those also seem to conflict and it really should advertise it.
[...]
No, "Auto-negotiation: on" does not mean auto-negotiation was
successful.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
Kurt Roeckx
> > It also ways:
> > Link partner advertised auto-negotiation: No
> > Auto-negotiation: on
> >
> > Those also seem to conflict and it really should advertise it.
> [...]
>
> No, "Auto-negotiation: on" does not mean auto-negotiation was
> successful.
But the link parter does support auto-negotiation, while
it says no.
Ben Hutchings
> On Sun, Dec 20, 2009 at 04:54:42PM +0000, Ben Hutchings wrote:
> > > It also ways:
> > > Link partner advertised auto-negotiation: No
> > > Auto-negotiation: on
> > >
> > > Those also seem to conflict and it really should advertise it.
> > [...]
> >
> > No, "Auto-negotiation: on" does not mean auto-negotiation was
> > successful.
>
> But the link parter does support auto-negotiation, while
> it says no.
That's really a bug in ethtool; it should say "not reported". I'll
submit a patch.
Moritz Muehlenhoff
thanks
On Sun, Dec 20, 2009 at 06:55:27PM +0000, Ben Hutchings wrote:
> On Sun, 2009-12-20 at 19:36 +0100, Kurt Roeckx wrote:
> > On Sun, Dec 20, 2009 at 04:54:42PM +0000, Ben Hutchings wrote:
> > > > It also ways:
> > > > Link partner advertised auto-negotiation: No
> > > > Auto-negotiation: on
> > > >
> > > > Those also seem to conflict and it really should advertise it.
> > > [...]
> > >
> > > No, "Auto-negotiation: on" does not mean auto-negotiation was
> > > successful.
> >
> > But the link parter does support auto-negotiation, while
> > it says no.
>
> That's really a bug in ethtool; it should say "not reported". I'll
> submit a patch.
You patch has been merged and it present in the 2.6.34 from unstable.
Reassigning, I'll leave it to ethtool maintainers to actually close it.
Cheers,
Moritz
Kurt Roeckx
> reassign 561843 ethtool
> thanks
>
> On Sun, Dec 20, 2009 at 06:55:27PM +0000, Ben Hutchings wrote:
> > On Sun, 2009-12-20 at 19:36 +0100, Kurt Roeckx wrote:
> > > On Sun, Dec 20, 2009 at 04:54:42PM +0000, Ben Hutchings wrote:
> > > > > It also ways:
> > > > > Link partner advertised auto-negotiation: No
> > > > > Auto-negotiation: on
> > > > >
> > > > > Those also seem to conflict and it really should advertise it.
> > > > [...]
> > > >
> > > > No, "Auto-negotiation: on" does not mean auto-negotiation was
> > > > successful.
> > >
> > > But the link parter does support auto-negotiation, while
> > > it says no.
> >
> > That's really a bug in ethtool; it should say "not reported". I'll
> > submit a patch.
>
> You patch has been merged and it present in the 2.6.34 from unstable.
>
> Reassigning, I'll leave it to ethtool maintainers to actually close it.
I don't get why you've reassigned this to ethool in the first
place. There were several issues I've reported with the driver,
and 1 with ethtool. Afaik, ethtool has been fixed a long time
ago.
But I don't know about the driver issue. I will look at this when
I get back from debconf.
Kurt