Ubuntu
linux package

NetworkManager fails to detect link status change -- Intel 82577LM e1000e

Bug #1098298 reported by Alexander List on 2013-01-10

This bug affects 9 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	Undecided	Unassigned

Bug Description

Steps to reproduce:

1.) Start Ubuntu, with LAN plugged in, login
2.) Verify NetworkManager detects the Wired Connection
3.) stop NetworkManager
4.) unplug LAN cable
5.) start NetworkManager
Result: NetworkManager doesn't detect that eth0 is not in the RUNNING state

Plugging in LAN cable doesn't change state either, i.e. eth0 remains unconfigured.

-----

## unplug network cable

root@thinkpad:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:26:2d:f6:06:8b
          inet addr:10.201.4.52 Bcast:10.201.7.255 Mask:255.255.252.0
          inet6 addr: fe80::226:2dff:fef6:68b/64 Scope:Link
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:17695 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14813 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:17180328 (17.1 MB) TX bytes:3811166 (3.8 MB)
          Interrupt:20 Memory:f2500000-f2520000

## dmesg:

[ 894.264179] init: network-manager main process (6194) killed by KILL signal
[ 899.925268] e1000e: eth0 NIC Link is Down

root@thinkpad:~# service network-manager start
network-manager start/running, process 7702
# nm-tool
[...]
- Device: eth0 [Wired connection 1] -------------------------------------------
  Type: Wired
  Driver: e1000e
  State: connecting (getting IP configuration)
  Default: no
  HW Address: 00:26:2D:F6:06:8B

Capabilities:

Wired Properties
Carrier: on

# dmesg:
[ 1043.488154] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1046.290181] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1046.290428] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

root@thinkpad:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:26:2d:f6:06:8b
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:17695 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14813 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:17180328 (17.1 MB) TX bytes:3811166 (3.8 MB)
          Interrupt:20 Memory:f2500000-f2520000

## plug in network cable

root@thinkpad:~# service network-manager stop
network-manager stop/waiting
root@thinkpad:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:26:2d:f6:06:8b
          inet addr:10.201.4.52 Bcast:10.201.7.255 Mask:255.255.252.0
          inet6 addr: fe80::226:2dff:fef6:68b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:17695 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14813 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:17180328 (17.1 MB) TX bytes:3811166 (3.8 MB)
          Interrupt:20 Memory:f2500000-f2520000
## unplug network cable
root@thinkpad:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:26:2d:f6:06:8b
          inet addr:10.201.4.52 Bcast:10.201.7.255 Mask:255.255.252.0
          inet6 addr: fe80::226:2dff:fef6:68b/64 Scope:Link
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:17695 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14813 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:17180328 (17.1 MB) TX bytes:3811166 (3.8 MB)
          Interrupt:20 Memory:f2500000-f2520000

## dmesg:

[ 894.264179] init: network-manager main process (6194) killed by KILL signal
[ 899.925268] e1000e: eth0 NIC Link is Down

Capabilities:

Wired Properties
Carrier: on

## plug in network cable
[ 1142.125629] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1187.240780] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1248.621854] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
[ 1248.624418] e1000e 0000:00:19.0: eth0: PHY Wakeup cause - Link Status Change
[ 1251.846511] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[ 1251.848190] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

root@thinkpad:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:26:2d:f6:06:8b
          inet6 addr: fe80::226:2dff:fef6:68b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:17755 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14829 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:17186538 (17.1 MB) TX bytes:3814930 (3.8 MB)
          Interrupt:20 Memory:f2500000-f2520000

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: network-manager 0.9.6.0-0ubuntu7
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
Date: Thu Jan 10 19:05:48 2013
InstallationDate: Installed on 2012-11-17 (54 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1
eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.6.0 connected enabled enabled enabled enabled disabled

See original description

Tags:

Revision history for this message

Alexander List (alexlist) wrote on 2013-01-10:

CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (7.4 KiB, text/plain; charset="utf-8")
IfupdownConfig.txt Edit (425 bytes, text/plain; charset="utf-8")
IpAddr.txt Edit (1.3 KiB, text/plain; charset="utf-8")
IpRoute.txt Edit (391 bytes, text/plain; charset="utf-8")
IwConfig.txt Edit (576 bytes, text/plain; charset="utf-8")
NetDevice.eth0.txt Edit (439 bytes, text/plain; charset="utf-8")
NetDevice.lo.txt Edit (206 bytes, text/plain; charset="utf-8")
NetDevice.lxcbr0.txt Edit (236 bytes, text/plain; charset="utf-8")
NetDevice.virbr0.txt Edit (236 bytes, text/plain; charset="utf-8")
NetDevice.wlan0.txt Edit (487 bytes, text/plain; charset="utf-8")
NetworkManager.conf.txt Edit (69 bytes, text/plain; charset="utf-8")
PciNetwork.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (106 bytes, text/plain; charset="utf-8")
RfKill.txt Edit (250 bytes, text/plain; charset="utf-8")
WifiSyslog.txt Edit (935.0 KiB, text/plain; charset="utf-8")
nmcli-con.txt Edit (4.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Thomas Hood (jdthood) wrote on 2013-01-14:

Possibly a driver issue

summary:	- network-manager fails to detect link status change + NetworkManager fails to detect link status change -- Intel 82577LM + e1000e
description:	updated
affects:	network-manager (Ubuntu) → linux (Ubuntu)

Revision history for this message

Brad Figg (brad-figg) wrote on 2013-01-14: Missing required logs.

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

apport-collect 1098298

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.

Changed in linux (Ubuntu):
status:	New → Incomplete

Revision history for this message

Tobias Wolf (towolf) wrote on 2013-02-17:

I see this too. NM stuck at "unplugged".

The thing is I only load e1000e on demand with modprobe because I normally don't need Ethernet and want to conserve the few milliwatts it's using when loaded.

So now when I load the module dmesg and NM never pick up link state. mii-tool does though.

Revision history for this message

arnuschky (abrutschy) wrote on 2013-03-12:

I have the same issue with a 82567LM on my Lenovo X200.

Network-manager randomly connects a wired connection set to "connect automatically". Disabling auto connect on all wired connections remove the problem of nm setting the wrong IP, but now it's constantly trying to connect -> fails ->trying to connect -> fails...

dmesg shows:
[206824.607644] ADDRCONF(NETDEV_UP): eth0: link is not ready
[206824.868925] ADDRCONF(NETDEV_UP): eth0: link is not ready
[206829.454837] ADDRCONF(NETDEV_UP): eth0: link is not ready
[206829.615378] ADDRCONF(NETDEV_UP): eth0: link is not ready
[206902.098256] ADDRCONF(NETDEV_UP): eth0: link is not ready
(and many more)

sudo modprobe -r e1000e solved the problem for me

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-05-12:

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

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

penalvch (penalvch) wrote on 2013-08-03:

Alexander List, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, 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 following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. 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.11-rc3

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

tags:	added: needs-kernel-logs needs-upstream-testing
Changed in linux (Ubuntu):
status:	Expired → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-10-03:

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

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

NetworkManager fails to detect link status change -- Intel 82577LM e1000e

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package