| 2010-04-22 07:42:47 |
Vish |
bug |
|
|
added bug |
| 2010-04-22 07:42:47 |
Vish |
attachment added |
|
Dependencies.txt http://launchpadlibrarian.net/45006428/Dependencies.txt |
|
| 2010-04-22 07:42:47 |
Vish |
attachment added |
|
Gconf.txt http://launchpadlibrarian.net/45006429/Gconf.txt |
|
| 2010-04-22 07:42:47 |
Vish |
attachment added |
|
IpAddr.txt http://launchpadlibrarian.net/45006430/IpAddr.txt |
|
| 2010-04-22 07:42:47 |
Vish |
attachment added |
|
IwConfig.txt http://launchpadlibrarian.net/45006431/IwConfig.txt |
|
| 2010-04-22 07:42:47 |
Vish |
attachment added |
|
NetDevice.eth0.txt http://launchpadlibrarian.net/45006432/NetDevice.eth0.txt |
|
| 2010-04-22 07:42:47 |
Vish |
attachment added |
|
NetDevice.lo.txt http://launchpadlibrarian.net/45006433/NetDevice.lo.txt |
|
| 2010-04-22 07:42:47 |
Vish |
attachment added |
|
NetDevice.vboxnet0.txt http://launchpadlibrarian.net/45006434/NetDevice.vboxnet0.txt |
|
| 2010-04-22 07:42:47 |
Vish |
attachment added |
|
NetDevice.wlan0.txt http://launchpadlibrarian.net/45006435/NetDevice.wlan0.txt |
|
| 2010-04-22 07:42:47 |
Vish |
attachment added |
|
PciNetwork.txt http://launchpadlibrarian.net/45006436/PciNetwork.txt |
|
| 2010-04-22 07:42:47 |
Vish |
attachment added |
|
RfKill.txt http://launchpadlibrarian.net/45006437/RfKill.txt |
|
| 2010-04-22 07:42:47 |
Vish |
attachment added |
|
WifiSyslog.txt http://launchpadlibrarian.net/45006438/WifiSyslog.txt |
|
| 2010-04-22 07:42:47 |
Vish |
attachment added |
|
nm-system-settings.conf.txt http://launchpadlibrarian.net/45006439/nm-system-settings.conf.txt |
|
| 2010-04-22 07:45:56 |
Vish |
network-manager (Ubuntu): importance |
Undecided |
Low |
|
| 2010-04-22 07:58:04 |
Vish |
attachment added |
|
syslog.log http://launchpadlibrarian.net/45007594/syslog.log |
|
| 2010-04-22 07:59:52 |
Vish |
description |
Binary package hint: network-manager
Since update :
network-manager (0.8-0ubuntu2) to 0.8-0ubuntu3
or
network-manager-pptp (0.8-0ubuntu1) to 0.8-0ubuntu2
network-manager-pptp-gnome (0.8-0ubuntu1) to 0.8-0ubuntu2
I have been noticing the following errors and wireless just disconnects for no reason:
Apr 22 12:17:01 vish-laptop CRON[30546]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 22 12:48:26 vish-laptop kernel: [85758.502125] No probe response from AP 00:14:6c:d0:d1:20 after 500ms, disconnecting.
Apr 22 12:48:26 vish-laptop wpa_supplicant[1006]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Apr 22 12:48:26 vish-laptop NetworkManager: <info> (wlan0): supplicant connection state: completed -> disconnected
Apr 22 12:48:26 vish-laptop NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Apr 22 12:48:27 vish-laptop kernel: [85759.129626] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:27 vish-laptop kernel: [85759.129637] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:27 vish-laptop kernel: [85759.629037] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.
Apr 22 12:48:28 vish-laptop kernel: [85760.129145] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:28 vish-laptop kernel: [85760.129156] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:28 vish-laptop kernel: [85760.631750] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:28 vish-laptop kernel: [85760.631761] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:29 vish-laptop kernel: [85761.131013] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
Apr 22 12:48:33 vish-laptop kernel: [85765.132430] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:33 vish-laptop kernel: [85765.132441] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:33 vish-laptop kernel: [85765.632330] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.
Apr 22 12:48:34 vish-laptop kernel: [85766.136110] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:34 vish-laptop kernel: [85766.136121] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:34 vish-laptop kernel: [85766.638541] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:34 vish-laptop kernel: [85766.638552] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:35 vish-laptop kernel: [85767.137475] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
Apr 22 12:48:39 vish-laptop kernel: [85771.136855] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:39 vish-laptop kernel: [85771.136866] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:39 vish-laptop kernel: [85771.636086] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.
Apr 22 12:48:40 vish-laptop kernel: [85772.136043] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:40 vish-laptop kernel: [85772.136053] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:40 vish-laptop kernel: [85772.638124] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:40 vish-laptop kernel: [85772.638135] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:41 vish-laptop kernel: [85773.138440] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
Apr 22 12:48:42 vish-laptop NetworkManager: <info> (wlan0): device state change: 8 -> 3 (reason 11)
Apr 22 12:48:42 vish-laptop NetworkManager: <info> (wlan0): deactivating device (reason: 11).
Apr 22 12:48:42 vish-laptop NetworkManager: <info> (wlan0): canceled DHCP transaction, dhcp client pid 1506
Apr 22 12:48:42 vish-laptop NetworkManager: <WARN> check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess#012
Apr 22 12:48:42 vish-laptop avahi-daemon[797]: Withdrawing address record for 192.168.1.2 on wlan0.
Apr 22 12:48:42 vish-laptop avahi-daemon[797]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.2.
Apr 22 12:48:42 vish-laptop avahi-daemon[797]: Interface wlan0.IPv4 no longer relevant for mDNS.
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Activation (wlan0) starting connection 'Auto Airtel'
Apr 22 12:48:42 vish-laptop NetworkManager: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 22 12:48:42 vish-laptop NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 22 12:48:42 vish-laptop NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto Airtel' has security, and secrets exist. No new secrets needed.
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Config: added 'ssid' value 'Airtel'
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Config: added 'scan_ssid' value '1'
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
Apr 22 12:48:42 vish-laptop NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Apr 22 12:48:42 vish-laptop NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 22 12:48:42 vish-laptop NetworkManager: <info> Config: set interface ap_scan to 1
Apr 22 12:48:44 vish-laptop postfix/master[1071]: reload -- version 2.7.0, configuration /etc/postfix
Apr 22 12:48:44 vish-laptop NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Apr 22 12:48:45 vish-laptop kernel: [85777.134457] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:45 vish-laptop kernel: [85777.134468] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:45 vish-laptop kernel: [85777.633202] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.
Apr 22 12:48:46 vish-laptop kernel: [85778.132808] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:46 vish-laptop kernel: [85778.132819] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:46 vish-laptop kernel: [85778.635040] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:46 vish-laptop kernel: [85778.635050] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:47 vish-laptop kernel: [85779.136039] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
Apr 22 12:48:51 vish-laptop kernel: [85783.138366] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:51 vish-laptop kernel: [85783.138376] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:51 vish-laptop kernel: [85783.638288] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.
Apr 22 12:48:52 vish-laptop kernel: [85784.136040] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:52 vish-laptop kernel: [85784.136051] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:52 vish-laptop kernel: [85784.639043] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:52 vish-laptop kernel: [85784.639054] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:53 vish-laptop kernel: [85785.136906] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
Apr 22 12:48:57 vish-laptop kernel: [85789.144055] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
Apr 22 12:48:57 vish-laptop kernel: [85789.144065] iwl3945 0000:03:00.0: Error setting new configuration (-110).
Apr 22 12:48:57 vish-laptop kernel: [85789.144133] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:48:57 vish-laptop kernel: [85789.144140] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
Apr 22 12:48:57 vish-laptop kernel: [85789.144158] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:48:57 vish-laptop kernel: [85789.144163] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:48:57 vish-laptop kernel: [85789.144169] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:48:57 vish-laptop kernel: [85789.144176] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:48:57 vish-laptop kernel: [85789.144181] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:48:57 vish-laptop kernel: [85789.144187] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:48:57 vish-laptop kernel: [85789.144199] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:48:57 vish-laptop kernel: [85789.144205] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:02 vish-laptop kernel: [85794.149958] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:02 vish-laptop kernel: [85794.149970] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:02 vish-laptop kernel: [85794.149977] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:02 vish-laptop kernel: [85794.150026] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:02 vish-laptop kernel: [85794.150033] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:02 vish-laptop kernel: [85794.150047] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:02 vish-laptop kernel: [85794.150052] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:02 vish-laptop kernel: [85794.150058] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:02 vish-laptop kernel: [85794.150065] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:02 vish-laptop kernel: [85794.150070] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:02 vish-laptop kernel: [85794.150076] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:02 vish-laptop kernel: [85794.150087] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:02 vish-laptop kernel: [85794.150093] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:07 vish-laptop kernel: [85799.152207] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:07 vish-laptop kernel: [85799.152219] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:07 vish-laptop kernel: [85799.152226] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:07 vish-laptop kernel: [85799.152257] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:07 vish-laptop kernel: [85799.152265] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:07 vish-laptop kernel: [85799.152284] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:07 vish-laptop kernel: [85799.152290] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:07 vish-laptop kernel: [85799.152296] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:07 vish-laptop kernel: [85799.152302] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:07 vish-laptop kernel: [85799.152307] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:07 vish-laptop kernel: [85799.152313] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:07 vish-laptop kernel: [85799.152325] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:07 vish-laptop kernel: [85799.152331] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:12 vish-laptop kernel: [85804.157237] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:12 vish-laptop kernel: [85804.157250] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:12 vish-laptop kernel: [85804.157257] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:12 vish-laptop kernel: [85804.157308] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:12 vish-laptop kernel: [85804.157314] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:12 vish-laptop kernel: [85804.157329] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:12 vish-laptop kernel: [85804.157334] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:12 vish-laptop kernel: [85804.157340] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:12 vish-laptop kernel: [85804.157346] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:12 vish-laptop kernel: [85804.157351] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:12 vish-laptop kernel: [85804.157357] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:12 vish-laptop kernel: [85804.157369] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:12 vish-laptop kernel: [85804.157374] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:17 vish-laptop kernel: [85809.161431] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:17 vish-laptop kernel: [85809.161443] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:17 vish-laptop kernel: [85809.161450] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:17 vish-laptop kernel: [85809.161503] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:17 vish-laptop kernel: [85809.161510] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:17 vish-laptop kernel: [85809.161525] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:17 vish-laptop kernel: [85809.161530] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:17 vish-laptop kernel: [85809.161536] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:17 vish-laptop kernel: [85809.161542] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:17 vish-laptop kernel: [85809.161548] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:17 vish-laptop kernel: [85809.161554] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:17 vish-laptop kernel: [85809.161565] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:17 vish-laptop kernel: [85809.161571] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:22 vish-laptop kernel: [85814.166562] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:22 vish-laptop kernel: [85814.166574] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:22 vish-laptop kernel: [85814.166581] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:22 vish-laptop kernel: [85814.166614] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:22 vish-laptop kernel: [85814.166622] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:22 vish-laptop kernel: [85814.166640] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:22 vish-laptop kernel: [85814.166645] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:22 vish-laptop kernel: [85814.166651] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:22 vish-laptop kernel: [85814.166658] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:22 vish-laptop kernel: [85814.166663] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:22 vish-laptop kernel: [85814.166669] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:22 vish-laptop kernel: [85814.166681] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:22 vish-laptop kernel: [85814.166687] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:27 vish-laptop kernel: [85819.170310] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:27 vish-laptop kernel: [85819.170322] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:27 vish-laptop kernel: [85819.170329] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:27 vish-laptop kernel: [85819.170415] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:27 vish-laptop kernel: [85819.170423] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:27 vish-laptop kernel: [85819.170440] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:27 vish-laptop kernel: [85819.170446] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:27 vish-laptop kernel: [85819.170452] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:27 vish-laptop kernel: [85819.170458] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:27 vish-laptop kernel: [85819.170463] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:27 vish-laptop kernel: [85819.170469] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:27 vish-laptop kernel: [85819.170482] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:27 vish-laptop kernel: [85819.170488] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:32 vish-laptop kernel: [85824.175675] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:32 vish-laptop kernel: [85824.175685] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:32 vish-laptop kernel: [85824.175690] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:32 vish-laptop kernel: [85824.175728] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:32 vish-laptop kernel: [85824.175732] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:32 vish-laptop kernel: [85824.175742] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:32 vish-laptop kernel: [85824.175745] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:32 vish-laptop kernel: [85824.175749] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:32 vish-laptop kernel: [85824.175753] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:32 vish-laptop kernel: [85824.175756] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:32 vish-laptop kernel: [85824.175759] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:32 vish-laptop kernel: [85824.175767] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:32 vish-laptop kernel: [85824.175771] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:37 vish-laptop kernel: [85829.181598] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:37 vish-laptop kernel: [85829.181607] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:37 vish-laptop kernel: [85829.181611] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:37 vish-laptop kernel: [85829.181702] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:37 vish-laptop kernel: [85829.181707] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:37 vish-laptop kernel: [85829.181718] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:37 vish-laptop kernel: [85829.181721] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:37 vish-laptop kernel: [85829.181725] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:37 vish-laptop kernel: [85829.181728] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:37 vish-laptop kernel: [85829.181731] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:37 vish-laptop kernel: [85829.181735] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:37 vish-laptop kernel: [85829.181743] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:37 vish-laptop kernel: [85829.181747] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:42 vish-laptop kernel: [85834.184077] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:42 vish-laptop kernel: [85834.184088] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:42 vish-laptop kernel: [85834.184095] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:42 vish-laptop kernel: [85834.184147] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:42 vish-laptop kernel: [85834.184153] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:42 vish-laptop kernel: [85834.184168] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:42 vish-laptop kernel: [85834.184173] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:42 vish-laptop kernel: [85834.184179] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:42 vish-laptop kernel: [85834.184186] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:42 vish-laptop kernel: [85834.184191] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:42 vish-laptop kernel: [85834.184197] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:42 vish-laptop kernel: [85834.184209] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:42 vish-laptop kernel: [85834.184214] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Activation (wlan0/wireless): association took too long.
Apr 22 12:49:43 vish-laptop NetworkManager: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 22 12:49:43 vish-laptop NetworkManager: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 22 12:49:43 vish-laptop NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 22 12:49:43 vish-laptop NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto Airtel' has security, and secrets exist. No new secrets needed.
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Config: added 'ssid' value 'Airtel'
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Config: added 'scan_ssid' value '1'
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
Apr 22 12:49:43 vish-laptop NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Apr 22 12:49:43 vish-laptop NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 22 12:49:43 vish-laptop NetworkManager: <info> Config: set interface ap_scan to 1
Apr 22 12:49:47 vish-laptop NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Apr 22 12:49:47 vish-laptop kernel: [85839.189680] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:47 vish-laptop kernel: [85839.189692] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:47 vish-laptop kernel: [85839.189699] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:47 vish-laptop kernel: [85839.189857] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:47 vish-laptop kernel: [85839.189865] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:47 vish-laptop kernel: [85839.189882] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:47 vish-laptop kernel: [85839.189887] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:47 vish-laptop kernel: [85839.189893] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:47 vish-laptop kernel: [85839.189899] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:47 vish-laptop kernel: [85839.189905] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:47 vish-laptop kernel: [85839.189911] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:47 vish-laptop kernel: [85839.189923] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:47 vish-laptop kernel: [85839.189929] iwl3945 0000:03:00.0: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:51 vish-laptop NetworkManager: <info> (wlan0): device state change: 5 -> 2 (reason 0)
Apr 22 12:49:51 vish-laptop NetworkManager: <info> (wlan0): deactivating device (reason: 0).
Apr 22 12:49:51 vish-laptop NetworkManager: <info> (wlan0): taking down device.
Apr 22 12:49:51 vish-laptop avahi-daemon[797]: Withdrawing address record for fe80::213:2ff:fe01:684d on wlan0.
Apr 22 12:49:51 vish-laptop kernel: [85843.208084] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:51 vish-laptop kernel: [85843.208093] iwl3945 0000:03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -28
Apr 22 12:49:51 vish-laptop kernel: [85843.208097] iwl3945 0000:03:00.0: Error setting new configuration (-28).
Apr 22 12:49:51 vish-laptop kernel: [85843.208103] iwl3945 0000:03:00.0: No space for Tx
Apr 22 12:49:51 vish-laptop kernel: [85843.208107] iwl3945 0000:03:00.0: Error sending REPLY_LEDS_CMD: enqueue_hcmd failed: -28
Apr 22 12:49:52 vish-laptop NetworkManager: <info> (wlan0): bringing up device.
Apr 22 12:49:53 vish-laptop kernel: [85844.829476] Registered led device: iwl-phy0::radio
Apr 22 12:49:53 vish-laptop kernel: [85844.829545] Registered led device: iwl-phy0::assoc
Apr 22 12:49:53 vish-laptop kernel: [85844.829570] Registered led device: iwl-phy0::RX
Apr 22 12:49:53 vish-laptop kernel: [85844.829594] Registered led device: iwl-phy0::TX
Apr 22 12:49:53 vish-laptop kernel: [85844.840819] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 22 12:49:53 vish-laptop NetworkManager: <info> (wlan0): supplicant interface state: starting -> ready
Apr 22 12:49:53 vish-laptop NetworkManager: <info> (wlan0): device state change: 2 -> 3 (reason 42)
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Activation (wlan0) starting connection 'Auto Airtel'
Apr 22 12:49:55 vish-laptop NetworkManager: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 22 12:49:55 vish-laptop NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto Airtel' has security, and secrets exist. No new secrets needed.
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Config: added 'ssid' value 'Airtel'
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Config: added 'scan_ssid' value '1'
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
Apr 22 12:49:55 vish-laptop NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Apr 22 12:49:55 vish-laptop NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 22 12:49:55 vish-laptop NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected
Apr 22 12:49:55 vish-laptop NetworkManager: <info> Config: set interface ap_scan to 1
Apr 22 12:50:00 vish-laptop NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Apr 22 12:50:01 vish-laptop wpa_supplicant[1006]: Trying to associate with 00:14:6c:d0:d1:20 (SSID='Airtel' freq=2462 MHz)
Apr 22 12:50:01 vish-laptop kernel: [85853.500708] wlan0: deauthenticating from 00:14:6c:d0:d1:20 by local choice (reason=3)
Apr 22 12:50:01 vish-laptop kernel: [85853.500889] wlan0: direct probe to AP 00:14:6c:d0:d1:20 (try 1)
Apr 22 12:50:01 vish-laptop NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Apr 22 12:50:01 vish-laptop kernel: [85853.503898] wlan0: direct probe responded
Apr 22 12:50:01 vish-laptop kernel: [85853.503907] wlan0: authenticate with AP 00:14:6c:d0:d1:20 (try 1)
Apr 22 12:50:01 vish-laptop kernel: [85853.506757] wlan0: authenticated
Apr 22 12:50:01 vish-laptop kernel: [85853.506796] wlan0: associate with AP 00:14:6c:d0:d1:20 (try 1)
Apr 22 12:50:01 vish-laptop kernel: [85853.509046] wlan0: RX AssocResp from 00:14:6c:d0:d1:20 (capab=0x411 status=0 aid=1)
Apr 22 12:50:01 vish-laptop kernel: [85853.509055] wlan0: associated
Apr 22 12:50:01 vish-laptop wpa_supplicant[1006]: Associated with 00:14:6c:d0:d1:20
Apr 22 12:50:01 vish-laptop wpa_supplicant[1006]: CTRL-EVENT-CONNECTED - Connection to 00:14:6c:d0:d1:20 completed (auth) [id=0 id_str=]
Apr 22 12:50:01 vish-laptop kernel: [85853.511244] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Apr 22 12:50:01 vish-laptop NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated
Apr 22 12:50:01 vish-laptop NetworkManager: <info> (wlan0): supplicant connection state: associated -> completed
Apr 22 12:50:01 vish-laptop NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Airtel'.
Apr 22 12:50:01 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 22 12:50:01 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Apr 22 12:50:01 vish-laptop NetworkManager: <info> (wlan0): device state change: 5 -> 7 (reason 0)
Apr 22 12:50:01 vish-laptop NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction (timeout in 45 seconds)
Apr 22 12:50:01 vish-laptop NetworkManager: <info> dhclient started with pid 31301
Apr 22 12:50:01 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) scheduled...
Apr 22 12:50:01 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Apr 22 12:50:01 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) started...
Apr 22 12:50:01 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) complete.
Apr 22 12:50:01 vish-laptop dhclient: Internet Systems Consortium DHCP Client V3.1.3
Apr 22 12:50:01 vish-laptop dhclient: Copyright 2004-2009 Internet Systems Consortium.
Apr 22 12:50:01 vish-laptop dhclient: All rights reserved.
Apr 22 12:50:01 vish-laptop dhclient: For info, please visit https://www.isc.org/software/dhcp/
Apr 22 12:50:01 vish-laptop dhclient:
Apr 22 12:50:01 vish-laptop NetworkManager: <info> DHCP: device wlan0 state changed normal exit -> preinit
Apr 22 12:50:01 vish-laptop dhclient: Listening on LPF/wlan0/00:13:02:01:68:4d
Apr 22 12:50:01 vish-laptop dhclient: Sending on LPF/wlan0/00:13:02:01:68:4d
Apr 22 12:50:01 vish-laptop dhclient: Sending on Socket/fallback
Apr 22 12:50:03 vish-laptop avahi-daemon[797]: Registering new address record for fe80::213:2ff:fe01:684d on wlan0.*.
Apr 22 12:50:05 vish-laptop dhclient: DHCPREQUEST of 192.168.1.2 on wlan0 to 255.255.255.255 port 67
Apr 22 12:50:06 vish-laptop dhclient: DHCPACK of 192.168.1.2 from 192.168.1.1
Apr 22 12:50:06 vish-laptop NetworkManager: <info> DHCP: device wlan0 state changed preinit -> reboot
Apr 22 12:50:06 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Apr 22 12:50:06 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Apr 22 12:50:06 vish-laptop NetworkManager: <info> address 192.168.1.2
Apr 22 12:50:06 vish-laptop NetworkManager: <info> prefix 24 (255.255.255.0)
Apr 22 12:50:06 vish-laptop NetworkManager: <info> gateway 192.168.1.1
Apr 22 12:50:06 vish-laptop NetworkManager: <info> nameserver '192.168.1.1'
Apr 22 12:50:06 vish-laptop NetworkManager: <info> domain name 'Airtel'
Apr 22 12:50:06 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Apr 22 12:50:06 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Apr 22 12:50:06 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Apr 22 12:50:06 vish-laptop avahi-daemon[797]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.2.
Apr 22 12:50:06 vish-laptop avahi-daemon[797]: New relevant interface wlan0.IPv4 for mDNS.
Apr 22 12:50:06 vish-laptop avahi-daemon[797]: Registering new address record for 192.168.1.2 on wlan0.IPv4.
Apr 22 12:50:06 vish-laptop dhclient: bound to 192.168.1.2 -- renewal in 875562841 seconds.
Apr 22 12:50:07 vish-laptop NetworkManager: <info> (wlan0): device state change: 7 -> 8 (reason 0)
Apr 22 12:50:07 vish-laptop NetworkManager: <info> Policy set 'Auto Airtel' (wlan0) as default for routing and DNS.
Apr 22 12:50:07 vish-laptop NetworkManager: <info> Activation (wlan0) successful, device activated.
Apr 22 12:50:07 vish-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Apr 22 12:50:08 vish-laptop postfix/master[1071]: reload -- version 2.7.0, configuration /etc/postfix
Apr 22 12:50:08 vish-laptop ntpdate[31357]: no servers can be used, exiting
Apr 22 12:50:12 vish-laptop kernel: [85864.125417] wlan0: no IPv6 routers present
When i notice the wireless has disconnected , the only option I have is to deselect the " Enable Wireless " and to enable it again.
Once i disable and enable it connects back.
Otherwise it just stays in stage2 connecting phase and tries to reconnect, making no progress..
Also this is very random and I'm not sure what triggers it.
Maybe It might have, something to do with Bug 565981 and the memory problems?[just a stab in the dark ;-) ]
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: network-manager 0.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
CheckboxSubmission: a488dc8580a64da042cc99114e54d55a
CheckboxSystem: 5484a8dd99f006173bd2ac53fa4837c2
Date: Thu Apr 22 12:54:25 2010
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
IpRoute:
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 2
169.254.0.0/16 dev wlan0 scope link metric 1000
default via 192.168.1.1 dev wlan0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: network-manager |
Binary package hint: network-manager
Since update :
network-manager (0.8-0ubuntu2) to 0.8-0ubuntu3
or
network-manager-pptp (0.8-0ubuntu1) to 0.8-0ubuntu2
network-manager-pptp-gnome (0.8-0ubuntu1) to 0.8-0ubuntu2
I have been noticing the following errors and wireless just disconnects for no reason:
http://launchpadlibrarian.net/45007594/syslog.log
When i notice the wireless has disconnected , the only option I have is to deselect the " Enable Wireless " and to enable it again.
Once i disable and enable it connects back.
Otherwise it just stays in stage2 connecting phase and tries to reconnect, making no progress..
Also this is very random and I'm not sure what triggers it.
Maybe It might have, something to do with Bug 565981 and the memory problems?[just a stab in the dark ;-) ]
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: network-manager 0.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
CheckboxSubmission: a488dc8580a64da042cc99114e54d55a
CheckboxSystem: 5484a8dd99f006173bd2ac53fa4837c2
Date: Thu Apr 22 12:54:25 2010
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
IpRoute:
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 2
169.254.0.0/16 dev wlan0 scope link metric 1000
default via 192.168.1.1 dev wlan0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: network-manager |
|
| 2010-05-30 06:42:15 |
Vish |
network-manager (Ubuntu): status |
New |
Incomplete |
|
| 2010-10-21 20:23:38 |
Jean-Baptiste Lallement |
tags |
apport-bug i386 lucid regression-potential |
apport-bug i386 lucid |
|
| 2010-11-13 13:06:12 |
Vish |
network-manager (Ubuntu): status |
Incomplete |
Invalid |
|
