On Mon, Aug 06, 2007 at 02:31:02PM +0200, Jukka Salmi wrote:
> Jukka Salmi --> current-users (2007-08-04 16:12:16 +0200):
> > Jukka Salmi --> current-users (2007-08-03 14:42:44 +0200):
> > > Hi,
> > > 
> > > since running 4.99.26 on my i386 laptop, the kernel logs
> > > 
> > > 	ath0: device timeout (txq 1)
> > > 
> > > every few seconds, and several times even lost connection (ifconfig(8)
> > > reporting `status: no network'). Stopping wpa_supplicant, bringing the
> > > interface down and up again and restarting wpa_supplicant seems to
> > > reestablish connection so far.
> > > 
> > > I remember seeing some `ath0: device timeout' messages previously
> > > (4.99.20), but fewer than now, and connection was never lost.
> > 
> > The recently merged "less invasive changes from the vmlocking branch"
> > seem to be the culprit: while a kernel built using sources as of
> > 2007.07.09.20.50.00 works fine, ath(4) looses connection after some
> > minutes when running a kernel built from 2007.07.09.23.00.00 sources.
> 
> Hmm, so far I couldn't reproduce the problem when using WEP or no
> encryption at all. I only see the disconnection when using
> wpa_supplicant (WPA-PSK)...
> 
> >From the APs view it looks as if the client just deauthenticates:
> 
> [...] hostapd: ath0: STA [...] IEEE 802.11: deauthenticated due to local deauth request
> [...] hostapd: ath0: STA [...] IEEE 802.11: deassociated
> 
> My userland is older than the kernel; is this a possible reason for
> the problem I'm seeing? I'll probably rebuild world and check again...

Are the client and the AP both little-endian?  ISTR somebody fixed an
endianness bug in hostapd and/or wpa_supplicant.

I suggest looking very closely at what hostapd and wpa_supplicant can
tell you about the disconnections.  Does a statistic shown by 'ifconfig
-v ath0' increase with the disconnections?

Dave

-- 
David Young             OJC Technologies
dyoung@ojctech.com      Urbana, IL * (217) 278-3933 ext 24