debugging kernel oops

2011-06-04 Thread ps2k 

Hi All,
I'm new to linux development. We are often seeing kernel oops and failure to
handle paging requests. Any idea how to debug these issues. We have a NAND
flash. I don't know how paging works on an embedded device with flash
memories and not sure why is it needed.

Any help would be greatly appreciated.

Thanks
psk


Jun  1 23:30:01 sbc kernel: [53181.318784] Call Trace:
Jun  1 23:30:01 sbc kernel: [53181.318793] [caab5c50] [c0008114]
show_stack+0x4c/0x1ac (unreliable)
Jun  1 23:30:01 sbc kernel: [53181.318828] [caab5c90] [c0045b4c]
__schedule_bug+0x64/0x78
Jun  1 23:30:01 sbc kernel: [53181.318852] [caab5ca0] [c027d774]
schedule+0x320/0x340
Jun  1 23:30:01 sbc kernel: [53181.318870] [caab5ce0] [c0045d94]
__cond_resched+0x24/0x50
Jun  1 23:30:01 sbc kernel: [53181.31] [caab5cf0] [c027dd90]
cond_resched+0x50/0x58
Jun  1 23:30:01 sbc kernel: [53181.318906] [caab5d00] [c007bb50]
generic_file_buffered_write+0x1ac/0x67c
Jun  1 23:30:01 sbc kernel: [53181.318934] [caab5d90] [c007c2a8]
__generic_file_aio_write_nolock+0x288/0x50c
Jun  1 23:30:01 sbc kernel: [53181.318954] [caab5e00] [c007c594]
generic_file_aio_write+0x68/0xf8
Jun  1 23:30:01 sbc kernel: [53181.318974] [caab5e30] [c00a0c14]
do_sync_write+0xc4/0x138
Jun  1 23:30:01 sbc kernel: [53181.319000] [caab5ef0] [c00a15bc]
vfs_write+0xb4/0x108
Jun  1 23:30:01 sbc kernel: [53181.319018] [caab5f10] [c00a1ba8]
sys_write+0x4c/0x90
Jun  1 23:30:01 sbc kernel: [53181.319036] [caab5f40] [c00101b8]
ret_from_syscall+0x0/0x38
Jun  1 23:30:01 sbc kernel: [53181.319062] --- Exception: c01 at 0xfe506c4
Jun  1 23:30:01 sbc kernel: [53181.319076] LR = 0x10072040
Jun  1 23:30:01 sbc kernel: [53181.375060] Page fault in user mode
within_atomic() = 1 mm = d4cee5a0
Jun  1 23:30:01 sbc kernel: [53181.375091] NIP = fe51434  MSR = 2000f932
Jun  1 23:30:01 sbc kernel: [53181.375105] Oops: Weird page fault, sig: 11
[#1]
Jun  1 23:30:01 sbc kernel: [53181.375113] PREEMPT MPC836x RDK
Jun  1 23:30:01 sbc kernel: [53181.375123] Modules linked in:
Jun  1 23:30:01 sbc kernel: [53181.375134] NIP: 0fe51434 LR: 1006ce70 CTR:
0fe51434
Jun  1 23:30:01 sbc kernel: [53181.375148] REGS: caab5f50 TRAP: 0401   Not
tainted  (2.6.24-sbc-2.0.2.7131)
Jun  1 23:30:01 sbc kernel: [53181.375159] MSR: 2000f932  
CR: 48000442  XER: 
Jun  1 23:30:01 sbc kernel: [53181.375188] TASK = d4cf0430[8646] 'cp'
THREAD: caab4000
Jun  1 23:30:01 sbc kernel: [53181.375246] NIP [0fe51434] 0xfe51434
Jun  1 23:30:01 sbc kernel: [53181.375260] LR [1006ce70] 0x1006ce70
Jun  1 23:30:01 sbc kernel: [53181.375271] Call Trace:
Jun  1 23:30:01 sbc kernel: [53181.375354] Call Trace:
Jun  1 23:30:01 sbc kernel: [53181.375362] [caab5c10] [c0008114]
show_stack+0x4c/0x1ac (unreliable)
Jun  1 23:30:01 sbc kernel: [53181.375394] [caab5c50] [c0045b4c]
__schedule_bug+0x64/0x78
Jun  1 23:30:01 sbc kernel: [53181.375417] [caab5c60] [c027d774]
schedule+0x320/0x340
Jun  1 23:30:01 sbc kernel: [53181.375435] [caab5ca0] [c0045d94]
__cond_resched+0x24/0x50
Jun  1 23:30:01 sbc kernel: [53181.375453] [caab5cb0] [c027dd90]
cond_resched+0x50/0x58
Jun  1 23:30:01 sbc kernel: [53181.375471] [caab5cc0] [c008a7d8]
unmap_vmas+0x5c4/0x5f4
Jun  1 23:30:01 sbc kernel: [53181.375493] [caab5d40] [c008e574]
exit_mmap+0x74/0x11c
Jun  1 23:30:01 sbc kernel: [53181.375513] [caab5d70] [c0048914]
mmput+0x50/0x108
Jun  1 23:30:01 sbc kernel: [53181.375532] [caab5d80] [c004d034]
exit_mm+0xa8/0x110
Jun  1 23:30:01 sbc kernel: [53181.375553] [caab5da0] [c004ecb8]
do_exit+0x13c/0x7bc
Jun  1 23:30:01 sbc kernel: [53181.375571] [caab5de0] [c000e160]
kernel_bad_stack+0x0/0x4c
Jun  1 23:30:01 sbc kernel: [53181.375593] [caab5e10] [c0013120]
do_page_fault+0xb8/0x4e4
Jun  1 23:30:01 sbc kernel: [53181.375611] [caab5f40] [c00105e8]
handle_page_fault+0xc/0x80
Jun  1 23:30:01 sbc kernel: [53181.375632] --- Exception: 401 at 0xfe51434
Jun  1 23:30:01 sbc kernel: [53181.375645] LR = 0x1006ce70
Jun  2 01:30:01 sbc kernel: [ 6381.530572] Unable to handle kernel paging
request for data at address 0xe1054000
Jun  2 01:30:01 sbc kernel: [ 6381.531024] Faulting instruction address:
0xc0149954
Jun  2 01:30:01 sbc kernel: [ 6381.531303] Oops: Kernel access of bad area,
sig: 11 [#1]
Jun  2 01:30:01 sbc kernel: [ 6381.531320] PREEMPT MPC836x RDK
Jun  2 01:30:01 sbc kernel: [ 6381.531329] Modules linked in:
Jun  2 01:30:01 sbc kernel: [ 6381.531340] NIP: c0149954 LR: c014990c CTR:
0018
Jun  2 01:30:01 sbc kernel: [ 6381.531354] REGS: d21cdb10 TRAP: 0300   Not
tainted  (2.6.24-sbc-2.0.2.7131)
Jun  2 01:30:01 sbc kernel: [ 6381.531365] MSR: 9032   CR:
4808  XER: 2000
Jun  2 01:30:01 sbc kernel: [ 6381.531388] DAR: e1054000, DSISR: 2000
Jun  2 01:30:01 sbc kernel: [ 6381.531398] TASK = d8610450[1994] 'cp'
THREAD: d21cc000
Jun  2 01:30:01 sbc kernel: [ 6381.531507] NIP [c0149954]
deflate_fast+0x144/0x34c
Jun  2 01:30:01 sbc kernel: [ 6381.531534] LR [c014990c]
deflate_fast+0xfc/0x34c
Jun  2 01:30:01 sbc kernel: [ 6381.531548] Call Trace:
Jun  2 01:30

MPC8360RDK: Badness at kernel/softirq.c:122

2011-07-12 Thread ps2k 

Hi,
When we are writing to the flash while data traffic is on we do see the
target rebooting with the following messages. Could some body please explain
what's going on here?

Any help is greatly appreciated.

Regards
psk

Call Trace:"
LR [c0005ea4] do_softirq+0x58/0x5c"
Badness at c0051360 [verbose debug info unavailable]"
NIP [c0051360] _local_bh_enable+0x40/0x84"
TASK = d772d430[1343] 'cp' THREAD: dc916000"
MSR: 00021032   CR: 44242482  XER: 2000"
REGS: dc916860 TRAP: 0700   Not tainted  (2.6.24-pwn-0.5.0.)"
NIP: c0051360 LR: c0005ea4 CTR: c01c0098"
[ cut here ]"



[d715c900] [c00060c0] do_softirq+0x58/0x5c"
Badness at net/core/skbuff.c:317"
[d715c8e0] [c0052670] __do_softirq+0x84/0xf8"
[d715c8c0] [c01c36fc] net_tx_action+0x84/0x17c"
[d715c8b0] [c01b9b2c] __kfree_skb+0x18/0xe8"
[d715c8a0] [012c] 0x12c (unreliable)"
Call Trace:"
LR [c01b9b2c] __kfree_skb+0x18/0xe8"
NIP [c01ba584] skb_release_all+0x68/0x124"
TASK = dc54c850[856] 'cp' THREAD: d715c000"
MSR: 00029032   CR: 24242488  XER: 2000"
REGS: d715c7f0 TRAP: 0700   Not tainted  (2.6.24-pwn-0.5.0.)"
NIP: c01ba584 LR: c01b9b2c CTR: c01c3678"
[ cut here ]"


---

Badness at kernel/softirq.c:122"
Call Trace:"
LR [c00060c0] do_softirq+0x58/0x5c"
NIP [c0051f78] _local_bh_enable+0x40/0x84"
TASK = dc5587d0[1763] 'cp' THREAD: dc7ee000"
MSR: 00021032   CR: 44242482  XER: "
REGS: dc7ee850 TRAP: 0700   Not tainted  (2.6.24-pwn-0.5.0.)"
NIP: c0051f78 LR: c00060c0 CTR: c0062040"
[ cut here ]"


-
Badness at kernel/softirq.c:122"
[d7114930] [c001108c] ret_from_except+0x0/0x14"
[d7114920] [c00065d4] do_IRQ+0xa8/0xc8"
[d7114910] [c0052190] irq_exit+0x60/0x80"
[d7114900] [c00060c0] do_softirq+0x58/0x5c (unreliable)"
Call Trace:"
LR [c00060c0] do_softirq+0x58/0x5c"
NIP [c0051f78] _local_bh_enable+0x40/0x84"
TASK = dc01c430[2468] 'cp' THREAD: d7114000"
MSR: 00021032   CR: 44242482  XER: 2000"
REGS: d7114850 TRAP: 0700   Tainted: G  D  (2.6.24-pwn-0.5.0.)"
NIP: c0051f78 LR: c00060c0 CTR: c016b7f4"
[ cut here ]"
-- 
View this message in context: 
http://old.nabble.com/MPC8360RDK%3A-Badness-at-kernel-softirq.c%3A122-tp32050889p32050889.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.

___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev