On Nov 21, 2007 8:03 PM, Luis R. Rodriguez [off-list ref] wrote:

On Jun 3, 2007 5:33 PM, Jan Willies [off-list ref] wrote:

quoted

Jean-Baptiste Note schrieb:

quoted

Hi,

Any chance you could decode the oops ? If you're recompiling the
kernel yourself, include symbols (can't remember the option name), or
run ksymoops...

I recompiled the kernel with KALLSYMS and got this:

root@OpenWrt:/# iwconfig
lo        no wireless extensions.

ethData bus error, epc == c007e16c, ra == c007d6c0
Oops[#1]:
Cpu 0
$ 0   : 00000000 1000b800 abad0000 00000032
$ 4   : 00000001 c0068000 00000013 00000001
$ 8   : 00000004 800feb8c 00000000 00000000
$12   : 00000000 00000000 8124ca40 00000000
$16   : 812a7800 000000fa 81361320 81361000
$20   : 00000010 00000000 a1cc0000 00000019
$24   : 00000000 2abd45f0
$28   : 813d6000 813d7ce8 ff02000d c007d6c0
Hi    : 000002fc
Lo    : 00035866
epc   : c007e16c isl38xx_trigger_device+0xc/0x60 [prism54]     Not tainted
ra    : c007d6c0 islpci_mgt_transaction+0x380/0x614 [prism54]
Status: 1000b803    KERNEL EXL IE
Cause : 0000001c
PrId  : 00029007
Modules linked in: prism54 switch_robo switch_core diag
Process iwconfig (pid: 1411, threadinfo=813d6000, task=8106f3f8)
Stack : 81108800 8001e418 00000060 00000000 00000000 8106f3f8 8003bf54
813616b0
         813616b0 80029ab0 00000004 00000000 00000000 80200ddc 0000008a
ff02000d
         81361320 813d7d98 81361000 c0086cd0 1000b800 00000000 1000b800
8002964c
         00000004 813d7d50 00000000 81271d04 813d7e70 813d7e70 813d7e60
80200ddc
         7fcad438 7fcad478 813d7e60 00008b01 c0081628 00000101 00000001
00000000
         ...
Call Trace:
[<c007e16c>] isl38xx_trigger_device+0xc/0x60 [prism54]
[<c007d6c0>] islpci_mgt_transaction+0x380/0x614 [prism54]
[<c0086cd0>] mgt_get_request+0x100/0x2ec [prism54]
[<c0081628>] prism54_set_mac_address+0x1a0/0xfd8 [prism54]

Sorry for the late reply ;) but anyway, I tried looking into this
finally (with new found knowledge on this subject, thanks to Kyle) and
I cannot see a place where isl38xx_trigger_device() would trigger
unaligned access.

Is this issue still present? If so I'd like to get to the bottom of
it. FYI p54 is there as a replacement but as you may know certain
features (ad-hoc, ap support, encryption) are still not present in
that driver.

Actually I've been informed this is not unaligned access problem but
instead it occurs on do_be() or ip22_be_interrupt() on MIPS. I'll have
to check how that works, I do not yet understand how this is reached.

  Luis