On Fri, 30 Mar 2007 17:47:04 +0300 "Tambet Ingo" <[EMAIL PROTECTED]> wrote:
> It sounds a lot like some sort of DBUS issue that prevents the > messages to reach NM. Is the system bus really busy when it happens? > There are some limits in dbus for maximum number of pending calls. > Messages that do not fit in that limit are just dropped (AFAIK). I managed to run dbus-monitor and dbus doesn't seem busy at all. Couple of messages every couple of tens of seconds. What I noticed is that in case I send a dbus sleep/wake command and NM does nothing with it, dbus-monitor reports only: signal sender=org.freedesktop.DBus -> dest=(null destination) path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.185" string "" string ":1.185" signal sender=org.freedesktop.DBus -> dest=(null destination) path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.185" string ":1.185" string "" And nothing else happens. In case it works as supposed (usually after a couple of tries with the wake/sleep command), I additionally get: signal sender=:1.2 -> dest=(null destination) path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; member=StateChange uint32 4 and the rest of the stuff you probably know very well. Also, when I manage to wake it up, it takes quite a lot of time for it to begin dhcp negotiations. Please note that 20s gap and sorry for formatting: Mar 30 17:06:26 kromka NetworkManager: <information> Waking up from sleep. Mar 30 17:06:26 kromka NetworkManager: <information> Deactivating device ath0. Mar 30 17:06:26 kromka NetworkManager: <information> Deactivating device eth0. Mar 30 17:06:26 kromka NetworkManager: <information> ath0: Device is fully-supported using driver 'ath_pci'. Mar 30 17:06:26 kromka NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start Mar 30 17:06:26 kromka NetworkManager: <information> nm_device_init(): device's worker thread started, continuing. Mar 30 17:06:26 kromka NetworkManager: <information> Now managing wireless (802.11) device 'ath0'. Mar 30 17:06:26 kromka NetworkManager: <information> Deactivating device ath0. Mar 30 17:06:26 kromka NetworkManager: <information> eth0: Device is fully-supported using driver 'tg3'. Mar 30 17:06:26 kromka NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start Mar 30 17:06:26 kromka NetworkManager: <information> nm_device_init(): device's worker thread started, continuing. Mar 30 17:06:26 kromka NetworkManager: <information> Now managing wired Ethernet (802.3) device 'eth0'. Mar 30 17:06:26 kromka NetworkManager: <information> Deactivating device eth0. Mar 30 17:06:47 kromka NetworkManager: <information> SWITCH: no current connection, found better connection 'ath0'. Mar 30 17:06:47 kromka NetworkManager: <information> Will activate connection 'ath0/some_essid'. Mar 30 17:06:47 kromka NetworkManager: <information> Device ath0 activation scheduled... Mar 30 17:06:47 kromka NetworkManager: <information> Activation (ath0) started... Mar 30 17:06:47 kromka NetworkManager: <information> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled. (...) -- Regards, Dawid Wróbel _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
