RE: Multicast a 1.5Mbit stream from AP generate a lot of INFDROP event


From: Sunny Lai (ktlai_at_ie.cuhk.edu.hk)
Date: 2002-08-29 04:05:26 UTC



>
> > I try the lastest CVS, but it don't solve the INFDROP. and some
> how the card
> > hang up, I need to reboot..
>
> There was at least one bug that caused deadlocks with the version you
> used. If the current CVS version with the set_rid fix crashes the host
> computer, I would like to get some more information about this since I
> would like to fix these crashes before releasing the next driver
> version.

I do the test again and find the following log when INFDROP, (it happen after I stream the 1.5mb video about 2min)

hostap_plx: hostap_plx.c 0.0.0 CVS (SSH Communications Security Corp, Jouni Mali
nen)
hostap_plx: (c) SSH Communications Security Corp <jkm_at_ssh.com>

PCI: Found IRQ 10 for device 02:08.0
PCI: Sharing IRQ 10 with 00:1f.3
PCI: Sharing IRQ 10 with 00:1f.5

PLX9052 PCI/PCMCIA adapter: mem=0xff6ffc00, plx_io=0xdc80, irq=10, pccard_io=0xd
c00
hostap_plx: CIS: 01 03 00 00 ff 17 ...
hostap_plx: manfid=0x0274, 0x1613
hostap_plx: cor_index=0x1 cor_offset=0x3e0
Prism2/2.5 PC Card detected in PLX9052 adapter PLX_INTCSR=0x1063
PLX_CNTRL=0x187866d2 (Serial EEPROM present=1)
hostap_plx: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_config: initialized in 16765 iterations
wlan0: NIC: id=0x801b v1.0.0
wlan0: PRI: id=0x15 v1.0.7

wlan0: STA: id=0x1f v1.3.5
wlan0: LinkStatus=2 (Disconnected)
device eth1 entered promiscuous mode
device wlan0 entered promiscuous mode
eth1: Setting promiscuous mode.
eth1: Setting promiscuous mode.
eth1: Setting promiscuous mode.
eth1: Setting promiscuous mode.

wlan0: prism2_open
br0: port 2(wlan0) entering listening state
br0: port 1(eth1) entering listening state
br0: port 2(wlan0) entering learning state
br0: port 1(eth1) entering learning state
br0: port 2(wlan0) entering forwarding state
br0: topology change detected, propagating
br0: port 1(eth1) entering forwarding state
br0: topology change detected, propagating
wlan0: authentication: 00:02:2d:28:be:7f len=6, auth_alg=0, auth_transaction=1,
status_code=0, fc=0x00b0
wlan0: new STA 00:02:2d:28:be:7f
wlan0: association request: from 00:02:2d:28:be:7f to 00:06:25:ab:26:df len=25
  capability=0x0001, listen_interval=1 - new AID 1 wlan0: authentication: 00:02:2d:28:be:9d len=6, auth_alg=0, auth_transaction=1,
status_code=0, fc=0x00b0
wlan0: new STA 00:02:2d:28:be:9d
wlan0: association request: from 00:02:2d:28:be:9d to 00:06:25:ab:26:df len=25
  capability=0x0001, listen_interval=1 - new AID 2 wlan0: TXEXC - fid=0x0269 - status=0x0001 ([RetryErr]) tx_control=000c

   retry_count=0 tx_rate=110 fc=0x0a08 (Data::0 FromDS)    A1=00:02:2d:28:be:9d A2=00:06:25:ab:26:df A3=00:b0:d0:9c:ae:0c A4=00:00:00:00
:00:00

wlan0: STA 00:02:2d:28:be:9d TX rate lowered to 55
wlan0: STA 00:02:2d:28:be:9d TX rate raised to 110
wlan0: TXEXC - fid=0x030c - status=0x0001 ([RetryErr]) tx_control=000c

   retry_count=0 tx_rate=110 fc=0x0a08 (Data::0 FromDS)    A1=00:02:2d:28:be:7f A2=00:06:25:ab:26:df A3=00:06:25:ab:26:df A4=00:00:00:00
:00:00
wlan0: STA 00:02:2d:28:be:7f TX rate lowered to 55 wlan0: sending disassociation info to STA 00:02:2d:28:be:7f(last=7843797, jiffie
s=7873897)
wlan0: TXEXC - fid=0x03a3 - status=0x0001 ([RetryErr]) tx_control=000c

   retry_count=0 tx_rate=0 fc=0x08a0 (Mgmt::10)    A1=00:02:2d:28:be:7f A2=00:06:25:ab:26:df A3=00:06:25:ab:26:df A4=00:00:00:00
