Interface eth0 not often detected at boot

[Ricardo de Barros]

My cabled interface is not properly configured in the kernel when i use my laptop outside its docking station.
The interface seems to appear in the kernel but for example, ethtool can't use it and when I plug in a cable no packets flow at all.

lisrferre@por0003n:/mnt/repository/dump$ dmesg | grep eth0
[ 1.122912] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 50:26:90:a5:73:0d
[ 1.122916] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 1.122955] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
[ 6.880747] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 24.671414] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 24.671689] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
lisrferre@por0003n:/mnt/repository/dump$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 50:26:90:a5:73:0d
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:17 Memory:e2700000-e2720000

lisrferre@por0003n:/mnt/repository/dump$ sudo ethtool eth0
[sudo] password for lisrferre:
Settings for eth0:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available

[ 24.189718] netlink: 12 bytes leftover after parsing attributes.
[ 24.189723] netlink: 12 bytes leftover after parsing attributes.
[ 24.189754] netlink: 12 bytes leftover after parsing attributes.
[ 24.189791] netlink: 12 bytes leftover after parsing attributes.
[ 24.568097] e1000e 0000:00:19.0: irq 47 for MSI/MSI-X
[ 24.671145] e1000e 0000:00:19.0: irq 47 for MSI/MSI-X
[ 24.671414] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 24.671689] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 24.712834] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

[ 27.413930] ipmi message handler version 39.2
[ 27.440197] IPMI System Interface driver.
[ 27.440220] ipmi_si: Adding default-specified kcs state machine
[ 27.440222] ipmi_si: Trying default-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
[ 27.440226] ipmi_si: Interface detection failed
[ 27.441233] ipmi_si: Adding default-specified smic state machine
[ 27.441236] ipmi_si: Trying default-specified smic state machine at i/o address 0xca9, slave address 0x0, irq 0
[ 27.441239] ipmi_si: Interface detection failed
[ 27.444786] ipmi_si: Adding default-specified bt state machine
[ 27.444788] ipmi_si: Trying default-specified bt state machine at i/o address 0xe4, slave address 0x0, irq 0
[ 27.444792] ipmi_si: Interface detection failed
[ 27.448787] ipmi_si: Unable to find any System Interface(s)

lisrferre@por0003n:~$ cat /proc/version_signature
Ubuntu 3.8.0-19.30-generic 3.8.8

I noticed this strange trace in the kernel log

