[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Kernel Crashes

Title: Message
I am using the following:
Cris Cross Compiler 1.56
Axis Development Software 1.92
Linux 2.4.26
and have installed the Bluez Kernel Drivers and Utils, Libs onto 2 seperate Axis 82 Developer boards. On one of the boards, everything works fine. On the other board, whenever I try to run a bluez command hcitool scan (sometimes the 2nd or 3rd attempt), the board freezes.
I have noted that on this mailing list (Alexander Eder, thread: USB Bluetooth crash & thread:MMU Bus fault) a setting to be changed (CONFIG_ETRAX_DEF_R_BUS_CONFIG)  from 104 to 04. When I checked this setting in my kernel config, I noticed it was already 004. I have reprogrammed both boards again using ./kflash and boot_linux -F.
But still, one of the boards works and one doesn't. I have swapped the usb devices around and done a whole bunch of other tests. but still can not seem to isolate the problem. I have tried disabling USB port 1 with eth1 in the kernel. Still no luck
Is there anything else I can check or do to try and get the one board to work. On the board that works, I was previously playing around with flashing. I noticed on another thread that I should flash the rescue image to initialise the CONFIG_ETRAX_DEF_R_BUS_CONFIG setting, but I am not sure as to how to do this successfully as the ./flashitall script does not come with the 1.92 software.
Here is the output from the board,
BusyBox v0.60.5 (2004.06.23-14:48+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
sh: can't access tty; job control turned off
# hcid
# Apr 27 20:44:03 Aqua hcid[236]: Bluetooth HCI daemon
Apr 27 20:44:03 Aqua hcid[236]: HCI dev 0 up
Apr 27 20:44:03 Aqua hcid[236]: Starting security manager 0

# hcitool scan
hcitool scan
Scanning ...
        00:40:8C:CD:00:00       UCT Axis Developer Board
Unable to handle kernel NULL pointer dereference at virtual address 00000000
Oops: 0000
IRP: c00a6c3c SRP: c001b564 DCCR: 00000484 USP: 9ffff97c MOF: 00000000
 r0: c0e5eec4  r1: 00000002   r2: c0c2cec8  r3: c0c2ceb4
 r4: c0207da0  r5: 000119ec   r6: 00000000  r7: c00a6bf2
 r8: 569000a0  r9: 00b26000  r10: c0b26000 r11: c0228080
r12: c0139eb0 r13: ba2e8ba3 oR10: c0b26000
R_MMU_CAUSE: 0000102e
Process swapper (pid: 0, stackpage=c0156000)
Stack from 9ffff97c:
       9ffffa60 355696f5 9ffff9cc 9ffff9d0 9ffff9c8 9ffff9d4 9ffff9d8 355676f2
       35566b14 35556b96 355567e8 00000004 3556798c 9ffffa58 355688c0 00078b74
       355696f5 3555c05a 35567238 00000000 35567a00 00000000 00000000 00000001
Call Trace:
Stack from c0157de0:
       c0008626 c0157f28 c006b3aa c006b508 c0228080 00000000 c0207da0 c0156000
       c012274c 00000000 c0157ee4 c006b5ce 00000000 c0157ee4 c0008626 c006d7b6
       569000a0 c00a6bf2 00000000 000119ec c0207da0 c0c2ceb4 c0b7a000 c0157ee4
Call Trace: [<c0008626>] [<c006b3aa>] [<c006b508>] [<c006b5ce>] [<c0008626>] [<c006d7b6>] [<c00a6bf2>]
       [<c00a6c78>] [<c006c05c>] [<c00195c2>] [<c00a7cde>] [<c006d590>] [<c006b1c2>] [<c00a6bf2>] [<c001b564>]
       [<c00a6c3c>] [<c006c02e>] [<c006be9a>] [<c006a460>] [<c006a4aa>] [<c006a4ac>] [<c006a460>] [<c00114fa>]
       [<c006a4bc>] [<c0008626>] [<c000407a>]
Code: 00 80 62 ca 3f bd 90 b9 10 c0 61 9a (01) 92 e1 9b 40 31 e9 9a 2a 20 0f 05
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing