Hard(?) lock when reassociating ath with wpa_supplicant on RELENG_7

[Sam Leffler]

Alexandre "Sunny" Kovalenko wrote:
> I seem to be able to lock my machine by going into wpa_cli and asking it
> to 'reassoc'. The reason for question mark after "hard" is that debug
> information (caused by wlandebug and athdebug) is being printed on the
> console. The only way to get machine's attention is to hold power button
> for 8 seconds.

So this is just livelock due to console debug msgs.

> 
> Note: manual reassociation is just the handy way to reproduce the
> problem -- I have had machine locking up on me the whole day long
> completely on its own.
> 
> Below are, what I think, relevant pieces of information. If anything is
> missing, please, chastise me appropriately and will do my best to
> provide. I have rigged firewire console, but am unable to break into the
> debugger locally or remotely.

I see no log msgs.

> 
> While I am on the subject, I would appreciate couple of the
> troubleshooting suggestions:
> * is there any way to get sysctl dev.ath.0.debug to appear, other then
> defining ATH_DEBUG in something like /usr/src/sys/dev/ath/ah_osdep.h?

options ATH_DEBUG

> * is there minimal, but still usable mask for athdebug and wlandebug? I
> have started with 0xFFFFFFFF and kept trimming likely high-volume
> settings until output slowed down to the reasonable pace.

Why do you want debug msgs from ath?  The debug msgs from wlandebug 
depend on what you're trying to debug.

I suggest that when debugging you start from the highest layer and move 
downward.  If you can't find what you need in a wpa_supplicant log then 
turn on msgs in net80211 with wlandebug.  If that doesn't tell you what 
you need then move to the driver.  Blindly turning everything on can 
easily livelock your system.  For high volume msgs I often do something 
like:

athdebug +intr; sleep 1; athdebug -intr

or

athdebug +intr; read x; athdebug -intr

so a carriage return will disable msgs.


> * what facility does wpa_supplicant use, when forced to syslog by -s
> switch?

trouble% cd /data/freebsd/head/contrib/wpa_supplicant/
trouble% grep openlog *.c
common.c:	openlog("wpa_supplicant", LOG_PID | LOG_NDELAY, LOG_DAEMON);


> 
> =======================================================================
> 
> * OS: 
> RELENG_7 cvsup'ed on May 11th @ 15:30EST, if_ath is loaded as the module
> 
> * HW: 
> ath0 at pci0:3:0:0:	class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01
> hdr=0x00
>     vendor     = 'Atheros Communications Inc.'
>     device     = 'AR5212 Atheros AR5212 802.11abg wireless'
>     class      = network
>     subclass   = ethernet
> ath0: <Atheros 5212> mem 0xedf00000-0xedf0ffff irq 17 at device 0.0 on
> pci3
> ath0: [ITHREAD]
> ath0: using obsoleted if_watchdog interface
> ath0: Ethernet address: xx:xx:xx:xx:xx:xx
> ath0: mac 10.3 phy 6.1 radio 10.2
> 
> * Debug settings:
> net.wlan.0.debug:
> 0xdfffffff<11n,debug,crypto,input,xrate,elemid,node,assoc,auth,scan,output,state,power,dot1x,dot1xsm,radius,raddump,radkeys,wpa,acl,wme,superg,doth,inact,roam,rate>
> dev.ath.0.debug:
> 0xffef8ff0<rate,reset,mode,beacon,watchdog,beacon_proc,calibrate,keycache,state,node,ff,dfs,fatal>
> 
> * Console output (somewhat trimmed) is attached -- last group of
> messages keeps repeating until I power down the machine.
> 
> * Output of 'wpa_supplicant -Dbsd -iath0 -d -d -K
> -c/etc/wpa_supplicant.conf' (hand transcribed) is:
> <complaining that it did not find any AP broadcasting needed SSID>
> Starting AP scan (specific SSID)
> Scan SSID = hexdump_ascii (len = NN)
> 	xx xx xx xx xx xx
> 
> * /etc/wpa_supplicant.conf is attached
> 
> * Setup: two stations with the identical SSID: Linksys WRT54Gv8 (running
> dd-wrt micro) at about 50' and Zyxel P-330W at about 20'. 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"