[Pkg-utopia-maintainers] Bug#608533: Problem started again after cold boot

[Dominique Brazziel]

	Spam start coincides with nm-applet start up:

Feb  7 11:36:16 asusb202 kernel: [   73.642425]    groups: 0-1
(cpu_power = 1178)
Feb  7 11:36:16 asusb202 kernel: [   73.642438] CPU1 attaching
sched-domain:
Feb  7 11:36:16 asusb202 kernel: [   73.642445]  domain 0: span 0-1
level SIBLING
Feb  7 11:36:16 asusb202 kernel: [   73.642452]   groups: 1 (cpu_power =
589) 0 (cpu_power = 589)
Feb  7 11:36:16 asusb202 kernel: [   73.642467]   domain 1: span 0-1
level CPU
Feb  7 11:36:16 asusb202 kernel: [   73.642474]    groups: 0-1
(cpu_power = 1178)
Feb  7 11:36:27 asusb202 kernel: [   84.650637] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:37:07 asusb202 kernel: [  124.648346] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:37:57 asusb202 kernel: [  174.648703] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:38:57 asusb202 kernel: [  234.650941] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:39:57 asusb202 kernel: [  294.649260] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:40:57 asusb202 kernel: [  354.649338] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:41:57 asusb202 kernel: [  414.649993] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:42:57 asusb202 kernel: [  474.650844] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:43:57 asusb202 kernel: [  534.646397] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:44:57 asusb202 kernel: [  594.649402] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:45:57 asusb202 kernel: [  654.649793] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:46:57 asusb202 kernel: [  714.650921] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:47:57 asusb202 kernel: [  774.650640] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105
Feb  7 11:48:57 asusb202 kernel: [  834.649588] ===>rt_ioctl_giwscan.
1(1) BSS returned, data->length = 105

1000      4189  3554  0 11:36 ?        00:00:01 nm-applet --sm-disable  

After "Enable Wireless" unchecked the messages stop.  Further inspection
of message log indicates that network-manager may not have properly 
reset the device to the desired state (unmanaged) before nm-applet
started up.  Here is the layout of the different states (from 
NetworkManager.h):

  /* Initial state of all devices and the only state for devices not
         * managed by NetworkManager.
         *
         * Allowed next states:
         *   UNAVAILABLE:  the device is now managed by NetworkManager
         */
        NM_DEVICE_STATE_UNMANAGED = 1,

        /* Indicates the device is not yet ready for use, but is managed
by
         * NetworkManager.  For Ethernet devices, the device may not
have an
         * active carrier.  For WiFi devices, the device may not have
it's radio
         * enabled.
         *
         * Allowed next states:
         *   UNMANAGED:  the device is no longer managed by
NetworkManager
         *   DISCONNECTED:  the device is now ready for use
         */
        NM_DEVICE_STATE_UNAVAILABLE = 2,

        /* Indicates the device does not have an activate connection to
anything.
         *
         * Allowed next states:
         *   UNMANAGED:  the device is no longer managed by
NetworkManager
         *   UNAVAILABLE:  the device is no longer ready for use
(rfkill, no carrier, etc)
         *   PREPARE:  the device has started activation
         */
        NM_DEVICE_STATE_DISCONNECTED = 3,

        /* Indicate states in device activation.
         *
         * Allowed next states:
         *   UNMANAGED:  the device is no longer managed by
NetworkManager
         *   UNAVAILABLE:  the device is no longer ready for use
(rfkill, no carrier, etc)
         *   FAILED:  an error ocurred during activation
         *   NEED_AUTH:  authentication/secrets are needed
         *   ACTIVATED:  (IP_CONFIG only) activation was successful
         *   DISCONNECTED:  the device's connection is no longer valid,
or NetworkManager went to sleep
         */
        NM_DEVICE_STATE_PREPARE = 4,
        NM_DEVICE_STATE_CONFIG = 5,
        NM_DEVICE_STATE_NEED_AUTH = 6,
        NM_DEVICE_STATE_IP_CONFIG = 7,

        /* Indicates the device is part of an active network connection.
         *
         * Allowed next states:
         *   UNMANAGED:  the device is no longer managed by
NetworkManager
         *   UNAVAILABLE:  the device is no longer ready for use
(rfkill, no carrier, etc)
         *   FAILED:  a DHCP lease was not renewed, or another error
         *   DISCONNECTED:  the device's connection is no longer valid,
or NetworkManager went to sleep
         */
        NM_DEVICE_STATE_ACTIVATED = 8,

        /* Indicates the device's activation failed.
         *
         * Allowed next states:
         *   UNMANAGED:  the device is no longer managed by
NetworkManager
         *   UNAVAILABLE:  the device is no longer ready for use
(rfkill, no carrier, etc)
         *   DISCONNECTED:  the device's connection is ready for
activation, or NetworkManager went to sleep
       /* Indicates the device's activation failed.
         *
         * Allowed next states:
         *   UNMANAGED:  the device is no longer managed by
NetworkManager
         *   UNAVAILABLE:  the device is no longer ready for use
(rfkill, no carrier, etc)
         *   DISCONNECTED:  the device's connection is ready for
activation, or NetworkManager went to sleep
         */
        NM_DEVICE_STATE_FAILED = 9

A restart of network-manager produced two notable changes:

1.  nm-applet shows Wireless Networks 'Device not Managed'
2.  nm-applet has 'Enable Wireless' checked

The root cause (in my case) may be in NetworkManager not setting
the device state to UNMANAGED _after_ nm startup but _before_ nm-applet
start up.  I will look into the code more to see more about how and
where nm-applet saves the 'Enable Wireless' setting, or if it saves it
at all.