#1634: "Unhandled kernel unaligned access" on 4G cube (MTX-1/AU1500) with custom
2.6 kernel
---------------------------------------------------+------------------------
 Reporter:  [EMAIL PROTECTED]                |             Type:  defect  
   Status:  new                                    |         Priority:  blocker 
Component:  madwifi: driver                        |          Version:  v0.9.3.3
 Keywords:  ar5213A  4gcube mips wlanconfig panic  |   Patch_attached:  0       
---------------------------------------------------+------------------------
 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.
 }}}

-- 
Ticket URL: <http://madwifi.org/ticket/1634>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to