Problems with: "hfa384x_cmd: cmd_queue full"

Tim Barker tim at tbarker.com
Wed Dec 7 16:23:14 EST 2005


Hi everyone,

I'm hoping to find some help with an issue I've been having. I've been
using the hostap driver in client (managed) mode for backhaul
applications but have had problems with the driver (or wifi card)
freezing after a few hours of use.

The client will not connect to an access point (via ifdown + ifup) and
using 'iwpriv wlan0 reset 1' and 'iwpriv wlan0 reset 0' does not help.

The issue can only be fixed reloading hostap (rmmod + modprobe) or a
reboot. This issue has been replicated on 5 separate (but identical)
systems so far but does not happen often.

Any help with this would be very much appreciated :-)

Thanks,

Tim


Useful lines from /var/log/messages:

Dec  2 06:27:22 localhost kernel: wifi0: LinkStatus=6 (Association failed)
Dec  2 06:27:22 localhost kernel: wifi0: LinkStatus: BSSID=44:44:44:44:44:44
Dec  2 06:27:23 localhost kernel: wifi0: JoinRequest:
BSSID=00:xx:xx:xx:xx:xx channel=6
Dec  2 06:27:24 localhost kernel: wifi0: LinkStatus=6 (Association failed)
Dec  2 06:27:24 localhost kernel: wifi0: LinkStatus: BSSID=44:44:44:44:44:44
Dec  2 06:27:28 localhost kernel: wifi0: hfa384x_cmd: entry still in
list? (entry=c3b564e0, type=0, res=0)
Dec  2 06:27:28 localhost kernel: wifi0: hfa384x_cmd: command was not
completed (res=0, entry=c3b564e0, type=0, cmd=0x0021, param0=0xfd51,
EVSTAT=0000 INTEN=e09f)
Dec  2 06:27:28 localhost kernel: wifi0: hfa384x_get_rid:
CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
Dec  2 06:27:30 localhost kernel: wifi0: hfa384x_cmd: entry still in
list? (entry=c3b564e0, type=0, res=0)
Dec  2 06:27:30 localhost kernel: wifi0: hfa384x_cmd: command was not
completed (res=0, entry=c3b564e0, type=0, cmd=0x0021, param0=0xfd51,
EVSTAT=0000 INTEN=e09f)
Dec  2 06:27:30 localhost kernel: wifi0: hfa384x_get_rid:
CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
Dec  2 06:27:32 localhost kernel: wifi0: hfa384x_cmd: entry still in
list? (entry=c3b564e0, type=0, res=0)
.
.
.
Dec  2 06:30:28 localhost kernel: wifi0: hfa384x_cmd: entry still in
list? (entry=c3b564e0, type=0, res=0)
Dec  2 06:30:28 localhost kernel: wifi0: hfa384x_cmd: command was not
completed (res=0, entry=c3b564e0, type=0, cmd=0x0021, param0=0xfd51,
EVSTAT=0000 INTEN=e09f)
Dec  2 06:30:28 localhost kernel: wifi0: hfa384x_get_rid:
CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
Dec  2 06:30:28 localhost kernel: wifi0: hfa384x_cmd: cmd_queue full
Dec  2 06:30:28 localhost kernel: wifi0: hfa384x_get_rid:
CMDCODE_ACCESS failed (res=-1, rid=fd51, len=6)
Dec  2 06:30:28 localhost kernel: wlan0: hfa384x_cmd: cmd_queue full
Dec  2 06:30:28 localhost kernel: wlan0: hfa384x_get_rid:
CMDCODE_ACCESS failed (res=-1, rid=fdc6, len=12)
Dec  2 06:30:28 localhost kernel: wlan0: hfa384x_cmd: cmd_queue full
Dec  2 06:30:28 localhost kernel: wlan0: hfa384x_get_rid:
CMDCODE_ACCESS failed (res=-1, rid=fdc6, len=12)
Dec  2 06:30:28 localhost kernel: wlan0: hfa384x_cmd: cmd_queue full
.
.
.
Dec  2 06:30:29 localhost kernel: wlan0: hfa384x_get_rid:
CMDCODE_ACCESS failed (res=-1, rid=fdc6, len=12)
Dec  2 06:30:29 localhost kernel: wlan0: hfa384x_setup_bap - timeout after
Dec  2 06:30:29 localhost kernel: wlan0: hfa384x_set_rid (rid=fce5,
len=38) - failed - res=-110
Dec  2 06:30:29 localhost kernel: wlan0: HOSTSCAN failed
Dec  2 06:30:29 localhost kernel: wlan0: hfa384x_cmd: cmd_queue full
Dec  2 06:30:29 localhost kernel: wlan0: hfa384x_get_rid:
CMDCODE_ACCESS failed (res=-1, rid=fdc6, len=12)
Dec  2 06:30:29 localhost kernel: wlan0: hfa384x_setup_bap - timeout before
Dec  2 06:30:29 localhost kernel: wlan0: hfa384x_set_rid (rid=fce5,
len=38) - failed - res=-110
Dec  2 06:30:29 localhost kernel: wlan0: HOSTSCAN failed



Details of system:

hostap_cs: 0.3.7 - 2005-02-12

PCMCIA WiFi card = Hyperlink HA2401GX-325 (PRISM2.5)
NIC: id=0x800c v1.0.0
PRI: id=0x15 v1.0.7
STA: id=0x1f v1.3.6

Hardware = Soekris net4511
Linux Kernel = 2.4.30






Here is the body from an email in the archives which appears to be the
same... but I can't find a reply :-(
 _________________________________________________

 On Wed, Nov 12, 2003 at 10:13:19AM +0900, imp wrote:

  > When I use WEP key, and run hostap for several hours, then the
hostap make bellow error.
 >
 > wifi0: hfa384x_cmd: cmd_queue full

 Can you still use the card after this? Does the driver eventually
  recover? If not, can you fix this by running 'iwpriv wlan0 reset 0' or
  'iwpriv wlan0 reset 1'? Can you get the previous messages just before
 the first "cmd_queue full"?

 And the set of default questions..

 Which Host AP driver version?
 Which kernel version?
 Which hardware platform/CPU?
  Which Prism2/2.5/3 card (model/NICID/firmware versions)?

 --
  Jouni Malinen



More information about the HostAP mailing list