card hangs, not system

Jouni Malinen jkmaline at cc.hut.fi
Wed May 14 21:45:05 EDT 2003


On Thu, May 15, 2003 at 12:14:59AM +0200, Santiago Garcia Mantinan wrote:

> What comes next is what happened on my last test, at first I saw this error:
> 
> wlan0: hfa384x_cmd: interrupted; err=-4
> wlan0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-4, rid=fdc6, len=12)
> wlan0: hfa384x_setup_bap - timeout after

Do you run any monitoring software that is displaying update wireless
interface statistics etc. periodically? RID FDC6 is read only for couple
of read ioctls. Such a program seemed to have started ioctl(), but it
was then interrupted (e.g., by killing the process).

> wlan0: hfa384x_setup_bap - timeout after

Could you please re-test this with BAP busy timeout set to some insanely
large value? To do this, change following line in hostap_hw.c:

#define HFA384X_BAP_BUSY_TIMEOUT 1500

to

#define HFA384X_BAP_BUSY_TIMEOUT 100000

This will make the driver to wait up to a second before reporting
timeout on BAP access.

-- 
Jouni Malinen                                            PGP id EFC895FA



More information about the HostAP mailing list