May 9 09:53:49 por0003n kernel: [ 10.572560] Call Trace:
May 9 09:53:49 por0003n kernel: [ 10.572570] [<ffffffffa05e0002>] ? hdmi_pcm_open+0xa2/0x1e0 [snd_hda_codec_hdmi]
May 9 09:53:49 por0003n kernel: [ 10.572600] [<ffffffffa0504186>] snd_hda_codec_configure+0x146/0x440 [snd_hda_codec]
May 9 09:53:49 por0003n kernel: [ 10.572629] [<ffffffffa05282f0>] azx_probe_continue+0x3a0/0x4f0 [snd_hda_intel]
May 9 09:53:49 por0003n kernel: [ 10.572656] [<ffffffffa05268b0>] ? azx_attach_pcm_stream+0x1e0/0x1e0 [snd_hda_intel]
May 9 09:53:49 por0003n kernel: [ 10.572683] [<ffffffffa0527cb0>] ? azx_halt+0x30/0x30 [snd_hda_intel]
May 9 09:53:49 por0003n kernel: [ 10.572707] [<ffffffffa05266d0>] ? azx_pcm_trigger+0x580/0x580 [snd_hda_intel]
May 9 09:53:49 por0003n kernel: [ 10.572733] [<ffffffffa0527810>] ? azx_runtime_suspend+0x30/0x30 [snd_hda_intel]
May 9 09:53:49 por0003n kernel: [ 10.572759] [<ffffffffa0524670>] ? azx_pcm_free+0x50/0x50 [snd_hda_intel]
May 9 09:53:49 por0003n kernel: [ 10.572784] [<ffffffffa052879a>] azx_probe+0x35a/0x940 [snd_hda_intel]
May 9 09:53:49 por0003n kernel: [ 10.572808] [<ffffffff8137b4cb>] local_pci_probe+0x4b/0x80
May 9 09:53:49 por0003n kernel: [ 10.572828] [<ffffffff8137b7f1>] pci_device_probe+0x111/0x120
May 9 09:53:49 por0003n kernel: [ 10.572850] [<ffffffff81455717>] driver_probe_device+0x77/0x230
May 9 09:53:49 por0003n kernel: [ 10.572871] [<ffffffff8145597b>] __driver_attach+0xab/0xb0
May 9 09:53:49 por0003n kernel: [ 10.572890] [<ffffffff814558d0>] ? driver_probe_device+0x230/0x230
May 9 09:53:49 por0003n kernel: [ 10.572912] [<ffffffff81453a2d>] bus_for_each_dev+0x5d/0xa0
May 9 09:53:49 por0003n kernel: [ 10.572932] [<ffffffff8145521e>] driver_attach+0x1e/0x20
May 9 09:53:49 por0003n kernel: [ 10.572950] [<ffffffff81454df0>] bus_add_driver+0x190/0x280
May 9 09:53:49 por0003n kernel: [ 10.572971] [<ffffffffa052f000>] ? 0xffffffffa052efff
May 9 09:53:49 por0003n kernel: [ 10.572989] [<ffffffff81456047>] driver_register+0x77/0x170
May 9 09:53:49 por0003n kernel: [ 10.574003] [<ffffffffa052f000>] ? 0xffffffffa052efff
May 9 09:53:49 por0003n kernel: [ 10.575007] [<ffffffff8137a6bc>] __pci_register_driver+0x4c/0x50
May 9 09:53:49 por0003n kernel: [ 10.575997] [<ffffffffa052f01e>] azx_driver_init+0x1e/0x1000 [snd_hda_intel]
May 9 09:53:49 por0003n kernel: [ 10.576985] [<ffffffff8100215a>] do_one_initcall+0x12a/0x180
May 9 09:53:49 por0003n kernel: [ 10.577941] [<ffffffff810bff17>] load_module+0x10c7/0x1520
May 9 09:53:49 por0003n kernel: [ 10.578861] [<ffffffff810bb880>] ? unset_module_init_ro_nx+0x80/0x80
May 9 09:53:49 por0003n kernel: [ 10.579751] [<ffffffff810c0435>] sys_init_module+0xc5/0xf0
May 9 09:53:49 por0003n kernel: [ 10.580611] [<ffffffff816d37dd>] system_call_fastpath+0x1a/0x1f
May 9 09:53:49 por0003n kernel: [ 10.581434] Code: 0f 1f 00 4d 8b bc 24 c0 00 00 00 25 00 e0 00 00 c1 e8 0c 83 c8 01 49 63 17 83 c0 01 83 f8 10 48 8d 14 92 49 8d 14 d7 48 8d 72 08 <66> 89 5a 08 c7 46 08 02 00 00 00 0f 86 5b 02 00 00 48 8d 4e 18
May 9 09:53:49 por0003n kernel: [ 10.583268] RIP [<ffffffffa05e1820>] patch_generic_hdmi+0xe0/0x550 [snd_hda_codec_hdmi]
May 9 09:53:49 por0003n kernel: [ 10.584180] RSP <ffff880121f45ac0>
May 9 09:53:49 por0003n kernel: [ 10.585064] CR2: ffff88012536ffe0
May 9 09:53:49 por0003n kernel: [ 10.596938] ---[ end trace 49ed9769a2f2a0ea ]---

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-19-generic 3.8.0-19.30
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Thu May 9 10:04:40 2013
HibernationDevice: RESUME=UUID=b92854ad-9326-4eaf-8e5e-0c269f335ba6
InstallationDate: Installed on 2012-07-25 (287 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: FUJITSU LIFEBOOK S761
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic root=/dev/mapper/vg0-lv_root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-04-30 (8 days ago)
dmi.bios.date: 06/20/2012
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.19
dmi.board.name: FJNB225
dmi.board.vendor: FUJITSU
dmi.board.version: D1
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: LIFEBOOK S761
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd06/20/2012:svnFUJITSU:pnLIFEBOOKS761:pvr10601409691:rvnFUJITSU:rnFJNB225:rvrD1:cvnFUJITSU:ct10:cvrLIFEBOOKS761:
dmi.product.name: LIFEBOOK S761
dmi.product.version: 10601409691
dmi.sys.vendor: FUJITSU

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-saucy/

[Ricardo de Barros (stealthymarine)]

Sorry, but the latest kernel has still not fixed this problem

lisrferre@por0003n:/mnt/repository/firmware/BROCADE$ sudo ifconfig eth0
[sudo] password for lisrferre:
eth0 Link encap:Ethernet HWaddr 50:26:90:a5:73:0d
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:17 Memory:e2700000-e2720000

lisrferre@por0003n:/mnt/repository/firmware/BROCADE$ sudo ethtool eth0
Settings for eth0:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available
lisrferre@por0003n:/mnt/repository/firmware/BROCADE$ uname -a^C
lisrferre@por0003n:/mnt/repository/firmware/BROCADE$ cd /
lisrferre@por0003n:/$ sudo ifconfig eth0
eth0 Link encap:Ethernet HWaddr 50:26:90:a5:73:0d
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:17 Memory:e2700000-e2720000

lisrferre@por0003n:/$ sudo ethtool eth0
Settings for eth0:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available
lisrferre@por0003n:/$ uname -a
Linux por0003n 3.9.0-030900-generic #201305071030 SMP Tue May 7 14:32:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
lisrferre@por0003n:/$ ^C
lisrferre@por0003n:/$

[Ricardo de Barros (stealthymarine)]

When I sit the laptop into the dock, ethtool already lists the interface correctly. I should add that this was working with the previous Ubuntu version

[Luis Henriques (henrix)]

This could be related with the e1000e driver power management bug that was present in the 3.8 (raring) kernel. Basically, the ethernet card couldn't detect carrier signal if it was on deep sleep state (e.g., the laptop was on battery, not on AC).

 I've uploaded a test kernel here: http://people.canonical.com/~henrix/e1000e-pm-bug/
Basically, it contains the fix for the e1000e PM issue. This fix is already in Raring kernel master-next branch, and should be released soon.

[Ricardo de Barros (stealthymarine)]

I'm sorry, but still not fixed for me with the kernel you specified:

lisrferre@por0003n:~/Downloads$ sudo ethtool eth0
[sudo] password for lisrferre:
Sorry, try again.
[sudo] password for lisrferre:
Settings for eth0:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available
lisrferre@por0003n:~/Downloads$ uname -a
Linux por0003n 3.8.0-21-generic #32~e1000epmbug SMP Wed May 22 14:13:22 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
lisrferre@por0003n:~/Downloads$ dmesg | grep eth0
[ 1.117600] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 50:26:90:a5:73:0d
[ 1.117603] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 1.117640] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
[ 8.425203] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 25.042826] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 25.043109] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
lisrferre@por0003n:~/Downloads$

I'm on battery of course.

[Ricardo de Barros (stealthymarine)]

This one fixed it.

lisrferre@por0003n:~/Downloads$ sudo ethtool eth0
[sudo] password for lisrferre:
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: No
        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: Unknown!
        Duplex: Unknown! (255)
        Port: Twisted Pair
        PHYAD: 2
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: pumbg
        Wake-on: d
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: no
lisrferre@por0003n:~/Downloads$ uname -a
Linux por0003n 3.8.13-030813-generic #201305111843 SMP Sat May 11 22:44:40 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux