lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 4 Jun 2010 00:20:24 +0200
From:	David Härdeman <david@...deman.nu>
To:	netdev@...r.kernel.org
Cc:	jesse.brandeburg@...el.com
Subject: e1000e driver, Intel 82567LF-2, link negotiation (and wol) problems

I have an Intel DG45FC motherboard with an integrated gigabit NIC (lspci 
says it's a "Intel Corporation 82567LF-2 Gigabit Network Connection").

When using the in-kernel e1000e driver (tried up to kernel version 
2.6.34), the speed is negotiated to 100mbit (most of the time) even 
though the NIC is connected to a gigabit switch using quality cables 
(I've tried a few different to be sure).  There seems to be no real 
pattern to when the link is negotiated to 100mbit or 1000mbit.

I've tried Intel's version of the driver (e1000e from sourceforge, 
version 1.1.19) and it seems to behave in the same way.

The output from mii-tool is quite confusing:
scott:~# mii-tool -v eth0
SIOCGMIIREG on eth0 failed: Input/output error
SIOCGMIIREG on eth0 failed: Input/output error
eth0: negotiated 100baseTx-FD flow-control, link ok
  product info: vendor 00:50:43, model 11 rev 0
  basic mode:   autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 
10baseT-HD
  advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD 
flow-control
  link partner: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 
10baseT-HD flow-control

(capabilities and link partner agree on 1000mbit, but only 100mbit is 
advertised according to mii-tool)

ethtool disagrees with mii-tool:
scott:~# ethtool eth0
Settings for eth0:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 100baseT/Half 
100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes
	Advertised link modes:  10baseT/Half 10baseT/Full 100baseT/Half 
100baseT/Full 1000baseT/Full Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Speed: 100Mb/s
	Duplex: Full
	Port: Twisted Pair
	PHYAD: 2
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: on
	Supports Wake-on: pumbag
	Wake-on: g
	Current message level: 0x00000001 (1)
	Link detected: yes

Manually setting the speed with ethtool doesn't work. Not sure how to 
proceed...any suggestions?

(And while I'm at it, the Intel e1000e driver from sourceforge seems to 
have a wol init bug, ethtool reports "Wake-on: g" but I can wake a 
suspended machine using a simple ping. Calling "ethtool -s eth0 wol g" 
before suspending gets the expected behaviour - i.e. only wake on a 
magic wol packet. Don't want to register on sourceforge just to report 
that to the bug tracker though).

Not subscribed to netdev, please CC me on any answers.

-- 
David Härdeman
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists