e1000e ethernet not working on raring 13.04 (nor in precise 12.04)

[Jorge]

After an upgrade in precise, the ethernet connection started failing. The problem is that it seems to connect and receive the dhcp but the ethernet fails all the time.

WORKAROUND: sudo ethtool -s eth0 speed 10 duplex full autoneg off

Syslog:
Jul 28 13:33:16 oro-1 kernel: [ 2031.340121] e1000e: eth0 NIC Link is Down
Jul 28 13:33:17 oro-1 NetworkManager[869]: <info> (eth0): carrier now ON (device state 100)
Jul 28 13:33:17 oro-1 kernel: [ 2032.996765] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Jul 28 13:33:17 oro-1 kernel: [ 2032.996772] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
Jul 28 13:33:18 oro-1 kernel: [ 2033.968121] e1000e: eth0 NIC Link is Down
Jul 28 13:33:18 oro-1 NetworkManager[869]: <info> (eth0): carrier now OFF (device state 100, deferring action for 4 seconds)
Jul 28 13:33:20 oro-1 NetworkManager[869]: <info> (eth0): carrier now ON (device state 100)
Jul 28 13:33:20 oro-1 kernel: [ 2035.820755] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Jul 28 13:33:20 oro-1 kernel: [ 2035.820763] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
Jul 28 13:33:22 oro-1 NetworkManager[869]: <info> (eth0): carrier now OFF (device state 100, deferring action for 4 seconds)
Jul 28 13:33:22 oro-1 kernel: [ 2037.592124] e1000e: eth0 NIC Link is Down
Jul 28 13:33:24 oro-1 NetworkManager[869]: <info> (eth0): carrier now ON (device state 100)
Jul 28 13:33:24 oro-1 kernel: [ 2039.288783] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Jul 28 13:33:24 oro-1 kernel: [ 2039.288790] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
Jul 28 13:33:25 oro-1 NetworkManager[869]: <info> (eth0): carrier now OFF (device state 100, deferring action for 4 seconds)
Jul 28 13:33:25 oro-1 kernel: [ 2040.504122] e1000e: eth0 NIC Link is Down
Jul 28 13:33:27 oro-1 NetworkManager[869]: <info> (eth0): carrier now ON (device state 100)
Jul 28 13:33:27 oro-1 kernel: [ 2042.196762] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Jul 28 13:33:27 oro-1 kernel: [ 2042.196770] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
Jul 28 13:33:27 oro-1 kernel: [ 2042.704125] e1000e: eth0 NIC Link is Down
Jul 28 13:33:28 oro-1 NetworkManager[869]: <info> (eth0): carrier now OFF (device state 100, deferring action for 4 seconds)
Jul 28 13:33:29 oro-1 NetworkManager[869]: <info> (eth0): carrier now ON (device state 100)
Jul 28 13:33:29 oro-1 kernel: [ 2044.344766] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Jul 28 13:33:29 oro-1 kernel: [ 2044.344774] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO

dmesg:
[ 2013.376189] e1000e: eth0 NIC Link is Down
[ 2014.968757] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 2014.968765] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 2018.504123] e1000e: eth0 NIC Link is Down
[ 2020.124759] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 2020.124767] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 2022.188128] e1000e: eth0 NIC Link is Down
[ 2023.796761] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 2023.796769] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 2023.840120] e1000e: eth0 NIC Link is Down
[ 2025.468762] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 2025.468770] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 2026.860120] e1000e: eth0 NIC Link is Down
[ 2028.512768] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 2028.512775] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 2031.340121] e1000e: eth0 NIC Link is Down
[ 2032.996765] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 2032.996772] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 2033.968121] e1000e: eth0 NIC Link is Down

lshw
  *-network
       description: Ethernet interface
       product: 82562V-2 10/100 Network Connection
       vendor: Intel Corporation
       physical id: 19
       bus info: pci@0000:00:19.0
       logical name: eth0
       version: 02
       serial: 00:1d:09:81:db:c4
       capacity: 100Mbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.3.2-k firmware=1.1-2 ip=10.0.0.2 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:41 memory:fdfc0000-fdfdffff memory:fdfff000-fdffffff ioport:ff00(size=32)

I tried with kernels:
3.10.3-031003-generic
3.8.0-19-generic
3.8.0-21-generic (from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152194 -- http://people.canonical.com/~henrix/e1000e-pm-bug/)

None of them worked.

Also I tried with the driver from http://sourceforge.net/projects/e1000/files/e1000e%20stable/2.4.14/ and neither it worked.
https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=15817

Attachments included.

Please, could you help me?

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1205843

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Jorge (jorge-vila)]

More info:

eth0 : 00:19.0
    Make/Model = Dell Inspiron 530
    Ethernet controller = Intel Corporation 82562V-2 10/100 Network Connection
    VenID:DevID = 8086:10c0
    Driver name = e1000e
    Driver version = 2.3.2-k

[Jorge (jorge-vila)]

Hi,

I can not run apport-collect as I have no network.

I tried with apport-bug to a file, but the program fails with a utf-8 problem.

Thanks
JORGE

[Jorge (jorge-vila)]

I changed (myself, the reporter) the status to confirmed.

Please, tell me any other information you would need.

Best
JORGE

[Jorge (jorge-vila)]

More logs as requested.

Any ideas?

Thanks
JORGE

[Jorge (jorge-vila)]

Any solution to this issue? please, could you review it?

Thank you

[Jorge (jorge-vila)]

Hi,

watching: http://ubuntuforums.org/showthread.php?t=1039514

the command

sudo ethtool -s eth0 speed 10 duplex full autoneg off

made it connect at 10Mbps speed, but the router is not the problem, as other linuxes are connecting at 100Mbps speed.

Any clues?

[Jorge (jorge-vila)]

Any news on this issue?

[Po-Hsu Lin (cypressyew)]

Hello Jorge,
did you try to reinstall the e1000e driver on a new kernel you installed?
(The latest driver version is 2.5.4)

According to https://answers.launchpad.net/ubuntu-certification/+question/238609
You might need to rebuild the driver once you upgrade the kernel.

[penalvch (penalvch)]

Jorge, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Jorge (jorge-vila)]

Hi Chistopher,

sorry for the late response.

Still my pc is configure at 10 full duplex.

I could not try before as I could not update it due to other limitations.

Will try asap and give some feedback.

Thank you

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]