1969:1083 NetworkManager does not connect eth0 -- atl1c

[Frank Denissen]

NetworkManager does not start eth0 when /etc/network/interfaces only contains "lo auto", " iface lo inet loopback" and "eth0 auto".

The connection only comes available when /etc/network/interfaces contains additionally "iface eth0 inet dhcp".
On other systems I have there is no problem.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
CRDA: Error: [Errno 2] Bestand of map bestaat niet
Date: Thu Jun 28 19:08:06 2012
IpRoute:
 default via 192.168.0.1 dev eth0 metric 100
 169.254.0.0/16 dev eth0 scope link metric 1000
 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.25
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=nl_BE:nl
 TERM=xterm
 LANG=nl_BE.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9:
 ** (process:8693): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Rejected send message, 2 matched rules; type="method_call", sender=":1.19" (uid=1000 pid=8693 comm="nmcli -f all con ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1953 comm="NetworkManager ")
 Error: nmcli (0.9.4.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
nmcli-dev:
 Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 9:
 ** (process:8692): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Rejected send message, 2 matched rules; type="method_call", sender=":1.18" (uid=1000 pid=8692 comm="nmcli -f all dev ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1953 comm="NetworkManager ")
 Error: nmcli (0.9.4.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
nmcli-nm:
 Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 9:
 ** (process:8691): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Rejected send message, 2 matched rules; type="method_call", sender=":1.17" (uid=1000 pid=8691 comm="nmcli -f all nm ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1953 comm="NetworkManager ")
 Error: nmcli (0.9.4.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: frank 5255 F.... pulseaudio
CRDA: Error: [Errno 2] Bestand of map bestaat niet
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xdf000000 irq 57'
   Mixer name : 'Realtek ALC663'
   Components : 'HDA:10ec0663,10431b73,00100001'
   Controls : 23
   Simple ctrls : 12
CurrentDmesg:
 [ 32.580233] eth0: no IPv6 routers present
 [ 34.843534] [drm] nouveau 0000:01:00.0: unknown i2c port 54
 [ 56.919623] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=992ca05f-b4b9-4a2b-b82a-512cf8251ec9
MachineType: ASUSTeK Computer Inc. N55SF
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=nl_BE:nl
 TERM=xterm
 PATH=(custom, no user)
 LANG=nl_BE.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-26-generic root=/dev/mapper/vga-precise_amd64 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-26-generic N/A
 linux-backports-modules-3.2.0-26-generic N/A
 linux-firmware 1.79
SourcePackage: linux
StagingDrivers: mei
Tags: precise staging precise staging
Uname: Linux 3.2.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N55SF.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N55SF
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN55SF.206:bd08/23/2011:svnASUSTeKComputerInc.:pnN55SF:pvr1.0:rvnASUSTeKComputerInc.:rnN55SF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: N55SF
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Thomas Hood (jdthood)]

Your /etc/NetworkManager/NetworkManager.conf contains

    [ifupdown]
    managed=false

In that case, as I understand it, ifupdown will be left in control of interfaces defined in /e/n/i. NM interprets the "auto eth0" as meaning that eth0 should be under ifupdown control, but that line alone is not enough to make ifup do anything with eth0. So eth0 is not brought up.

[Frank Denissen (aankoopdenissen)]

Thanks for the hint.

I have changed managed to true in NetworkManager.conf, commented out the "iface eth0 inet dhcp" line and rebooted, but the problem stays.

If I uncomment again the "iface eth0 inet dhcp" line then eth0 gets connected and the "fixed line connected" appears. The network manager applet indicates that eth0 is under ifup control.

[Thomas Hood (jdthood)]

What if you comment out both "auto eth0" and "iface eth0 inet dhcp"? Does NM configure eth0 then?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Frank Denissen (aankoopdenissen)]

I have commented out both "auto eth0" and "iface eth0 inet dhcp": problem remains. In attachment the NetworkManager logs.

I have compared with diff NetworkManager.conf with the one on my desktop PC (where everything works) and it is identical: both managed=true.

So I don't have any clue while the NetworkManager connects on the (older) desktop and does not connect on the (newer) laptop.

[Thomas Hood (jdthood)]

What I meant was:

What if you comment out both "auto eth0" and "iface eth0 inet dhcp" and set managed=false in NetworkManager.conf? Does NM configure eth0 then?

[Frank Denissen (aankoopdenissen)]

No it does not.

For me it is not a big problem: with "auto eth0" en "iface eth0 inet dhcp" in /etc/network/interfaces I have a working fixed ethernet connection and with "managed=true" in NetworkManager.conf even the icon on the NetworkManager applet is OK. The only thing is that it does not work the way it is supposed to work (as far as I know)

[Thomas Hood (jdthood)]

So the only problem is that eth0 doesn't get configured if /etc/network/interfaces is missing the line "iface eth0 inet dhcp"? And that it fails to get configured both with managed=true and managed=false?

Or is there some other problem in addition to this?

[Thomas Hood (jdthood)]

In any case, let's deal with the (main) problem. When eth0 is not mentioned in /e/n/i, NM should configure it regardless of the "managed" setting. But in Frank's case that doesn't happen. In Frank's log (NM 0.9.4.0-0ubuntu4.1) we see:

Jun 26 13:50:17 zwaluw NetworkManager[1772]: <info> (eth0): carrier is OFF
Jun 26 13:50:17 zwaluw NetworkManager[1772]: <info> (eth0): new Ethernet device (driver: 'atl1c' ifindex: 2)
Jun 26 13:50:17 zwaluw NetworkManager[1772]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Jun 26 13:50:17 zwaluw NetworkManager[1772]: <info> (eth0): now managed
Jun 26 13:50:17 zwaluw NetworkManager[1772]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jun 26 13:50:17 zwaluw NetworkManager[1772]: <info> (eth0): bringing up device.
Jun 26 13:50:17 zwaluw NetworkManager[1772]: <info> (eth0): carrier now ON (device state 20)
Jun 26 13:50:17 zwaluw NetworkManager[1772]: <info> (eth0): preparing device.
Jun 26 13:50:17 zwaluw NetworkManager[1772]: <info> (eth0): deactivating device (reason 'managed') [2]
Jun 26 13:50:17 zwaluw kernel: [ 24.667139] atl1c 0000:05:00.0: irq 57 for MSI/MSI-X
Jun 26 13:50:17 zwaluw kernel: [ 24.667253] atl1c 0000:05:00.0: atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>
Jun 26 13:50:17 zwaluw NetworkManager[1772]: <info> (eth0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]

For comparison, here's what I see on my laptop where eth0 gets configured by NM quantal (0.9.4.0+git201206081144.2efeac8-0ubuntu1):

Jun 28 10:03:40 tenerife kernel: [ 23.112806] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X
Jun 28 10:03:40 tenerife kernel: [ 23.113317] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 28 10:03:40 tenerife kernel: [ 23.113549] ADDRCONF(NETDEV_UP): eth0: link is not ready
[...]
Jun 28 10:03:44 tenerife NetworkManager[1017]: <info> (eth0): carrier now ON (device state 20)
Jun 28 10:03:44 tenerife NetworkManager[1017]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Jun 28 10:03:44 tenerife NetworkManager[1017]: <info> Auto-activating connection 'Wired connection 1'.
Jun 28 10:03:44 tenerife NetworkManager[1017]: <info> Activation (eth0) starting connection 'Wired connection 1'
Jun 28 10:03:44 tenerife NetworkManager[1017]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun 28 10:03:44 tenerife NetworkManager[1017]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 28 10:03:44 tenerife NetworkManager[1017]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jun 28 10:03:44 tenerife NetworkManager[1017]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jun 28 10:03:44 tenerife NetworkManager[1017]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jun 28 10:03:44 tenerife NetworkManager[1017]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jun 28 10:03:44 tenerife NetworkManager[1017]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Jun 28 10:03:44 tenerife NetworkManager[1017]: <info> Ac...

[Frank Denissen (aankoopdenissen)]

I'm thinking it has to be related to hardware or the kernel module of eth0.
I have 3 PC's running identical software (Kubuntu Precise complete up to date):
- 1 older laptop
- 1 older desktop
- 1 brand-new laptop

The install was for all three a clean install: no upgrade from the previous release. The home directories were of course preserved.

Only the brand-new laptop has problems.

For the others is managed=false in NetworkManager.conf and network/interfaces only contains auto eth0 and eth0 comes up properly.

To make the thing even more strange: the brand-new PC was previously running lucid-i386 with the backported oneiric kernel (because the driver for eth0 was not supported by the lucid kernel) and then the settings were managed=false in NetworkManager/nm-system-settings.conf and eth0 was not mentioned at all in /etc/network/interfaces. eth0 did in lucid connect without problems.

[Thomas Hood (jdthood)]

> For the others is managed=false in NetworkManager.conf and
> network/interfaces only contains auto eth0 and eth0 comes
> up properly.

I presume that it is NM that brings up eth0 in that case. So it seems that NM *does* realize that "auto eth0" alone isn't enough to count eth0 as being under ifupdown's control. So what I hypothesized in #4 was wrong. That's good to know.

Yes, I'd guess that the present issue is related to the driver, atl1c.

[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.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

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.5-rc7-quantal/

[Frank Denissen (aankoopdenissen)]

Tested on mainstream kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc7-quantal/ and the problem still exists.
Removed tag kernel-unable-to-test-upstream and added kernel-bug-exists-upstream

[penalvch (penalvch)]

Frank Denissen, thank you for reporting this and helping make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1018933
As well, does this problem occur in a prior version of Ubuntu?

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

apport information

[Frank Denissen (aankoopdenissen)]

The problem did not occur on lucid-i386 with linux-image-generic-pae-lts-backport-oneiric (I needed this kernel to able to use the ethernet interface).

[penalvch (penalvch)]

Frank Denissen, does https://launchpad.net/ubuntu/+source/linux-meta work for you in Precise?

[Frank Denissen (aankoopdenissen)]

I don't understand your question. I installed the packages from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc7-quantal/, rebooted and the problem still exists.

Is there something more I have to try ?

[penalvch (penalvch)]

Frank Denissen, https://launchpad.net/ubuntu/+source/linux-meta is a link on Launchpad that displays the driver backport package. What I want you to try is the linux-backports-modules-headers-precise-generic package in Precise, mentioned in that link, to see if this provides you a working driver in Precise, in comparison to the linux-image-generic-pae-lts-backport-oneiric package that worked for you in Lucid.

[Frank Denissen (aankoopdenissen)]

I installed linux-backports-modules-headers-precise-generic_3.2.0.26.28_amd64.deb and linux-headers-lbm-3.2.0-26-generic but both packages seem to be empty ....

[penalvch (penalvch)]

Frank Denissen, I also noticed no amd64. Instead, could you try i386 https://launchpad.net/~canonical-kernel-team/+archive/ppa/+build/3576360 ?

[Frank Denissen (aankoopdenissen)]

That would be difficult as I have only amd64 installed ...

[penalvch (penalvch)]

Frank Denissen, could you please make a separate partition for testing purposes?

[Frank Denissen (aankoopdenissen)]

The problem does not occur on i386: I tried versions linux-generic-pae 3.2.0-23 and 3.2.0-26 and both work without problems. So it seems to be an amd64 problem.

[Vladimir Dovgalyuk (vvd416-r)]

I have exactly the same problem in i386. The OS version is 12.04.1 32 bit, NIC is Macronix 98715. With 12.10 LiveCD NetworkManager works as designed.
Please let me know if you need logs.

[penalvch (penalvch)]

Vladimir Dovgalyuk, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[penalvch (penalvch)]

Frank Denissen, as per http://www.asus.com/Notebooks_Ultrabooks/N55SF/#support_Download_8 an update is available for your BIOS (207). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Thank you for your understanding.

[Frank Denissen (aankoopdenissen)]

I recently had to reinstall my PC and the problem was gone (I'm still using precise).

I assume that a recent update in kernel or NetworkManager solved the problem:

3.2.0-51-generic #77-Ubuntu SMP Wed Jul 24 20:18:19 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Frank Denissen, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1018933/comments/47 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.