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 #1281 (new defect)

Opened 15 years ago

Last modified 15 years ago

ath_pci (0.9.3) on mips-be platform unable to transmit beacons (or any packet maybe)

Reported by: adq_dvb@lidskialf.net Assigned to:
Priority: major Milestone:
Component: madwifi: driver Version: v0.9.3
Keywords: Cc:
Patch is attached: 0 Pending:

Description (Last modified by mentor)

Hi - please see ticket #927 for full details of my system (NOTE: the issue in that ticket is now gone with 0.9.3; this is a different issue).

dmesg output from madwifi drivers on load:

<6>wlan: 0.8.4.2 (0.9.3)
<6>wlan: mac acl policy registered
<6>ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413, REGOPS_FUNC)
<6>ath_rate_sample: 1.2 (0.9.3)
<6>ath_pci: 0.9.4.5 (0.9.3)
<6>ath_pci: switching rfkill capability off
<4>wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
<4>wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
<4>wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
<4>wifi0: H/W encryption support: WEP AES AES_CCM TKIP
<4>wifi0: mac 7.9 phy 4.5 radio 5.6
<4>wifi0: Use hw queue 1 for WME_AC_BE traffic
<4>wifi0: Use hw queue 0 for WME_AC_BK traffic
<4>wifi0: Use hw queue 2 for WME_AC_VI traffic
<4>wifi0: Use hw queue 3 for WME_AC_VO traffic
<4>wifi0: Use hw queue 8 for CAB traffic
<4>wifi0: Use hw queue 9 for beacons
<6>wifi0: Atheros 5212: mem=0x8000000, irq=32

I've set my system up as an AP, using hostap 0.5.7. However, I don't see the network on any client. I started playing about with the debug options, and enabled the "beacon_proc" athdebug flag. I see the following continually:

<4>ath_beacon_setup: m 80568180 len 149
<4>ath_beacon_send: missed 1 consecutive beacons
<4>ath_beacon_send: resume beacon xmit after 1 misses
<4>ath_beacon_send: slot 2 [tsf 227194349 tsftu 221869 intval 100] vap 00000000
<4>ath_beacon_send: slot 3 [tsf 227215393 tsftu 221890 intval 100] vap 00000000
<4>ath_beacon_send: slot 0 [tsf 227240993 tsftu 221915 intval 100] vap 80407220

The device *IS* able to receive packets though; I enabled "athdebug recv" and I can see packets from other people around me. I checked /proc/interrupts, and its definitely increasing.

I never see any packets being transmitted using the "athdebug xmit" option.

Any idea what would cause this and how I can help track it? Its like the TX ring is never being emptied or something....

Change History

04/24/07 23:58:16 changed by mentor

  • description changed.