15315 – [ath9k] Reconnection to wireless network fails until rmmod/modprobe.

Bug 15315 - [ath9k] Reconnection to wireless network fails until rmmod/modprobe.

Summary: [ath9k] Reconnection to wireless network fails until rmmod/modprobe.

Status:	RESOLVED OBSOLETE

Alias:	None

Product:	Drivers
Classification:	Unclassified
Component:	network-wireless (show other bugs)
Hardware:	All Linux

Importance:	P1 high
Assignee:	drivers_network-wireless@kernel-bugs.osdl.org

URL:
Keywords:

Depends on:
Blocks:

Reported:	2010-02-15 16:25 UTC by hayarms
Modified:	2013-11-20 13:27 UTC (History)
CC List:	7 users (show)

See Also:
Kernel Version:	2.6.39
Subsystem:
Regression:	No
Bisected commit-id:

Attachments
lspci (1.65 KB, text/plain) 2010-05-13 04:30 UTC, borsten	Details
link to netbook on samsung website (120 bytes, text/plain) 2010-05-13 04:42 UTC, borsten	Details
dmesg error log (11.37 KB, text/plain) 2011-08-07 19:44 UTC, Filipe Vieira	Details
dmesg error log (2.75 KB, text/plain) 2011-08-07 19:48 UTC, Filipe Vieira	Details
Add an attachment (proposed patch, testcase, etc.)

Description hayarms 2010-02-15 16:25:06 UTC

I'm using Archlinux with the latest kernel 2.6.32.8 and I have problems with the ath9k driver.

This is my card on an Asus EEEPC 1000HE :
01:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)


The problem is this. The driver connects and is stable the first time I do so, but if I disconnect to a network for some reason (for example to change network, or because I just didn't need a connection for some time) then I can't reconnect to a network anymore until I do a : rmmod ath9k && modprobe ath9k 

I can still sense networks in this state, but I can't connect to any of them, because dhcpcd just times out.

This is the output of dmesg when this happens:

wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
wlan0: deauthenticating from 00:1e:2a:1d:40:1a by local choice (reason=3)
ADDRCONF(NETDEV_UP): wlan0: link is not ready

As you can see the wireless associates with the network, but then giveup the connection after some time. This continues to happen until I rmmod the driver.

There's a bug report about this problem in the Archlinux bug tracking system at this address : http://bugs.archlinux.org/task/18011?string=wicd&project=1&type[0]=&sev[0]=&pri[0]=&due[0]=&reported[0]=&cat[0]=&status[0]=open&percent[0]=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=
The bug report is referred to Wicd, but the problem does happen with all the versions of Wicd and also when Wicd is not involved, so it isn't a Wicd bug. It also begun to happen from kernel 2.6.32.2

There's also another problem. If I switch the Kill Switch on and then reenable the Wifi the wireless card just dies. I can't see networks anymore and connect to any of them . rmmod the driver and reloading it doesn't works. I just have to reboot in this case.

This is the output of "ifconfig wlan0 up" in this state:

ifconfig wlan0 up
SIOCSIFFLAGS: Unknown error 132

Marcello Maggioni

Comment 1 John W. Linville 2010-03-17 15:33:50 UTC

Error 132 is ERFKILL, indicating that something things you still have your kill switch enabled.  What sort of laptop is this?  The issue could relate to the platform driver.

Any input from the ath9k guys?

Comment 2 borsten 2010-05-04 04:36:45 UTC

I have the same problem on a samsung nb30 with gentoo.
after shutting down wlan0 i get :

Could not set interface wlan0 flags: Unknown error 132
Failed to initialize driver interface

rfkill says softblock after shutdown.

tried 2.6.34-rc6-git1 and 2.6.33-gentoo-r1.

reproduceable with 
/etc/init.d/net.wlan0 restart 
rfkill list

Comment 3 John W. Linville 2010-05-12 18:42:52 UTC

What sort of laptop is involved?

Comment 4 borsten 2010-05-13 04:30:02 UTC

Created attachment 26363 [details]
lspci

Comment 5 borsten 2010-05-13 04:42:10 UTC

Created attachment 26364 [details]
link to netbook on samsung website

Comment 6 borsten 2010-05-13 04:50:59 UTC

there is a staging driver for samsung n130 netbooks who modifies the start of the wlan-chip to reset rfkill before restarting, but this driver is not loading on my machine because of an incompatible bios for rebinding the keymap and stuff like that. should be easier to include a patch directly in the ath9k driver instead of creating a special driver for each new platform since it seems to be the same problem on a set of notebooks.

Comment 7 John W. Linville 2010-05-25 18:01:56 UTC

Rfkill buttons generally are controlled by the platform, not the wireless driver.  In any case, the driver for your laptop should be loading.

Comment 8 borsten 2010-10-09 06:29:47 UTC

The Samsung N130 Driver is not loading since it is for N128 and N130 Series, mine is an NB30 based on Intel Pineview instead of i945 chipsets on N128 and N130.
Message while Loading the module with added "NB30" section says:
samsung_laptop: found model 'NB30'
This computer does not support SABI

Comment 9 Filipe Vieira 2011-08-07 19:43:22 UTC

Kubuntu 11.04 64bits
2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:07:17 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

I have a similar problem. I connect and after a few hours the process of renewing the connection or DHCP lease fails. Knetowrkmanager understands it as a authentication error, but it's not.

I also have to run rmmod/modprobe ath9k to fix the problem.

Comment 10 Filipe Vieira 2011-08-07 19:44:56 UTC

Created attachment 67912 [details]
dmesg error log

Comment 11 Filipe Vieira 2011-08-07 19:48:15 UTC

Created attachment 67922 [details]
dmesg error log 

After this error the connection is completely impossible and I have to rmmod/modprobe.

PS: Sorry about the flood, first time reporting a bug here :), forgive me.

