Date: Mon, 14 Jun 2010 04:49:09 -0700 From: Rui Paulo <rpaulo@freebsd.org> To: =?iso-8859-1?Q?Ulrich_Sp=F6rlein?= <uqs@spoerlein.net> Cc: freebsd-current@freebsd.org, Jakub Lach <jakub_lach@mailplus.pl> Subject: Re: wpa_supplicant update? CTRL-EVENT-SCAN-RESULTS Message-ID: <A79E040B-2544-490A-A8F8-419FE991E3FE@freebsd.org> In-Reply-To: <20100614101154.GC3632@acme.spoerlein.net> References: <28870665.post@talk.nabble.com> <2BD1167C-E2B3-49FA-89D0-7B1DA487BB71@FreeBSD.org> <20100614101154.GC3632@acme.spoerlein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14 Jun 2010, at 03:11, Ulrich Sp=F6rlein wrote: > On Sun, 13.06.2010 at 12:03:05 -0700, Rui Paulo wrote: >> On 13 Jun 2010, at 04:23, Jakub Lach wrote: >>=20 >>>=20 >>> Hello. >>>=20 >>> Is update of wpa_supplicant planned?=20 >>>=20 >>> Current version in STABLE as well as CURRENT =20 >>> (v0.6.8) is suffering from CTRL-EVENT-SCAN-RESULTS >>> log spam. >>>=20 >>> If it's the same problem, looks like it's fixed in v0.6.10 >>>=20 >>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D539915 >>=20 >> I'll likely work on this soon. >=20 > Great news, >=20 > btw, are you aware of WPA problems with the iwi(4) driver? I had no > problems and good performance early this year, but since March or so, > the driver gets stuck regularly. For example I can no longer boot up > with if_iwi loaded and the WPA bits in rc.conf, as the immediate = startup > of wpa_supplicant will somehow wedge things (I have a couple of traces > for this): ifconfig wlan0 down will get stuck, killing wpa_supplicant = is > no longer possible, etc. >=20 > What works for me (please don't laugh): > - boot up without if_iwi loaded > - disable wlan radio using hotkey > - load if_iwi, devd will automatically start wpa_supplicant > - wpa_supplicant will eventually (1-2 min) associate with my ath(4) > based AP > - turn on radio per hotkey > - check ifconfig wlan0 to see if everything is alright > - ifconfig lagg0 laggport wlan0 for wired/wireless roaming. >=20 > Here's a trace of when 'ifconfig wlan0 down' was stuck, too bad the > trace for wpa_supplicant doesn't show up in the textdump >=20 > Tracing command ifconfig pid 1894 tid 100121 td 0xc4d76c30 > sched_switch(c4d76c30,0,104,191,3593fa53,...) at sched_switch+0x2fc > mi_switch(104,0,c092b242,1eb,5c,...) at mi_switch+0x200 > sleepq_switch(c4d76c30,0,c092b242,260,0,...) at sleepq_switch+0x15f > sleepq_wait(c41862d8,5c,c091c518,0,0,...) at sleepq_wait+0x63 > _sleep(c41862d8,c3f02494,5c,c091c518,0,...) at _sleep+0x365 > taskqueue_drain(c3f02480,c41862d8,48d,c0935b10,fb51cab8,...) at = taskqueue_drain+0xf5 > ieee80211_vap_detach(c4186000,fb51cae4,0,fb51cacc,c06bac77,...) at = ieee80211_vap_detach+0x78 > iwi_vap_delete(c4186000,fb51cae4,c0694457,c413f000,c413f000,...) at = iwi_vap_delete+0x12 > wlan_clone_destroy(c413f000,c413f000,c413f000,c413f000,fb51cb10,...) = at wlan_clone_destroy+0x17 > ifc_simple_destroy(c099c260,c413f000,c09362cc,105,c099c290,...) at = ifc_simple_destroy+0x27 > if_clone_destroyif(c099c260,c413f000,c09362cc,e0,c42225c0,...) at = if_clone_destroyif+0x12e > if_clone_destroy(c42225c0,19c,c0954c7d,c091ead3,3,...) at = if_clone_destroy+0xa2 > ifioctl(c3c4f670,80206979,c42225c0,c4d76c30,c4415100,...) at = ifioctl+0x476 > soo_ioctl(c44433b8,80206979,c42225c0,c44b2700,c4d76c30,...) at = soo_ioctl+0x40f > kern_ioctl(c4d76c30,3,80206979,c42225c0,6230b0,...) at = kern_ioctl+0x1fd > ioctl(c4d76c30,fb51ccf8,c09615aa,c09492c0,c4d6d2a8,...) at ioctl+0x134 > syscall(fb51cd38) at syscall+0x220 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (54, FreeBSD ELF32, ioctl), eip =3D 0x281cbb13, esp =3D = 0xbfbfe44c, ebp =3D 0xbfbfe468 --- Please update your sources. I think this was fixed a while ago. -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A79E040B-2544-490A-A8F8-419FE991E3FE>