I discussed this problem on the upstream mailing list here: http://thread.gmane.org/gmane.linux.network.networkmanager.devel/25377
In my case, the problem was indeed that netconsole was loaded. Netconsole was loaded in the initrd, and brought the network interface up. As the network interface went up, the kernel would automatically configure an IPv6 address via SLAAC. Then when later network-manager starts up, it notices that the network interface is already brought up, and hence it decides not to touch it any more: instead of loading the default network configuration for that device, a (temporary) network connection with the name of the device and the configuration corresponding to the actual state (in my case: IPv6 activated but no IPv4) is created in NM. I removed the netconsole stuff, removed the eth0 network connection in NM, and rebooted the system, and everything was OK again. Apparently it's only safe to load netconsole after NM has started, otherwise you get hit by this problem. -- Frederik Himpe <frede...@frehi.be> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
