prism 2.5 card resets

[Jar]

Rees wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> I'm running hostap on an ipcop box using the wlanap addon and hostap
> drivers and i seem to be having a problem whereby the card (Senao
> NL-2511CD Ext2) resets under heavyish traffic load or when there are
> more than a couple of clients connected.
> 
> At the moment i'm running,
> NICID: id=0x800c v1.0.0 (PRISM II (2.5) PCMCIA (SST parallel flash))
> PRIID: id=0x0015 v1.1.1
> STAID: id=0x001f v1.7.4 (station firmware)
> 
> but i've also experienced the problem using 1.8.2 firmware as well.
> Dmesg output leading up to the reset is included below.
> The only idea i could come up with is that according to /proc/interrupts
> the card is sharing an irq with my ethernet card and another pci device
> (i'm assuming it's the pcmcia>pci bridge?) Would this be expected to
> cause problems?
> 
> output of /proc/interrupts;
> 5:    1459605          XT-PIC  PCI device 1180:0476, hostap_cs, eth0
> 
> Dmesg output
> wifi0: hfa384x_cmd: entry still in list? (entry=c199dbd0, type=0, res=0)
> wifi0: hfa384x_cmd: command was not completed (res=0, entry=c199dbd0,
> type=0, cmd=0x0002, param0=0x0000, EVSTAT=0000 INTEN=e09f)
> wifi0: reset port failed to disable port
> NETDEV WATCHDOG: wifi0: transmit timed out
> wifi0 Tx timed out! Resetting card
> wifi0: CMD=0002 EVSTAT=0000 OFFSET0=0000 OFFSET1=0000 SWSUPPORT0=8a32
> wifi0: scheduled card reset
> hostap_cs: wifi0: resetting card
> prism2_pccard_cor_sreset: original COR 41
> wifi0: removed pending cmd_queue entry (type=1, cmd=0x010b, param0=0x0134)
> prism2_hw_init: initialized in 190 ms
> wifi0: STA xx:xx:xx:xx:xx:xx TX rate lowered to 55
> wifi0: hfa384x_cmd: entry still in list? (entry=c199dc50, type=0, res=0)
> wifi0: hfa384x_cmd: command was not completed (res=0, entry=c199dc50,
> type=0, cmd=0x0002, param0=0x0000, EVSTAT=0000 INTEN=e09f)
> wifi0: reset port failed to disable port
> wifi0: hfa384x_cmd: entry still in list? (entry=c199dd10, type=0, res=0)
> wifi0: hfa384x_cmd: command was not completed (res=0, entry=c199dd10,
> type=0, cmd=0x0021, param0=0xfc28, EVSTAT=0000 INTEN=e09f)
> wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fc28, len=2)
> Could not read current WEP flags.
> wifi0: encryption setup failed
> NETDEV WATCHDOG: wifi0: transmit timed out
> wifi0 Tx timed out! Resetting card
> wifi0: CMD=0002 EVSTAT=0000 OFFSET0=0000 OFFSET1=0000 SWSUPPORT0=8a32
> wifi0: scheduled card reset
> hostap_cs: wifi0: resetting card
> prism2_pccard_cor_sreset: original COR 41
> wifi0: removed pending cmd_queue entry (type=1, cmd=0x0011, param0=0xf100)
> wifi0: removed pending cmd_queue entry (type=1, cmd=0x010b, param0=0x015e)
> prism2_hw_init: initialized in 190 ms

My card is:

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.7.4 (station firmware)

And I am getting these randomly even if there is no stations associated. 
Either something is changed in hostap-driver between kernels 
2.6.17...2.6.25 or is my card dying?

wifi0: hfa384x_cmd: entry still in list? (entry=d6c97c40, type=0, res=0)
wifi0: hfa384x_cmd: command was not completed (res=0, entry=d6c97c40, 
type=0, cmd=0x0002, param0=0x0000, EVSTAT=0000 INTEN=e09f)
wifi0: reset port failed to disable port
wifi0: hfa384x_cmd: entry still in list? (entry=d6c97700, type=0, res=0)
wifi0: hfa384x_cmd: command was not completed (res=0, entry=d6c97700, 
type=0, cmd=0x0021, param0=0xfc28, EVSTAT=0000 INTEN=e09f)
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fc28, len=2)
Could not read current WEP flags.
wifi0: encryption setup failed
wifi0: hfa384x_cmd_issue: cmd reg was busy for 3 usec
wifi0: hfa384x_cmd_issue: cmd reg was busy for 3 usec
wifi0: hfa384x_cmd_issue: cmd reg was busy for 4 usec
wifi0: hfa384x_cmd_issue: cmd reg was busy for 4 usec
wifi0: hfa384x_cmd_issue: cmd reg was busy for 4 usec
wifi0: Command completion event, but no pending commands


-- 
Best Regards, Jar