Bug#514943: [Pkg-utopia-maintainers] Bug#514943: network-manager: wired connection remains with wireless associated and no cable
Drew Parsons wrote: On Thu, 2009-02-12 at 08:57 +0100, Michael Biebl wrote: NM checks /sys/class/net/*/carrier What does that say [1] one your system, when eth0 is connected/disconnected? Cheers Michael [1] cat /sys/class/net/eth0/carrier The problem's popped up again. My system froze (kernel oops, video driver unrelated to nm). After rebooting, it's back in that horrid state where it brings up eth0 even with no cable plugged in. Currently, $ cat /sys/class/net/eth0/carrier 0 So no cable detected there. Why would nm bring up eth0 then? Now I'm stuck back in the broken state I was originally reporting. All I can do to workaround the problem is set the eth0 configuration to manual. Rebooting doesn't help. (I don't know why it magically started working correctly after I reported this bug this week). Ok, after resume, when the system is back up (and carrier is 0), please stop the running network-manager (/etc/init.d/network-manager) and run (as root) /usr/sbin/NetworkManager --no-daemon and attach the complete output to this bug report. Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#514943: [Pkg-utopia-maintainers] Bug#514943: network-manager: wired connection remains with wireless associated and no cable
On Sat, 2009-02-14 at 11:35 +0100, Michael Biebl wrote: Ok, after resume, when the system is back up (and carrier is 0), please stop the running network-manager (/etc/init.d/network-manager) and run (as root) /usr/sbin/NetworkManager --no-daemon and attach the complete output to this bug report. Here it is. I reset the wired configuration to Connect Automatically, so the log would be for the embugged state. There's an (eth0): carrier now ON (device state 2) message which I guess should not be there. While network-manager is stopped, there are a couple of nm apps still running in the background (nm-system-settings, nm-applet). They wouldn't be confusing nm's state would they? Drew NetworkManager.out Description: chemical/gulp
Bug#514943: [Pkg-utopia-maintainers] Bug#514943: network-manager: wired connection remains with wireless associated and no cable
Drew Parsons schrieb: On Thu, 2009-02-12 at 07:57 +0100, Michael Biebl wrote: What driver do you use? What does nm-tool say for eth0, is carrier detect supported? Driver for eth0 is e1000e, Carrier Detect: yes The wlan0 driver is iwlagn. You might also check the syslog . syslog says before the new kernel, nm would bring eth0 up at home, and then deactivate it: Jan 31 21:47:50 pug NetworkManager: info Waking up... Jan 31 21:47:50 pug NetworkManager: info (eth0): now managed Jan 31 21:47:50 pug NetworkManager: info (eth0): device state change: 1 - 2 Jan 31 21:47:50 pug NetworkManager: info (eth0): bringing up device. Jan 31 21:47:50 pug kernel: [31790.172718] ADDRCONF(NETDEV_UP): eth0: link is not ready Jan 31 21:47:50 pug NetworkManager: info (eth0): preparing device. Jan 31 21:47:50 pug NetworkManager: info (eth0): deactivating device (reason: 2). Jan 31 21:47:50 pug NetworkManager: info (wlan0): now managed Jan 31 21:47:50 pug NetworkManager: info (wlan0): device state change: 1 - 2 Jan 31 21:47:50 pug NetworkManager: info (wlan0): bringing up device. ... Jan 31 21:50:09 pug NetworkManager: info (wlan0): preparing device. Jan 31 21:50:09 pug NetworkManager: info (wlan0): deactivating device (reason: 2). Jan 31 21:50:09 pug kernel: [31929.475088] ADDRCONF(NETDEV_UP): wlan0: link is not ready Jan 31 21:50:09 pug kernel: [31929.488461] wlan0: authenticate with AP Does reason 2 means no cable? Nothing more was said about eth0. It continued from wlan0: authenticate with AP and the wireless interface got established. With the new kernel, syslog starts reporting the same, including (eth0): deactivating device (reason: 2). But then a second later it continues on saying: Feb 12 00:35:14 pug NetworkManager: info (wlan0): preparing device. Feb 12 00:35:14 pug NetworkManager: info (wlan0): deactivating device (reason: 2). Feb 12 00:35:14 pug kernel: [ 8875.187423] ADDRCONF(NETDEV_UP): wlan0: link is not ready Feb 12 00:35:14 pug NetworkManager: info (eth0): carrier now ON (device state 2) Feb 12 00:35:14 pug NetworkManager: info (eth0): device state change: 2 - 3 Feb 12 00:35:14 pug NetworkManager: info (wlan0): device state change: 2 - 3 Feb 12 00:35:14 pug NetworkManager: info Activation (eth0) starting connection 'ANU wired' Feb 12 00:35:14 pug NetworkManager: info (eth0): device state change: 3 - 4 Feb 12 00:35:14 pug NetworkManager: info Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... ... Feb 12 00:35:15 pug NetworkManager: info (eth0): device state change: 7 - 8 Feb 12 00:35:15 pug NetworkManager: info (eth0): writing resolv.conf to /sbin/resolvconf Feb 12 00:35:27 pug NetworkManager: info Policy set (eth0) as default for routing and DNS. These eth0 entries are new. I guess (eth0): carrier now ON is the start of the trouble. Only after this do I get to the wlan0: authenticate with AP step. There are also some new wlan0 steps between set (eth0) as default and authenticate with AP, including: Feb 12 00:35:27 pug NetworkManager: info Activation (eth0) successful, device activated. Feb 12 00:35:27 pug NetworkManager: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. Feb 12 00:35:27 pug NetworkManager: info (wlan0): supplicant interface state change: 1 - 2. Feb 12 00:35:29 pug NetworkManager: info Activation (wlan0) starting connection 'myAP' Feb 12 00:35:29 pug NetworkManager: info (wlan0): device state change: 3 - 4 Feb 12 00:35:29 pug NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Is that enough detail or do you need full logs? NM checks /sys/class/net/*/carrier What does that say [1] one your system, when eth0 is connected/disconnected? Cheers Michael [1] cat /sys/class/net/eth0/carrier -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#514943: [Pkg-utopia-maintainers] Bug#514943: network-manager: wired connection remains with wireless associated and no cable
Drew Parsons schrieb: Package: network-manager Version: 0.7.0-1 Severity: normal A change in network-manager behaviour appears to have been triggered by the 2.6.28 linux kernel. Up till now, I've had network-manager automatically connect to and switch between wired and wireless networks. At work I insert the cable, and my wired connection is set up. I take my laptop home, and it finds my wireless network, the wired connection is switched off. Now all of a sudden I've found that when I get home, the wired connection is still on, even though no cable is inserted to the ethernet jack. At the same time the wireless network is still found and set up. But because nm has already set up the eth0 interface, the gateway and dns (/etc/resolve.conf) is not rewritten. wlan0 is routed to the local network only, the gateway is still set to the eth0 address. So I can't connect properly to the external internet from home. The only way I know to work around the problem is to switch off Connects automatically in the nm configuration entry for the wired network. This makes it less convenient at work, where previously I just had to plug in the cable for nm to set up the connection. As far as I can tell the only change I've made to cause this new behaviour is to install a 2.6.28 kernel (well, bind9-host also got upgraded over the weekend along with associated libraries). What driver do you use? What does nm-tool say for eth0, is carrier detect supported? You might also check the syslog . Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
