On Fri, 2008-10-17 at 21:49 +0100, Peter Denison wrote:
> 
> Try -a r4000 instead.

ksymoops 2.4.11 on i686 2.6.27-6-generic.  Options used
     -v ../openwrt-11527/build_dir/linux-brcm47xx/linux-2.6.25.7/vmlinux 
(specified)
     -K (specified)
     -l /proc/modules (default)
     -o /lib/modules/2.6.27-6-generic/ (default)
     -m ../openwrt-11527/build_dir/linux-brcm47xx/linux-2.6.25.7/System.map 
(specified)
     -a r4000

No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Data bus error, epc == 8011635c, ra == 8015dfe4
Cpu 0
$ 0   : 00000000 1000d800 81c52454 8015ddd4
$ 4   : c00003f8 81c52454 00000001 00000000
$ 8   : 80257f40 80250000 802a0000 802a0000
$12   : 802a0000 00000000 80298588 802985a8
$16   : 81c52400 81c52454 000003f8 00000002
$20   : c02bd000 00000007 c02e9090 00000001
$24   : 80ea1b78 000186a0                  
$28   : 80ea0000 80ea1cb8 80ef4d80 8015dfe4
Hi    : 003d08db
Lo    : c5476300
epc   : 8011635c     Not tainted
Using defaults from ksymoops -t elf32-little
Cause : 0080001c
        c02e9090 800c7294 00000003 00000002 00000007 00000000 00000001 00000000
        00000000 028c3263 00000003 80ef4d80 81c52400 81c77400 00000001 80ef4e1c
        81f1a584 00000001 00000000 80ea1e00 c0321d68 81c52454 c0321d84 81c7ac8c
        c02bd000 0000001a c02e9090 c02e8be0 c01d0140 8015bfac 81c52454 800c7a6c
Call 
Trace:[<c02fd094>][<800c7294>][<c01d0140>][<8015bfac>][<800c7a6c>][<8010457c>][<80138030>][<80137fd4>][<8020d7cc>][<801384c8>][<80136bf8>][<80104af0>][<80104348>][<80138350>][<80136d78>][<80104b50>][<80136a24>][<80137a98>][<80137a70>][<80105444>][<80138c18>][<80057af0>][<8006ecf8>][<c0263034>][<8006eec4>][<8004bff4>][<8003aed8>][<8006a800>][<8000b0d0>]
Code: 90820000  03e00008  304200ff <94820000> 03e00008  3042ffff  8c820000  
03e00008  00000000 
Error (Oops_bfd_perror): scan_arch for specified architecture File in wrong 
format
Sorry, looks like your binutils cannot handle the specified architecture


>>RA;  8015dfe4 <ssb_pci_read16+58/7c>
>>$12; 802a0000 <swap_info+18c/88c>
>>$14; 80298588 <per_cpu__runqueues+30/410>
>>$15; 802985a8 <per_cpu__runqueues+50/410>
>>$31; 8015dfe4 <ssb_pci_read16+58/7c>

>>???; 8011635c <ioread16+0/c>   <=====

Trace; c02fd094 <END_OF_CODE+40052754/????>
Trace; 800c7294 <sysfs_new_dirent+7c/128>
Trace; c01d0140 <END_OF_CODE+3ff25800/????>
Trace; 8015bfac <ssb_device_probe+44/7c>
Trace; 800c7a6c <sysfs_create_dir+3c/58>
Trace; 8010457c <kobject_get+20/34>
Trace; 80138030 <driver_probe_device+16c/288>
Trace; 80137fd4 <driver_probe_device+110/288>
Trace; 8020d7cc <klist_next+6c/a4>
Trace; 801384c8 <__driver_attach+178/2d8>
Trace; 80136bf8 <next_device+10/2c>
Trace; 80104af0 <kobject_add_varg+58/78>
Trace; 80104348 <kobject_init+58/9c>
Trace; 80138350 <__driver_attach+0/2d8>
Trace; 80136d78 <bus_for_each_dev+5c/a8>
Trace; 80104b50 <kobject_init_and_add+40/58>
Trace; 80136a24 <bus_get+28/3c>
Trace; 80137a98 <bus_add_driver+cc/2b4>
Trace; 80137a70 <bus_add_driver+a4/2b4>
Trace; 80105444 <kobject_uevent_env+3dc/42c>
Trace; 80138c18 <driver_register+80/128>
Trace; 80057af0 <free_hot_cold_page+18c/1e4>
Trace; 8006ecf8 <remove_vm_area+4c/78>
Trace; c0263034 <END_OF_CODE+3ffb86f4/????>
Trace; 8006eec4 <__vunmap+f8/12c>
Trace; 8004bff4 <sys_init_module+1420/15cc>
Trace; 8003aed8 <autoremove_wake_function+0/44>
Trace; 8006a800 <do_brk+174/2e8>
Trace; 8000b0d0 <stack_done+20/3c>


1 error issued.  Results may not be reliable.

> That's what my objdump claims to support as a -m 
> switch (of course we're guessing about how ksymoops calls objdump, but 
> it's an educated guess)

In this case, there was no call to objdump.  Using strace I can see
calls to nm, but nothing about objdump.

This is getting mostly academic though as I do now have a new firmware
based on r12987 which does have a functional b43 driver in it.  I say
functional because while it does work, it shoots the softirq up through
the roof while there is bulk data flying through the wireless interface.
I will post about that in a few mins.

b.

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to