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

Opened 14 years ago

Last modified 13 years ago

"Unhandled kernel unaligned access" on 4G cube (MTX-1/AU1500) with custom 2.6 kernel

Reported by: olivier.mehani@inria.fr Assigned to:
Priority: major Milestone:
Component: madwifi: driver Version: v0.9.3.3
Keywords: ar5213A 4gcube mips wlanconfig panic Cc:
Patch is attached: 0 Pending:

Description

Hi,

Using release version 0.9.3.3 of Madwifi, with an AR5213A-based MiniPCI card, I experience the following on a 4G Cube with a custom (OpenWRT + NEMO patchsets) 2.6.21.3 kernel.

Unhandled kernel unaligned access[#1]:
Cpu 0
$ 0   : 00000000 1000fc01 00000000 cccccccd
$ 4   : 00004801 00000050 0000001a 00000324
$ 8   : 00000050 0000003c 000009e4 00002790
$12   : 00002790 fff00000 00000001 00000001
$16   : 811f8320 83be7000 810c28c0 80c26020
$20   : 00000000 00000006 8118a000 801259bc
$24   : 00000001 2ac06180                  
$28   : 830bc000 830bdde0 000000ff c020e0f8
Hi    : 00006744
Lo    : cccce69e
epc   : c015af60 ieee80211_input+0xac/0x1350 [wlan]     Tainted: P      
ra    : c020e0f8 ath_rx_tasklet+0x3cc/0x900 [ath_pci]
Status: 1000fc03    KERNEL EXL IE 
Cause : 00800010
BadVA : 00000052
PrId  : 01030202
Modules linked in: vfat fat nls_base wlan_scan_sta ath_rate_sample ath_pci wlan)
Process ipkg-cl (pid: 8217, threadinfo=830bc000, task=817863f8)
Stack : 8118a320 c02133f4 81263000 00000000 00000001 7fffc559 c016f4c8 8019a420
        803fa11c 803fa134 00000608 80273300 835b9540 c0170594 8118a320 81283510
        a3a9d510 83be7000 810c28c0 83b08000 8118a000 801259bc 00000000 c020e0f8
        01fe0353 00000000 0000001a 00000324 00000007 00000000 8118a000 8118a320
        00000000 fffffffe 00000001 803f592c 0000000a 1044c060 ffffffff 00000000
        ...
Call Trace:
[<c015af60>] ieee80211_input+0xac/0x1350 [wlan]
[<c020e0f8>] ath_rx_tasklet+0x3cc/0x900 [ath_pci]
[<8012c8e4>] tasklet_action+0xb0/0x180
[<8012c4c4>] __do_softirq+0x110/0x118
[<8012c558>] do_softirq+0x8c/0x94
[<8012c5c0>] irq_exit+0x4c/0x54
[<8010182c>] intc0_req0_irqdispatch+0x80/0xf8
[<80101b48>] plat_irq_dispatch+0x8c/0xa4
[<80103240>] ret_from_irq+0x0/0x4

Previously during the boot process (when the device is brought up using wlanconfig ath0 create wlandev wifi0 wlanmode adhoc),these other messages were displayed:

Error for wireless request "Set ESSID" (8B1A) :
    SET failed on device wlan0 ; No such device.
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan0 ; No such device.
SIOCSIFADDR: No such device
SIOCSIFNETMASK: No such device
SIOCGIFFLAGS: No such device
ath0      no private ioctls.

Change History

11/09/07 18:11:16 changed by Olivier Mehani <olivier.mehani@inria.fr>

Additionally, the device seems to "flicker": only running iwconfig at a few seconds interval, not doing anything else, the ath device disappear and reappears, or is stated not to have any wireless extension:

Below is the output of 4 iwconfig commands run with a (manual) period of a few seconds.

Not here at all:

root@mtx-130:~# iwconfig 
lo        no wireless extensions.

eth0      no wireless extensions.

ip6tnl0   no wireless extensions.

wifi0     no wireless extensions.

Present:

root@mtx-130:~# iwconfig 
lo        no wireless extensions.

eth0      no wireless extensions.

ip6tnl0   no wireless extensions.

wifi0     no wireless extensions.

Warning: Driver for device ath0 has been compiled with version 22
of Wireless Extension, while this program supports up to version 20.
Some things may be broken...

ath0      IEEE 802.11g  ESSID:""  Nickname:""
          Mode:Ad-Hoc  Channel:0  Cell: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power:19 dBm   Sensitivity=1/1  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/70  Signal level=-100 dBm  Noise level=-100 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Gone again:

root@mtx-130:~# iwconfig 
lo        no wireless extensions.

eth0      no wireless extensions.

ip6tnl0   no wireless extensions.

wifi0     no wireless extensions.

ath0      No such device

And back:

root@mtx-130:~# iwconfig 
lo        no wireless extensions.

eth0      no wireless extensions.

ip6tnl0   no wireless extensions.

wifi0     no wireless extensions.

Warning: Driver for device ath0 has been compiled with version 22
of Wireless Extension, while this program supports up to version 20.
Some things may be broken...

ath0      IEEE 802.11b  ESSID:"cube-mesh"  Nickname:""
          Mode:Ad-Hoc  Frequency:2.422 GHz  Cell: 02:02:6F:2F:04:F2   
          Bit Rate:0 kb/s   Tx-Power:19 dBm   Sensitivity=1/1  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=21/70  Signal level=-77 dBm  Noise level=-98 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

11/13/07 01:13:30 changed by mentor

  • priority changed from blocker to major.

(follow-up: ↓ 4 ) 11/13/07 01:22:32 changed by mentor

As the first thing, have you tried using trunk?

(in reply to: ↑ 3 ) 11/13/07 09:28:41 changed by Olivier Mehani <olivier.mehani@inria.fr>

Replying to mentor:

As the first thing, have you tried using trunk?

Yes, I both tried 0.9.3.3 and trunk as of rev. 2834.

The same behavior was observed.

02/23/08 23:17:05 changed by SanTiago

I got similar problems with madwifi 0.9.3.3 on ADM 5120 SoC compiled by GCC 4.1.2 . When i switched to GCC 3.4.6, the problem disappeared. Kernel and GCCs were from openwrt.

05/29/08 03:58:41 changed by Olivier Mehani <olivier.mehani@inria.fr>

Both the kernel and the MadWifi drivers were compiled with GCC 3.3.4 in this case.

09/10/08 09:50:06 changed by Olivier Mehani <olivier.mehani@inria.fr>

The flickering issue is still present with 0.9.4 and -hal-2008-08-15 as of rev source:#3862.