Transmit timed out problem and some others...

[Martin Lexa]

Greetings,

  I'm trying to debug and resolve strange problem which is occurring about
10x per a day, but sometimes more than it. Here is the log of problematic
part:

    Mar 17 20:30:18 router wlan0 unsupported ioctl(0x89f0)
    Mar 17 20:34:51 router NETDEV WATCHDOG: wlan0: transmit timed out
    Mar 17 20:34:51 router wlan0 Tx timed out! Resetting card
    Mar 17 20:34:51 router wlan0: CMD=010b EVSTAT=0000 OFFSET0=0000
    OFFSET1=0000 SWSUPPORT0=8a32
    Mar 17 20:34:51 router wlan0: scheduled card reset
    Mar 17 20:34:51 router hostap_pci: wlan0: resetting card
    Mar 17 20:34:52 router prism2_hw_init: initialized in 190 ms
    
  I spent almost two weeks about resolving it. No success. I tried various
hostap versions (0.1.2, 0.1.3, CVS),... Various f/ws, currently card has:

  NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
  PRIID: id=0x0015 v1.1.1
  STAID: id=0x001f v1.8.0 (station firmware)

  Card runs in master mode and about 6 clients (Win, Linux) connect to it.

  Current kernel: 2.4.25, hostap version: 0.1.3, card is: Z-COM XI-626 PCI.
  (note: Computer has 2 Z-COM 626 cards.)

  Another thing is that sometimes card deauthenticate almost all
clients. When doing this connection became very unstable (no ping). Just
everything is blocked when doing this! Could it be some kind of spinlock
problem?
  My idea: In the first scenario card goes to reset because of the
time out and in second the deauthentication/association didn't last to long,
so no timeout => no reset.
  Here is the log (only interesting parts):

    Mar 17 20:49:32 router wlan0: 00:0c:6e:ac:a8:3b auth_cb - STA
    authenticated
    Mar 17 20:49:32 router wlan0: 00:0c:6e:ac:a8:3b assoc_cb - STA
    associated
    Mar 17 20:49:32 router wlan0: deauthentication: 00:60:b3:6e:21:20
    len=2, reason_code=3
    Mar 17 20:49:32 router wlan0: 00:60:b3:6e:19:79 auth_cb - STA
    authenticated
    Mar 17 20:49:32 router wlan0: deauthentication: 00:60:b3:6e:21:20
    len=2, reason_code=3
    Mar 17 20:49:32 router wlan0: deauthentication: 00:60:b3:6e:21:20
    len=2, reason_code=3
    Mar 17 20:49:32 router wlan0: deauthentication: 00:60:b3:6e:21:20
    len=2, reason_code=3
    Mar 17 20:49:32 router wlan0: deauthentication: 00:60:b3:6e:19:79
    len=2, reason_code=3
    Mar 17 20:49:32 router wlan0: deauthentication: 00:60:b3:6e:19:79
    len=2, reason_code=3
    ...
    ...
    ...
    Mar 17 20:49:45 router wlan0: dropped received packet from
    non-associated STA 00:60:b3:6e:21:20 (type=0x02, subtype=0x00)
    Mar 17 20:49:45 router handle_ap_item - data frame
    Mar 17 20:49:45 router wlan0: dropped received packet from
    non-associated STA 00:60:b3:6e:21:20 (type=0x02, subtype=0x00)
    ...
    ...
    ...
    Mar 17 20:49:51 router wlan0: deauthentication: 00:60:b3:6e:19:79
    len=2, reason_code=3
    Mar 17 20:49:51 router wlan0: deauthentication: 00:60:b3:6e:21:20
    len=2, reason_code=3
    Mar 17 20:49:52 router wlan0: deauthentication: 00:60:b3:6e:1f:2f
    len=2, reason_code=3
    Mar 17 20:49:53 router wlan0: deauthentication: 00:60:b3:6e:21:20
    len=2, reason_code=3
    Mar 17 20:49:53 router wlan0: deauthentication: 00:60:b3:6e:21:20
    len=2, reason_code=3
    Mar 17 20:49:53 router wlan0: deauthentication: 00:60:b3:6e:19:79
    len=2, reason_code=3
    Mar 17 20:49:53 router wlan0: deauthentication: 00:60:b3:6e:21:20
    len=2, reason_code=3
    Mar 17 20:49:53 router wlan0: deauthentication: 00:60:b3:6e:1f:2f
    len=2, reason_code=3
    Mar 17 20:49:53 router wlan0: deauthentication: 00:60:b3:6e:1f:2f
    len=2, reason_code=3
    Mar 17 20:49:53 router wlan0: deauthentication: 00:60:b3:6e:1f:2f
    len=2, reason_code=3
    Mar 17 20:49:53 router wlan0: deauthentication: 00:60:b3:6e:1f:2f
    len=2, reason_code=3
    Mar 17 20:49:53 router wlan0: deauthentication: 00:60:b3:6e:1f:2f
    len=2, reason_code=3
    ...
    ...
    ...
    Mar 17 20:50:04 router handle_ap_item -
    addr3(BSSID)=57:2d:39:e8:d7:ab not own MAC
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    What's going on here?

  And CVS development version (0.2 branch) has some problems with
managed mode.
Symptoms are: 
    1) One card in master mode (works ok), another one in managed mode
    (problematic).
    2) The card in managed mode connects to host (which runs hostap driver
    0.1.2, Z-COM XI-626 PCI, f/w: STA: 1.3.6), in logs there is word connected.
    Signal is around 62/90. However no ping to host ip. Don't know why.
    3) Booting with the same kernel only hostap drivers 0.1.3 => everything
    ok. Of course, with problems which I described above.

  Note: I tried CVS development version on another computer, which have only one
Z-Com card and it works ok.

Every help is greatly appreciated. I've some time to spend on debugging and
may be coding if necessary.

Thanks,
Martin.