[Voyage-linux] Problems with alix 2d3 and madwifi on voyage-current (lenny)

[Juergen Adolph]

Hi Punky,

following my test results:

r3942.20090205haltesting
------------------------

I started a download and after 60s the download failed and the connection to the AP
breaks. After reconnect the download failed again and a connect with a another client
is not possible (stuck beacon error).


[  735.259373] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  737.161583] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  738.961892] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  742.504311] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  744.304613] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  749.586032] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  751.999771] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  756.975301] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  758.785858] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  765.297451] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  766.996140] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  792.963733] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  794.673210] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  797.907949] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  801.039313] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  802.635212] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  805.666912] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  807.467211] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  809.574224] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  812.603327] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  814.403627] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  816.101530] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  819.134258] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  832.198093] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  833.895019] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  872.351043] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  874.152179] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)
[  875.564289] wifi0: ath_rxorn_tasklet: Receive FIFO overrun; resetting.
[  877.219129] wifi0: ath_rxorn_tasklet: Receive FIFO overrun; resetting.
[  879.047774] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)


Feb 24 18:17:02 alix hostapd: ath0: STA 00:1c:d6:2d:f8:19 IEEE 802.11: associated
Feb 24 18:17:02 alix hostapd: ath0: STA 00:1c:d6:2d:f8:19 WPA: pairwise key handshake completed (RSN)
Feb 24 18:17:02 alix dnsmasq[3154]: DHCPDISCOVER(ath0) 0.0.0.0 00:1c:d6:2d:f8:19
Feb 24 18:17:02 alix dnsmasq[3154]: DHCPOFFER(ath0) 192.168.3.101 00:1c:d6:2d:f8:19
Feb 24 18:17:03 alix vmunix: [  735.259373] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting (beacon miss count: 11)


r3942hal
--------
after a few seconds, the connection breaks. I can't reconnect to the AP - only a hostapd restart helped.
Feb 24 18:55:29 alix hostapd: ath0: STA 00:1e:c2:b9:21:36 IEEE 802.11: deauthenticated due to local deauth request

r3952.20090213free
------------------
behave exactly the same as the r3942hal
Feb 24 20:04:06 alix hostapd: ath0: STA 00:1e:c2:b9:21:36 IEEE 802.11: deauthenticated due to local deauth request


Is this a problem with madwifi or hostapd or interaction with both ?!

Regards,
Juergen

----- "Kim-man 'Punky' TSE" <punkytse at punknix.com> schrieb:

> Hi Juergen,
> 
> I think it is quite important highlight that even if there are stuck 
> beacons reported, the AP is still functional although the client may 
> experienced reassociation intermittently. When I used trunk branch,
> the 
> AP is not recoverable and require a reboot.
> 
> I see from your can that the stuck beacon appears 6 times within 10 
> seconds.  If it is recoverable, you should wait to see how often it 
> would occur again.
> 
> Regards,
> Punky
> 
> 
> Juergen Adolph wrote:
> > ----- "Kim-man 'Punky' TSE" <punkytse at punknix.com> schrieb:
> >
> >   
> >> Hi Juergen,
> >>     
> >
> > Hi Punky,
> >  
> >   
> >> I encountered one stuck beacon after 1 day of running.
> >>     
> >
> > I found 6 errors in 12h:
> > is this long enough or should I longer test?
> >
> > [  301.470651] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting
> (beacon miss count: 11)
> > [  303.282184] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting
> (beacon miss count: 11)
> > [  304.980084] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting
> (beacon miss count: 11)
> > [  306.790151] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting
> (beacon miss count: 11)
> > [  308.692854] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting
> (beacon miss count: 11)
> > [  310.493159] wifi0: ath_bstuck_tasklet: Stuck beacon; resetting
> (beacon miss count: 11)
> >
> >   
> >> The download 
> >> didn't break and the link is recoverable, so I continue to run it
> until tonight.
> >>     
> >
> > yes, here also so. 
> >
> > Regards,
> > Jürgen
> >
> >   
> 
> 
> -- 
> Regards,
> Punky
> 
> Voyage Solutions (http://solution.voyage.hk)
> * Embedded Solutions and Systems
>   - Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
>   - Network Engineering, Development Platform and Consultation

-- 
Juergen Adolph
----------------------------------------------------------------------------
PGP-KeyID: 0x4A77083A