Comment 12 Jimmy Cao 2011-09-05 04:08:59 UTC

I have this problem too, on kernel 2.6.39-2
(Eee PC 1000HE, Atheros AR928X)

Comment 13 Account Deleted 2012-03-05 20:13:55 UTC

This Bug affects me, too.
lspci -nn delivers this device:

02:07.0 Network controller [0280]: Atheros Communications Inc. AR5008 Wireless Network Adapter [168c:0023] (rev 01)

uname -a:

Linux alpha 3.0.0-16-generic #28-Ubuntu SMP Fri Jan 27 17:44:39 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

I'm sure this bug exists for me since I've got this wireless card. After third devices I think wireless lan never will work for me...

Comment 14 Filipe Vieira 2012-05-06 23:14:18 UTC

Please, fix this. Every kernel makes a regression on it. 




lspci -vvv -s 07:01.0 
07:01.0 Network controller: Atheros Communications Inc. AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn] (rev 01)
        Subsystem: Atheros Communications Inc. Device 3071
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 168, Cache Line Size: 256 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at fbef0000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: <access denied>
        Kernel driver in use: ath9k
        Kernel modules: ath9k
uname -a
Linux piobox 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
May  6 19:38:00 piobox kernel: [ 1380.742692] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:38:00 piobox kernel: [ 1380.742694] cfg80211: Disabling freq 2484 MHz
May  6 19:38:00 piobox kernel: [ 1380.742698] cfg80211: World regulatory domain updated:
May  6 19:38:00 piobox kernel: [ 1380.742700] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
May  6 19:38:00 piobox kernel: [ 1380.742703] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May  6 19:38:00 piobox kernel: [ 1380.742706] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May  6 19:38:00 piobox kernel: [ 1380.742709] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May  6 19:38:00 piobox kernel: [ 1380.742712] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May  6 19:38:00 piobox kernel: [ 1380.742715] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May  6 19:38:00 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: disconnected -> scanning
May  6 19:38:01 piobox wpa_supplicant[1235]: Trying to authenticate with 7c:4f:b5:ef:7f:59 (SSID='centuplomegao' freq=2412 MHz)
May  6 19:38:01 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: scanning -> authenticating
May  6 19:38:01 piobox kernel: [ 1381.937346] wlan0: authenticate with 7c:4f:b5:ef:7f:59 (try 1)
May  6 19:38:01 piobox kernel: [ 1382.134864] wlan0: authenticate with 7c:4f:b5:ef:7f:59 (try 2)
May  6 19:38:01 piobox wpa_supplicant[1235]: Trying to associate with 7c:4f:b5:ef:7f:59 (SSID='centuplomegao' freq=2412 MHz)
May  6 19:38:01 piobox kernel: [ 1382.310597] wlan0: authenticated
May  6 19:38:01 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: authenticating -> associating
May  6 19:38:01 piobox kernel: [ 1382.314566] wlan0: associate with 7c:4f:b5:ef:7f:59 (try 1)
May  6 19:38:01 piobox kernel: [ 1382.513982] wlan0: associate with 7c:4f:b5:ef:7f:59 (try 2)
May  6 19:38:02 piobox kernel: [ 1382.713441] wlan0: associate with 7c:4f:b5:ef:7f:59 (try 3)
May  6 19:38:02 piobox wpa_supplicant[1235]: Associated with 7c:4f:b5:ef:7f:59
May  6 19:38:02 piobox kernel: [ 1382.747108] wlan0: RX ReassocResp from 7c:4f:b5:ef:7f:59 (capab=0x431 status=0 aid=4)
May  6 19:38:02 piobox kernel: [ 1382.747112] wlan0: associated
May  6 19:38:02 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: associating -> associated
May  6 19:38:02 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
May  6 19:38:03 piobox wpa_supplicant[1235]: WPA: Key negotiation completed with 7c:4f:b5:ef:7f:59 [PTK=CCMP GTK=TKIP]
May  6 19:38:03 piobox wpa_supplicant[1235]: CTRL-EVENT-CONNECTED - Connection to 7c:4f:b5:ef:7f:59 completed (reauth) [id=0 id_str=]
May  6 19:38:03 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
May  6 19:39:01 piobox CRON[23381]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
May  6 19:40:01 piobox CRON[26916]: (root) CMD ([ -x /etc/init.d/mythtv-status ] && /etc/init.d/mythtv-status reload > /dev/null)
May  6 19:40:01 piobox CRON[26917]: (www-data) CMD (php /usr/share/cacti/site/poller.php >/dev/null 2>/var/log/cacti/poller-error.log)
May  6 19:41:00 piobox wpa_supplicant[1235]: CTRL-EVENT-DISCONNECTED bssid=7c:4f:b5:ef:7f:59 reason=4
May  6 19:41:00 piobox kernel: [ 1560.648641] cfg80211: All devices are disconnected, going to restore regulatory settings
May  6 19:41:00 piobox kernel: [ 1560.648648] cfg80211: Restoring regulatory settings
May  6 19:41:00 piobox kernel: [ 1560.648655] cfg80211: Calling CRDA to update world regulatory domain
May  6 19:41:00 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: completed -> disconnected
May  6 19:41:00 piobox kernel: [ 1560.652800] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652805] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652808] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652812] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652815] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652818] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652821] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652824] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652827] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652830] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652833] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652836] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652839] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652842] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652845] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652848] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652851] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652854] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652857] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652860] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652863] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652866] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652869] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652872] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652875] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
May  6 19:41:00 piobox kernel: [ 1560.652878] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652881] cfg80211: Disabling freq 2484 MHz
May  6 19:41:00 piobox kernel: [ 1560.652884] cfg80211: World regulatory domain updated:
May  6 19:41:00 piobox kernel: [ 1560.652886] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
May  6 19:41:00 piobox kernel: [ 1560.652889] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652893] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652896] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652899] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May  6 19:41:00 piobox kernel: [ 1560.652902] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May  6 19:41:00 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: disconnected -> scanning
May  6 19:41:01 piobox wpa_supplicant[1235]: Trying to authenticate with 7c:4f:b5:ef:7f:59 (SSID='centuplomegao' freq=2412 MHz)
May  6 19:41:01 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: scanning -> authenticating
May  6 19:41:01 piobox kernel: [ 1561.859272] wlan0: authenticate with 7c:4f:b5:ef:7f:59 (try 1)
May  6 19:41:01 piobox kernel: [ 1562.057038] wlan0: authenticate with 7c:4f:b5:ef:7f:59 (try 2)
May  6 19:41:02 piobox kernel: [ 1562.256391] wlan0: authenticate with 7c:4f:b5:ef:7f:59 (try 3)
May  6 19:41:02 piobox kernel: [ 1562.455996] wlan0: authentication with 7c:4f:b5:ef:7f:59 timed out
May  6 19:41:03 piobox NetworkManager[1216]: <info> (wlan0): roamed from BSSID 7C:4F:B5:EF:7F:59 (centuplomegao) to (none) ((none))
May  6 19:41:08 piobox wpa_supplicant[1235]: Trying to authenticate with 7c:4f:b5:ef:7f:59 (SSID='centuplomegao' freq=2412 MHz)
May  6 19:41:08 piobox kernel: [ 1568.678812] wlan0: direct probe to 7c:4f:b5:ef:7f:59 (try 1/3)
May  6 19:41:08 piobox kernel: [ 1568.880406] wlan0: direct probe to 7c:4f:b5:ef:7f:59 (try 2/3)
May  6 19:41:08 piobox kernel: [ 1569.079927] wlan0: direct probe to 7c:4f:b5:ef:7f:59 (try 3/3)
May  6 19:41:09 piobox kernel: [ 1569.279455] wlan0: direct probe to 7c:4f:b5:ef:7f:59 timed out
May  6 19:41:14 piobox wpa_supplicant[1235]: Trying to authenticate with 7c:4f:b5:ef:7f:59 (SSID='centuplomegao' freq=2412 MHz)
May  6 19:41:14 piobox kernel: [ 1575.146795] wlan0: authenticate with 7c:4f:b5:ef:7f:59 (try 1)
May  6 19:41:15 piobox kernel: [ 1575.344662] wlan0: authenticate with 7c:4f:b5:ef:7f:59 (try 2)
May  6 19:41:15 piobox NetworkManager[1216]: <warn> (wlan0): link timed out.
May  6 19:41:15 piobox NetworkManager[1216]: <info> (wlan0): device state change: activated -> disconnected (reason 'supplicant-timeout') [100 30 11]
May  6 19:41:15 piobox NetworkManager[1216]: <info> (wlan0): deactivating device (reason 'supplicant-timeout') [11]
May  6 19:41:15 piobox kernel: [ 1575.544195] wlan0: authenticate with 7c:4f:b5:ef:7f:59 (try 3)
May  6 19:41:15 piobox wpa_supplicant[1235]: Trying to associate with 7c:4f:b5:ef:7f:59 (SSID='centuplomegao' freq=2412 MHz)
May  6 19:41:15 piobox kernel: [ 1575.549707] wlan0: authenticated
May  6 19:41:15 piobox kernel: [ 1575.555782] wlan0: associate with 7c:4f:b5:ef:7f:59 (try 1)
May  6 19:41:15 piobox NetworkManager[1216]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 7936
May  6 19:41:15 piobox avahi-daemon[1227]: Withdrawing address record for fe80::da5d:4cff:feb4:5011 on wlan0.
May  6 19:41:15 piobox avahi-daemon[1227]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::da5d:4cff:feb4:5011.
May  6 19:41:15 piobox avahi-daemon[1227]: Interface wlan0.IPv6 no longer relevant for mDNS.
May  6 19:41:15 piobox avahi-daemon[1227]: Withdrawing address record for 192.168.1.4 on wlan0.
May  6 19:41:15 piobox avahi-daemon[1227]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.4.
May  6 19:41:15 piobox kernel: [ 1575.613686] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May  6 19:41:15 piobox avahi-daemon[1227]: Interface wlan0.IPv4 no longer relevant for mDNS.
May  6 19:41:15 piobox dnsmasq[8121]: exiting on receipt of SIGTERM
May  6 19:41:15 piobox NetworkManager[1216]: <info> DNS: starting dnsmasq...
May  6 19:41:15 piobox NetworkManager[1216]: <info> (wlan0): writing resolv.conf to /sbin/resolvconf
May  6 19:41:15 piobox dnsmasq[31193]: started, version 2.59 cache disabled
May  6 19:41:15 piobox dnsmasq[31193]: compile time options: IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN
May  6 19:41:15 piobox dnsmasq[31193]: warning: no upstream servers configured
May  6 19:41:15 piobox dbus[1175]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
May  6 19:41:15 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: authenticating -> associating
May  6 19:41:15 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: associating -> disconnected
May  6 19:41:15 piobox NetworkManager[1216]: <info> Auto-activating connection 'centuplomegao'.
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) starting connection 'centuplomegao'
May  6 19:41:15 piobox NetworkManager[1216]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May  6 19:41:15 piobox NetworkManager[1216]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0/wireless): access point 'centuplomegao' has security, but secrets are required.
May  6 19:41:15 piobox NetworkManager[1216]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May  6 19:41:15 piobox dbus[1175]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May  6 19:41:15 piobox kernel: [ 1575.751651] wlan0: associate with 7c:4f:b5:ef:7f:59 (try 2)
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May  6 19:41:15 piobox NetworkManager[1216]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May  6 19:41:15 piobox NetworkManager[1216]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0/wireless): connection 'centuplomegao' has security, and secrets exist.  No new secrets needed.
May  6 19:41:15 piobox NetworkManager[1216]: <info> Config: added 'ssid' value 'centuplomegao'
May  6 19:41:15 piobox NetworkManager[1216]: <info> Config: added 'scan_ssid' value '1'
May  6 19:41:15 piobox NetworkManager[1216]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May  6 19:41:15 piobox NetworkManager[1216]: <info> Config: added 'psk' value '<omitted>'
May  6 19:41:15 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May  6 19:41:15 piobox NetworkManager[1216]: <info> Config: set interface ap_scan to 1
May  6 19:41:15 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: disconnected -> scanning
May  6 19:41:15 piobox kernel: [ 1575.955161] wlan0: associate with 7c:4f:b5:ef:7f:59 (try 3)
May  6 19:41:15 piobox kernel: [ 1576.154682] wlan0: association with 7c:4f:b5:ef:7f:59 timed out
May  6 19:41:16 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: scanning -> disconnected
May  6 19:41:16 piobox ntpd[8978]: Deleting interface #4 wlan0, fe80::da5d:4cff:feb4:5011#123, interface stats: received=0, sent=0, dropped=0, active_time=380 secs
May  6 19:41:16 piobox ntpd[8978]: Deleting interface #3 wlan0, 192.168.1.4#123, interface stats: received=27, sent=30, dropped=0, active_time=380 secs
May  6 19:41:16 piobox ntpd[8978]: 91.189.94.4 interface 192.168.1.4 -> (none)
May  6 19:41:16 piobox ntpd[8978]: 200.144.121.33 interface 192.168.1.4 -> (none)
May  6 19:41:16 piobox ntpd[8978]: 200.186.125.195 interface 192.168.1.4 -> (none)
May  6 19:41:16 piobox ntpd[8978]: 200.199.205.149 interface 192.168.1.4 -> (none)
May  6 19:41:16 piobox ntpd[8978]: 150.162.55.3 interface 192.168.1.4 -> (none)
May  6 19:41:16 piobox ntpd[8978]: peers refreshed
May  6 19:41:16 piobox wpa_supplicant[1235]: Trying to authenticate with 7c:4f:b5:ef:7f:59 (SSID='centuplomegao' freq=2412 MHz)
May  6 19:41:16 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: disconnected -> authenticating
May  6 19:41:16 piobox kernel: [ 1576.950530] wlan0: authenticate with 7c:4f:b5:ef:7f:59 (try 1)
May  6 19:41:16 piobox kernel: [ 1577.148262] wlan0: authenticate with 7c:4f:b5:ef:7f:59 (try 2)
May  6 19:41:17 piobox kernel: [ 1577.351693] wlan0: authenticate with 7c:4f:b5:ef:7f:59 (try 3)
May  6 19:41:17 piobox wpa_supplicant[1235]: Trying to associate with 7c:4f:b5:ef:7f:59 (SSID='centuplomegao' freq=2412 MHz)
May  6 19:41:17 piobox kernel: [ 1577.454674] wlan0: authenticated
May  6 19:41:17 piobox kernel: [ 1577.458770] wlan0: associate with 7c:4f:b5:ef:7f:59 (try 1)
May  6 19:41:17 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: authenticating -> associating
May  6 19:41:17 piobox kernel: [ 1577.655036] wlan0: associate with 7c:4f:b5:ef:7f:59 (try 2)
May  6 19:41:17 piobox kernel: [ 1577.858536] wlan0: associate with 7c:4f:b5:ef:7f:59 (try 3)
May  6 19:41:17 piobox kernel: [ 1578.056542] wlan0: RX ReassocResp from 7c:4f:b5:ef:7f:59 (capab=0x431 status=0 aid=4)
May  6 19:41:17 piobox kernel: [ 1578.056547] wlan0: associated
May  6 19:41:17 piobox kernel: [ 1578.057669] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May  6 19:41:17 piobox wpa_supplicant[1235]: Associated with 7c:4f:b5:ef:7f:59
May  6 19:41:17 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: associating -> associated
May  6 19:41:17 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
May  6 19:41:18 piobox wpa_supplicant[1235]: WPA: Key negotiation completed with 7c:4f:b5:ef:7f:59 [PTK=CCMP GTK=TKIP]
May  6 19:41:18 piobox wpa_supplicant[1235]: CTRL-EVENT-CONNECTED - Connection to 7c:4f:b5:ef:7f:59 completed (reauth) [id=0 id_str=]
May  6 19:41:18 piobox NetworkManager[1216]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
May  6 19:41:18 piobox NetworkManager[1216]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'centuplomegao'.
May  6 19:41:18 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
May  6 19:41:18 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
May  6 19:41:18 piobox NetworkManager[1216]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
May  6 19:41:18 piobox NetworkManager[1216]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May  6 19:41:18 piobox NetworkManager[1216]: <info> dhclient started with pid 31413
May  6 19:41:18 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
May  6 19:41:18 piobox dhclient: Internet Systems Consortium DHCP Client 4.1-ESV-R4
May  6 19:41:18 piobox dhclient: Copyright 2004-2011 Internet Systems Consortium.
May  6 19:41:18 piobox dhclient: All rights reserved.
May  6 19:41:18 piobox dhclient: For info, please visit https://www.isc.org/software/dhcp/
May  6 19:41:18 piobox dhclient: 
May  6 19:41:18 piobox NetworkManager[1216]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
May  6 19:41:18 piobox dhclient: Listening on LPF/wlan0/d8:5d:4c:b4:50:11
May  6 19:41:18 piobox dhclient: Sending on   LPF/wlan0/d8:5d:4c:b4:50:11
May  6 19:41:18 piobox dhclient: Sending on   Socket/fallback
May  6 19:41:18 piobox dhclient: DHCPREQUEST of 192.168.1.4 on wlan0 to 255.255.255.255 port 67
May  6 19:41:19 piobox ntpd[8978]: bind(19) AF_INET6 fe80::da5d:4cff:feb4:5011%3#123 flags 0x11 failed: Cannot assign requested address
May  6 19:41:19 piobox ntpd[8978]: unable to create socket on wlan0 (6) for fe80::da5d:4cff:feb4:5011#123
May  6 19:41:19 piobox ntpd[8978]: failed to init interface for address fe80::da5d:4cff:feb4:5011
May  6 19:41:19 piobox avahi-daemon[1227]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::da5d:4cff:feb4:5011.
May  6 19:41:19 piobox avahi-daemon[1227]: New relevant interface wlan0.IPv6 for mDNS.
May  6 19:41:19 piobox avahi-daemon[1227]: Registering new address record for fe80::da5d:4cff:feb4:5011 on wlan0.*.
May  6 19:41:20 piobox dhclient: DHCPACK of 192.168.1.4 from 192.168.1.1
May  6 19:41:20 piobox dhclient: bound to 192.168.1.4 -- renewal in 33225 seconds.
May  6 19:41:20 piobox NetworkManager[1216]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
May  6 19:41:20 piobox NetworkManager[1216]: <info>   address 192.168.1.4
May  6 19:41:20 piobox NetworkManager[1216]: <info>   prefix 24 (255.255.255.0)
May  6 19:41:20 piobox NetworkManager[1216]: <info>   gateway 192.168.1.1
May  6 19:41:20 piobox NetworkManager[1216]: <info>   nameserver '192.168.1.1'
May  6 19:41:20 piobox NetworkManager[1216]: <info>   domain name 'lan'
May  6 19:41:20 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May  6 19:41:20 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
May  6 19:41:20 piobox avahi-daemon[1227]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.4.
May  6 19:41:20 piobox avahi-daemon[1227]: New relevant interface wlan0.IPv4 for mDNS.
May  6 19:41:20 piobox avahi-daemon[1227]: Registering new address record for 192.168.1.4 on wlan0.IPv4.
May  6 19:41:21 piobox dnsmasq[31193]: exiting on receipt of SIGTERM
May  6 19:41:21 piobox NetworkManager[1216]: <info> DNS: starting dnsmasq...
May  6 19:41:21 piobox NetworkManager[1216]: <info> (wlan0): writing resolv.conf to /sbin/resolvconf
May  6 19:41:21 piobox dnsmasq[31617]: started, version 2.59 cache disabled
May  6 19:41:21 piobox dnsmasq[31617]: compile time options: IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN
May  6 19:41:21 piobox dnsmasq[31617]: using nameserver 192.168.1.1#53
May  6 19:41:21 piobox NetworkManager[1216]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
May  6 19:41:21 piobox NetworkManager[1216]: <info> Policy set 'centuplomegao' (wlan0) as default for IPv4 routing and DNS.
May  6 19:41:21 piobox NetworkManager[1216]: <info> Activation (wlan0) successful, device activated.
May  6 19:41:21 piobox NetworkManager[1216]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
May  6 19:41:22 piobox ntpd[8978]: ntpd exiting on signal 15
May  6 19:41:29 piobox kernel: [ 1589.143087] wlan0: no IPv6 routers present
May  6 19:41:32 piobox ntpdate[31783]: adjust time server 200.186.125.195 offset 0.004185 sec
May  6 19:41:32 piobox ntpd[32401]: ntpd 4.2.6p3@1.2290 Tue Mar  6 15:36:36 UTC 2012 (1)
May  6 19:41:32 piobox ntpd[32402]: proto: precision = 0.105 usec
May  6 19:41:32 piobox ntpd[32402]: ntp_io: estimated max descriptors: 2144, initial socket boundary: 16
May  6 19:41:32 piobox ntpd[32402]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
May  6 19:41:32 piobox ntpd[32402]: Listen and drop on 1 v6wildcard :: UDP 123
May  6 19:41:32 piobox ntpd[32402]: Listen normally on 2 lo 127.0.0.1 UDP 123
May  6 19:41:32 piobox ntpd[32402]: Listen normally on 3 wlan0 192.168.1.4 UDP 123
May  6 19:41:32 piobox ntpd[32402]: Listen normally on 4 wlan0 fe80::da5d:4cff:feb4:5011 UDP 123
May  6 19:41:32 piobox ntpd[32402]: Listen normally on 5 lo ::1 UDP 123
May  6 19:41:32 piobox ntpd[32402]: peers refreshed
May  6 19:41:32 piobox ntpd[32402]: Listening on routing socket on fd #22 for interface updates
May  6 19:43:00 piobox wpa_supplicant[1235]: CTRL-EVENT-DISCONNECTED bssid=7c:4f:b5:ef:7f:59 reason=4

Note You need to log in before you can comment on or make changes to this bug.