Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #2404 (new defect)

Opened 12 years ago

Last modified 12 years ago

Unexpected sensitivity drops

Reported by: JaFojtik@seznam.cz Assigned to:
Priority: minor Milestone:
Component: madwifi: other Version: v0.9.4
Keywords: sensitivity Cc:
Patch is attached: 0 Pending: 0

Description

The device after several days of working irreversibly drops its sensitivity. After reloading madwifi, sensitivity returns to previous state. So it is purely problem of MadWifi.

I will attach a chart that demonstrates this issue. Purple line shows signal strength measurements. Drops occured at random time, but returning to original sensitivity occurs after MadWiFi restarting.

This problem occurs in MadWiFi-0.9.4, I cannot test Madwifi-ng, because it stops working


This is found in my logs: wifi1: rx FIFO overrun; resetting wifi1: ath_reset: unable to reset hardware: (HAL status 0)

Is it normal to reset wifi1 interface so frequently?

I am using: madwifi-0.9.4-r4119-20100201

It is also interesting that wifi0 does not need reset.

wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: ath_reset: unable to reset hardware: '' (HAL status 0)
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting
wifi1: rx FIFO overrun; resetting

Attachments

rodga-month_big.png (32.8 kB) - added by JaFojtik@seznam.cz on 04/23/10 09:05:58.
Bidirectional measurement signal strength chart

Change History

04/23/10 09:05:58 changed by JaFojtik@seznam.cz

  • attachment rodga-month_big.png added.

Bidirectional measurement signal strength chart

05/15/10 23:27:15 changed by JaFojtik@seznam.cz

I have tested ATH5k on a same device.

It is interesting that ATH5k reports same sensitivity like MadWifi after this defect triggers.

So I suspect that the problem is in XR (eXtended Range) or ANI (Advanced Noise Imunity) MadWifi implementation. This support simply crashes after several days.