Strange behavior of the driver and trasmit timed out errors


From: Carlo Pires (carlo_at_uganet.com.br)
Date: 2002-06-10 19:58:17 UTC



Hello,

I'm testing hostap driver with a LG 11Mbps Wireless LAN PCI Card and, after compiles and install the driver, everything seems to work well, the driver recognizes the card as:
cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x3c0-0x3df 0x4d0-0x4d7

cs: IO port probe 0x0380-0x03bf: clean.
cs: IO port probe 0x03e0-0x04cf: clean.
cs: IO port probe 0x04d8-0x04ff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
hostap_cs: index 0x01: Vcc 3.3, irq 5, io 0x0100-0x013f
hostap_cs: Registered netdevice wlan0

prism2_hw_init()
prism2_hw_config: initialized in 9682 iterations
wlan0: NIC: id=0x8003 v1.0.0
wlan0: PRI: id=0x15 v0.3.0
wlan0: STA: id=0x1f v0.8.3
wlan0: prism2_open

Then, I set a 172.16.1.4 for wlan0 and try to ping 172.16.1.1, (that not exists) and I get in /var/log/messages:

Jun 10 16:37:02 carlo kernel: NETDEV WATCHDOG: wlan0: transmit timed out
Jun 10 16:37:02 carlo kernel: hostap_cs: wlan0 Tx timed out! Resetting card
Jun 10 16:37:02 carlo kernel: hostap_cs: wlan0: resetting card
Jun 10 16:37:06 carlo kernel: NETDEV WATCHDOG: wlan0: transmit timed out
Jun 10 16:37:06 carlo kernel: hostap_cs: wlan0 Tx timed out! Resetting card
Jun 10 16:37:06 carlo kernel: hostap_cs: wlan0: resetting card
Jun 10 16:37:10 carlo kernel: NETDEV WATCHDOG: wlan0: transmit timed out
Jun 10 16:37:10 carlo kernel: hostap_cs: wlan0 Tx timed out! Resetting card
Jun 10 16:37:10 carlo kernel: hostap_cs: wlan0: resetting card

In dmesg:
cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x3c0-0x3df 0x4d0-0x4d7

cs: IO port probe 0x0380-0x03bf: clean.
cs: IO port probe 0x03e0-0x04cf: clean.
cs: IO port probe 0x04d8-0x04ff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
hostap_cs: index 0x01: Vcc 3.3, irq 5, io 0x0100-0x013f
hostap_cs: Registered netdevice wlan0

prism2_hw_init()
prism2_hw_config: initialized in 9682 iterations
wlan0: NIC: id=0x8003 v1.0.0
wlan0: PRI: id=0x15 v0.3.0
wlan0: STA: id=0x1f v0.8.3
wlan0: prism2_open

NETDEV WATCHDOG: wlan0: transmit timed out hostap_cs: wlan0 Tx timed out! Resetting card wlan0: CMD=010b EVSTAT=8011 OFFSET0=0000 OFFSET1=0000 SWSUPPORT0=8a32
hostap_cs: wlan0: resetting card
prism2_pccard_cor_sreset: original COR 41
prism2_hw_init()
prism2_hw_config: initialized in 9783 iterations
prism2_tx_timeout: wake up queue

NETDEV WATCHDOG: wlan0: transmit timed out hostap_cs: wlan0 Tx timed out! Resetting card wlan0: CMD=010b EVSTAT=8019 OFFSET0=0000 OFFSET1=0000 SWSUPPORT0=8a32
hostap_cs: wlan0: resetting card
prism2_pccard_cor_sreset: original COR 41
prism2_hw_init()
prism2_hw_config: initialized in 9783 iterations
prism2_tx_timeout: wake up queue

Although the 172.16.1.1 does not exist, is this behavior normal?

-- 
Carlo Pires
Usu�rio Linux n�mero 277089
----------------------------


This archive was generated by hypermail 2.1.4.