:00:00
wlan0: STA 00:02:2d:28:be:7f TX rate lowered to 20 wlan0: TXEXC - fid=0x0371 - status=0x0001 ([RetryErr]) tx_control=000c

   retry_count=0 tx_rate=110 fc=0x0a08 (Data::0 FromDS)    A1=00:02:2d:28:be:9d A2=00:06:25:ab:26:df A3=00:b0:d0:9c:ae:0c A4=00:00:00:00
:00:00
wlan0: STA 00:02:2d:28:be:9d TX rate lowered to 55 wlan0: sending deauthentication info to STA 00:02:2d:28:be:7f(last=7843797, jiff
ies=7873997)
wlan0: TXEXC - fid=0x0153 - status=0x0001 ([RetryErr]) tx_control=000c

   retry_count=0 tx_rate=0 fc=0x08c0 (Mgmt::12)    A1=00:02:2d:28:be:7f A2=00:06:25:ab:26:df A3=00:06:25:ab:26:df A4=00:00:00:00
:00:00

wlan0: Could not find STA for this TX error
wlan0: INFDROP event
wlan0: INFDROP event
wlan0: INFDROP event
wlan0: INFDROP event
wlan0: INFDROP event
wlan0: INFDROP event
wlan0: INFDROP event
wlan0: INFDROP event...


I find one time the driver start normally, but in the Beacon frame, the SSID is "non", not the one I set in the file. The log is a follows.

hostap_plx: hostap_plx.c 0.0.0 CVS (SSH Communications Security Corp, Jouni Mali
nen)
hostap_plx: (c) SSH Communications Security Corp <jkm_at_ssh.com>

PCI: Found IRQ 10 for device 02:08.0
PCI: Sharing IRQ 10 with 00:1f.3
PCI: Sharing IRQ 10 with 00:1f.5

PLX9052 PCI/PCMCIA adapter: mem=0xff6ffc00, plx_io=0xdc80, irq=10, pccard_io=0xd
c00
hostap_plx: CIS: 01 03 00 00 ff 17 ...
hostap_plx: manfid=0x0274, 0x1613
hostap_plx: cor_index=0x1 cor_offset=0x3e0
Prism2/2.5 PC Card detected in PLX9052 adapter PLX_INTCSR=0x1063
PLX_CNTRL=0x187866d2 (Serial EEPROM present=1)
hostap_plx: Registered netdevice wlan0
prism2_hw_init()
prism2_hw_config: initialized in 16757 iterations
wlan0: NIC: id=0x801b v1.0.0
wlan0: hfa384x_get_rid_copy - RID len mismatch: rid=0xfd02, len=-2 (expected 8)
Could not get RID for component PRI
wlan0: hfa384x_get_rid_copy - RID len mismatch: rid=0xfd20, len=2 (expected 8)
Could not get RID for component STA
wlan0: hfa384x_get_rid_copy - RID len mismatch: rid=0xfc09, len=4 (expected 2)
wlan0: LinkStatus=2 (Disconnected)
device eth1 entered promiscuous mode
device wlan0 entered promiscuous mode
eth1: Setting promiscuous mode.
eth1: Setting promiscuous mode.
eth1: Setting promiscuous mode.
eth1: Setting promiscuous mode.

wlan0: prism2_open
br0: port 2(wlan0) entering listening state
br0: port 1(eth1) entering listening state
br0: port 2(wlan0) entering learning state
br0: port 1(eth1) entering learning state
br0: port 2(wlan0) entering forwarding state
br0: topology change detected, propagating
br0: port 1(eth1) entering forwarding state
br0: topology change detected, propagating





>
> > Do you mean, the driver pass all packet no matter multicast or
> unicast to
> > the firmware, then the firmware descide when to send?? Is there
> any material
> > on the web, so I can know more on the programming of this chip or card??
>
> The driver passes all multicast/broadcast frames to the firmware and it
> is up to the firmware to decide when to really send these. However,
> unicast frames are buffered in the host driver if the station is using
> power saving.
>
> Driver programmer's manual is available from Intersil, but it is
> distributed only under NDA.

I am getting the manual, hope i can do something to stop the internal buffering of the mulitcast/broadcast by the CNFMULTICASTPMBUFFRING field. Thanks.

Regards,
Sunny



This archive was generated by hypermail 2.1.4.