From: Terry Hardie (terryh_at_orcas.net)
Date: 2002-06-11 05:33:15 UTC
On Mon, 10 Jun 2002, Jouni Malinen wrote:
> On Mon, Jun 10, 2002 at 12:46:23PM +1000, wayne wrote:
> > wlan0: timeout on waiting pending transmit command..
> > wlan0: handle_pspoll - to BAP0 failed
> > hfa384x_cmd: timeout on waiting pending TX
> > wlan0: hfa384x_set_rid: CMDCODE_ACCESS_WRITE failed (res=-110, rid=fc40,
> > len=2)
> > hostap_cs: wlan0: resetting card
> OK, this is an issue with power saving mode and buffering packets to
> stations. I haven't tested the driver with stations using PS for a
> long time. It did not apparently survive
> PRISM2_USE_CMD_COMPL_INTERRUPT related changes without breaking..
> The driver tried to setup STA's TIM bit just after performing transmit
> command. However, with cmd completion events, the next command should
> not be started before the previous one has completed. This leads to
> the reported timeouts. In addition, there's another problem that can
> occur if the station has many buffered frames and it moves into non-PS
Whatever you changed in the latest CVS tree has fixed my freezing problem. (I was getting the aforementioned error when it froze)
I was trying it with a zoom card and a linksys, and after a few seconds of high traffic, the system would get dropped. Only on Windows XP clients (I suspect earlier version of windows didn't ask for power saving facilities from the AP)
Thanks very much!
--- Terry Hardie terry_at_net.com SHOUTip Engineering Product Manager ICQ#: 977679 net.com, 6530 Paseo Padre Parkway Mailstop #2207, Fremont, CA 94555, USA V: +1-510-574-2366