Package: network-manager
Version: 0.8.2-3
Severity: important
Since upgrading network-manager from 0.8.1-6 to 0.8.2-3, I am not sure
about the previous experimental version 0.8.2-1 or what is was, I get
quite frequent crashes when Network Manager tries to connect via DHCP
and one also via DSL.
In syslog I get - this time a failed DHCP attempt, my Debian Lenny based
DSL router ASUS WL-500g Premium takes some time to boot from USB stick:
Dec 23 10:06:54 shambhala dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port
67
[...]
Dec 23 10:07:10 shambhala dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 8
Dec 23 10:07:18 shambhala dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 12
Dec 23 10:07:30 shambhala dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 13
Dec 23 10:07:31 shambhala NetworkManager[25690]: <warn> (eth0): DHCPv4 request
timed out.
Dec 23 10:07:32 shambhala NetworkManager[25690]: <info> (eth0): canceled DHCP
transaction, DHCP client pid 25024
Dec 23 10:07:32 shambhala NetworkManager[25690]: <info> Activation (eth0) Stage
4 of 5 (IP4 Configure Timeout) sche
duled...
Dec 23 10:07:32 shambhala NetworkManager[25690]: <info> Activation (eth0) Stage
4 of 5 (IP4 Configure Timeout) star
ted...
Dec 23 10:07:32 shambhala NetworkManager[25690]: <info> Activation (eth0) Stage
5 of 5 (IP Configure Commit) schedu
led...
Dec 23 10:07:32 shambhala NetworkManager[25690]: <info> Activation (eth0) Stage
4 of 5 (IP4 Configure Timeout) comp
lete.
Dec 23 10:07:32 shambhala NetworkManager[25690]: <info> Activation (eth0) Stage
5 of 5 (IP Configure Commit) starte
d...
Dec 23 10:07:32 shambhala NetworkManager[25690]: <info> Activation (eth0) Stage
5 of 5 (IP Configure Commit) failed
(no IP configuration found)
Dec 23 10:07:32 shambhala NetworkManager[25690]: <info> (eth0): device state
change: 7 -> 9 (reason 5)
Dec 23 10:07:32 shambhala NetworkManager[25690]: <info> Marking connection
'Auto eth0' invalid.
Dec 23 10:07:32 shambhala NetworkManager[25690]: <warn> Activation (eth0)
failed.
Dec 23 10:07:32 shambhala NetworkManager[25690]: <info> Activation (eth0) Stage
5 of 5 (IP Configure Commit) comple
te.
Dec 23 10:07:32 shambhala NetworkManager[25690]: <info> (eth0): device state
change: 9 -> 3 (reason 0)
Dec 23 10:07:32 shambhala NetworkManager[25690]: <info> (eth0): deactivating
device (reason: 0).
Dec 23 10:07:35 shambhala NetworkManager[25690]: <info> Activation (eth0)
starting connection 'M-Net'
Dec 23 10:07:35 shambhala NetworkManager[25690]: <info> (eth0): device state
change: 3 -> 4 (reason 0)
Dec 23 10:07:35 shambhala NetworkManager[25690]: <info> Activation (eth0) Stage
1 of 5 (Device Prepare) scheduled..
.
Dec 23 10:07:35 shambhala NetworkManager[25690]: <info> Activation (eth0) Stage
1 of 5 (Device Prepare) started...
Dec 23 10:07:36 shambhala NetworkManager[25690]: <warn> caught signal 6.
Generating backtrace...
Dec 23 10:07:36 shambhala NetworkManager: ******************* START
**********************************
Dec 23 10:07:37 shambhala NetworkManager: [Thread debugging using libthread_db
enabled]
Dec 23 10:07:37 shambhala NetworkManager: [New Thread 0xb7082b70 (LWP 25701)]
Dec 23 10:07:38 shambhala NetworkManager: 0xb77ed424 in __kernel_vsyscall ()
Dec 23 10:07:38 shambhala NetworkManager: ******************* END
**********************************
The crash was after waking up network-manager via
# Network Manager aufwecken
dbus-send --print-reply --system \
--dest=org.freedesktop.NetworkManager \
/org/freedesktop/NetworkManager \
org.freedesktop.NetworkManager.wake
in my hibernate-extra script. I use hibernate with in kernel
suspend-to-disk as I am not convinced that pm-tools are
stable and robust enough.
I also get it on regular shutdowns of Network Manager:
Dec 21 22:09:44 shambhala NetworkManager[26476]: <info> caught signal 15,
shutting down normally.
Dec 21 22:09:44 shambhala NetworkManager[26476]: <warn> caught signal 6.
Generating backtrace...
Dec 21 22:09:44 shambhala NetworkManager: ******************* START
**********************************
Dec 21 22:09:46 shambhala NetworkManager: [Thread debugging using libthread_db
enabled]
Dec 21 22:09:46 shambhala NetworkManager: [New Thread 0xb7094b70 (LWP 26484)]
Dec 21 22:09:46 shambhala NetworkManager: 0xb7791424 in __kernel_vsyscall ()
Dec 21 22:09:46 shambhala NetworkManager: ******************* END
**********************************
Hmmm, that might be a way to try again with the debug package installed.
Yes, this seems to be reproducable always. But after installing
network-manager-dbg, libglib2.0-0-dbg, libdbus-glib-1-2-dbg and
libgcrypt11-dbg I still only get:
Dec 23 10:32:10 shambhala NetworkManager[30784]: <info> caught signal 15,
shutting down normally.
Dec 23 10:32:10 shambhala NetworkManager[30784]: <warn> caught signal 6.
Generating backtrace...
Dec 23 10:32:10 shambhala NetworkManager: ******************* START
**********************************
Dec 23 10:32:10 shambhala NetworkManager: [Thread debugging using libthread_db
enabled]
Dec 23 10:32:10 shambhala NetworkManager: [New Thread 0xb70bab70 (LWP 30793)]
Dec 23 10:32:10 shambhala NetworkManager: 0xb7825424 in __kernel_vsyscall ()
Dec 23 10:32:10 shambhala NetworkManager: ******************* END
**********************************
Are there other debug packages I need to install?
Changed configuration file:
mar...@shambhala:~> cat /etc/NetworkManager/NetworkManager.conf
[main]
#plugins=ifupdown,keyfile
plugins=keyfile
#[ifupdown]
#managed=true
no-auto-default=00:11... (primary network interface eth0)
[keyfile]
hostname=shambhala
I just disabled ifupdown management, as I let network-manager do everything
itself. I don't know where with no-auto-default is coming from.
I get no hint whatsoever in the plasma-widget-networkmanagement applet
when Network Manager crashed.
Have a merry and peaceful Christmas,
Martin
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (450, 'testing'), (400, 'unstable'), (110, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.37-rc7-tp42-ata-eh-dbg-dirty (PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages network-manager depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii dbus 1.2.24-3 simple interprocess messaging syst
ii isc-dhcp-client 4.1.1-P1-15 ISC DHCP client
ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib
ii libdbus-1-3 1.2.24-3 simple interprocess messaging syst
ii libdbus-glib-1-2 0.88-2 simple interprocess messaging syst
ii libgcrypt11 1.4.5-2 LGPL Crypto library - runtime libr
ii libglib2.0-0 2.27.4-2 The GLib library of C routines
ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr
ii libgudev-1.0-0 164-3 GObject-based wrapper library for
ii libnl1 1.1-6 library for dealing with netlink s
ii libnm-glib2 0.8.2-3 network management framework (GLib
ii libnm-util1 0.8.2-3 network management framework (shar
ii libpolkit-gobject-1-0 0.96-4 PolicyKit Authorization API
ii libuuid1 2.17.2-3.3 Universally Unique ID library
ii lsb-base 3.2-26 Linux Standard Base 3.2 init scrip
ii udev 164-3 /dev/ and hotplug management daemo
ii wpasupplicant 0.6.10-2.1 client support for WPA and WPA2 (I
Versions of packages network-manager recommends:
ii dns 2.55-2+b1 A small caching DNS proxy and DHCP
ii ipt 1.4.10-1 administration tools for packet fi
ii mod 0.4+git.20100624t180933.6e79d15-1+b1 D-Bus service for managing modems
ii pol 0.96-4 framework for managing administrat
ii ppp 2.4.5-4 Point-to-Point Protocol (PPP) - da
Versions of packages network-manager suggests:
pn avahi-autoipd <none> (no description available)
-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed [not included]
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
