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

Opened 13 years ago

Strange freeze when moving laptop and/or lots of ESSID/BSSIDs in list

Reported by: thomas@mich.com Assigned to:
Priority: minor Milestone:
Component: madwifi: other Version: trunk
Keywords: Cc:
Patch is attached: 0 Pending: 0

Description

Version is the current snapshot which untars to madwifi-hal-0.10.5.6-r3835-20080801, on the current Ubuntu kernels "2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 GNU/Linux" and the 32 bit equivalent (I dual boot and share /home). I recompiled to verify.

Two days in a row, everything works fine at the hotel in the morning where I'm surfing, then without shutting the laptop off (nor suspending it) I drive to work a short distance away (passing several APs which I see recorded). At work there are over 20 different ad-hoc/APs (we're developing a wireless device). When I get to work, it freezes. I can enter an ESSID, but it won't show the AP's BSSID or associate with it. iwlist scan returns an error about not being able to allocate something for printing the list to screen (it isn't happening as I write this and I didn't copy it down but will if it happens again). I boot into Vista and/or XP and it works perfectly, but not when I go back to either (32 or 64 bit) linux. Eventually "wlanconfig ath0 destroy", then "..create..." will return the interface to normal, but usually in the afternoon. I've shut off power and waited and recompiled and reinstalled the drivers but that doesn't help.

It may simply be overflowing or finding something it can't handle when it tries the iwlist scan (or implicit or association scans).

I suspect it has to do with my drive in to work (which will go by 8-10 open APs), then at work the excessive number of ESSIDs and unique cells. There may also be duplicates (ad-hoc OR managed, same ESSID, different channel), or other wireless weird things going on.

Nothing appears in dmesg output. It usually will do iwlist scan correctly UNTIL I try an iwconfig to my access point. Then I get the problem and it won't associate.

This is what dmesg says when loading the modules:

[ 36.156354] ath_hal: module license 'Proprietary' taints kernel. [ 36.158226] AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) [ 36.390778] ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 18 [ 36.390896] PCI: Setting latency timer of device 0000:05:00.0 to 64 [ 36.884515] MadWifi: ath_attach: Switching rfkill capability off. [ 36.944611] wifi0: Atheros AR2425 chip found (MAC 14.2, PHY SChip 7.0, Radio 10.2) [ 36.964635] ath_pci: wifi0: Atheros 5424/2424: mem=0xf8000000, irq=18

Is there anything I can easily enable to get copious amounts of debug data to help further? Since it happened twice I expect it will happen again. It may not be in the madwifi component specifically, but that is where I see the problem.

I also have an old zd1211rw adapter which works fine in the environment.