Kernel panic in P2020

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Kernel panic in P2020

984 Views
reagankasimayan
Contributor I

Hi All,

I got kernel panic in my P2020 AMC card. Issue occured only once.

Kernel version is 2.6.33.7 (with RT patch enabled). Pasted the complete logs below for your reference.

Any idea?

[ 4570.194555] mmc0: Timeout waiting for hardware interrupt.

[ 4687.164478] mmc0: Timeout waiting for hardware interrupt.

[ 4737.443189] mmc0: Timeout waiting for hardware interrupt.

[ 4789.866888] mmc0: Timeout waiting for hardware interrupt.

[ 4811.926961] mmc0: Timeout waiting for hardware interrupt.

[ 4824.162883] mmc0: Timeout waiting for hardware interrupt.

[ 4841.735129] mmc0: Timeout waiting for hardware interrupt.

[ 4881.163197] mmc0: Timeout waiting for hardware interrupt.

[ 4907.350417] mmc0: Timeout waiting for hardware interrupt.

[ 4907.356832] Unable to handle kernel paging request for data at address 0x0000

[ 4907.364308] Faulting instruction address: 0xc0358904

[ 4907.369266] Oops: Kernel access of bad area, sig: 11 [#1]

[ 4907.374655] PREEMPT SMP NR_CPUS=2 P2020 AMC

[ 4907.378838] Modules linked in:

[ 4907.381888] NIP: c0358904 LR: c0358900 CTR: c03588d8

[ 4907.386845] REGS: e689de40 TRAP: 0300 Not tainted (2.6.33.7-rt29)

[ 4907.393189] MSR: 00029000 <EE,ME,CE> CR: 24244082 XER: 20000000

[ 4907.399300] DEAR: 00000000, ESR: 00000000

[ 4907.403302] TASK = e685b590[25] 'sirq-tasklet/1' THREAD: e689c000 CPU: 1

[ 4907.409825] GPR00: c0358900 e689def0 e685b590 00000000 00029000 00000001 016

[ 4907.418205] GPR08: 013acb73 dd330220 e685b590 00000000 00000000 05082118 3ff

[ 4907.426584] GPR16: 00000002 00000001 00000000 c06332f0 c0682f94 00000002 c05

[ 4907.434963] GPR24: 00000000 00000001 00000000 00000002 000f4240 dd330208 000

[ 4907.443528] NIP [c0358904] esdhc_tasklet_finish+0x2c/0x18c

[ 4907.449006] LR [c0358900] esdhc_tasklet_finish+0x28/0x18c

[ 4907.454394] Call Trace:

[ 4907.456833] [e689def0] [c0358900] esdhc_tasklet_finish+0x28/0x18c (unreliabl)

[ 4907.464063] [e689df10] [c0049358] __tasklet_action+0xbc/0x16c

[ 4907.469806] [e689df40] [c0049ea4] run_ksoftirqd+0x1a4/0x2b8

[ 4907.475376] [e689dfa0] [c005d680] kthread+0x78/0x7c

[ 4907.480254] [e689dff0] [c0010584] kernel_thread+0x4c/0x68

[ 4907.485647] Instruction dump:

[ 4907.488609] 4e800020 9421ffe0 7c0802a6 bfa10014 3ba30008 7c7f1b78 7fa3eb78 9

[ 4907.496378] 4817ae91 387f00ac 4bcf7525 83df003c <813e0000> 81690020 2f8b0000

[ 4907.504331] ---[ end trace 8231010cc60cf454 ]---

[ 4907.516749] NOHZ: local_softirq_pending 40

[ 4907.521505] NOHZ: local_softirq_pending 40

[ 4907.526169] NOHZ: local_softirq_pending 40

[ 4907.531303] NOHZ: local_softirq_pending 40

[ 4907.535481] NOHZ: local_softirq_pending 40

[ 4907.540096] NOHZ: local_softirq_pending 40

[ 4907.550678] NOHZ: local_softirq_pending 40

[ 4907.555763] NOHZ: local_softirq_pending 40

[ 4907.560732] NOHZ: local_softirq_pending 40

[ 4963.039368] Unable to handle kernel paging request for data at address 0x9948

[ 4963.046848] Faulting instruction address: 0xc0035c34

[ 4963.051806] Oops: Kernel access of bad area, sig: 11 [#2]

[ 4963.057195] PREEMPT SMP NR_CPUS=2 P2020 AMC

[ 4963.061378] Modules linked in:

[ 4963.064430] NIP: c0035c34 LR: c003e2bc CTR: c001992c

[ 4963.069387] REGS: e6865d60 TRAP: 0300 Tainted: G D (2.6.33.7-rt29)

[ 4963.076513] MSR: 00021000 <ME,CE> CR: 24000024 XER: 00000000

[ 4963.082360] DEAR: 99451288, ESR: 00000000

[ 4963.086361] TASK = e6841030[0] 'swapper' THREAD: e6864000 CPU: 1

[ 4963.092188] GPR00: d8dce0e4 e6865e10 e6841030 e685b590 e6865e38 00000000 000

[ 4963.100569] GPR08: 2db7a14d e689c000 e6804000 00000060 2db76539 00000000 000

[ 4963.108950] GPR16: a20a0080 0021a684 04301060 56520090 c0666548 c06831a4 000

[ 4963.117332] GPR24: 00000000 00000000 e6864000 c06831a4 e6865e38 c0633e40 000

[ 4963.125901] NIP [c0035c34] task_rq_lock+0x50/0xb0

[ 4963.130603] LR [c003e2bc] try_to_wake_up+0x40/0x3a8

[ 4963.135471] Call Trace:

[ 4963.137909] [e6865e10] [c0638260] 0xc0638260 (unreliable)

[ 4963.143310] [e6865e30] [c003e2bc] try_to_wake_up+0x40/0x3a8

[ 4963.148886] [e6865e70] [c0049920] trigger_softirqs+0x94/0xb0

[ 4963.154545] [e6865e90] [c0004ca4] do_softirq+0x60/0x64

[ 4963.159681] [e6865ea0] [c004a394] irq_exit+0x98/0xc4

[ 4963.164642] [e6865eb0] [c0004e3c] do_IRQ+0xcc/0xf4

[ 4963.169434] [e6865ed0] [c0010e6c] ret_from_except+0x0/0x18

[ 4963.174919] [e6865f90] [c0008758] cpu_idle+0x60/0x17c

[ 4963.179970] [e6865fb0] [c04d79e0] start_secondary+0x340/0x358

[ 4963.185714] [e6865ff0] [c0001c60] __secondary_start+0x30/0x84

[ 4963.191454] Instruction dump:

[ 4963.194417] 7c9c2378 3b6931a4 48000004 801f0000 70090200 4082fff8 7c0000a6 9

[ 4963.202188] 7c000146 813f0004 80090008 5400103a <7d3b002e> 7fdd4a14 7fc3f378

[ 4963.210134] ---[ end trace 8231010cc60cf455 ]---

[ 4963.214744] Kernel panic - not syncing: Attempted to kill the idle task!

[ 4963.221435] Call Trace:

[ 4963.223875] [e6865c50] [c0007570] show_stack+0x4c/0x16c (unreliable)

[ 4963.230231] [e6865c80] [c04d40bc] panic+0xa0/0x194

[ 4963.235020] [e6865cd0] [c0047540] do_exit+0x4c4/0x654

[ 4963.240068] [e6865d20] [c000ddf0] kernel_bad_stack+0x0/0x50

[ 4963.245638] [e6865d40] [c0014a2c] bad_page_fault+0x98/0xd8

[ 4963.251120] [e6865d50] [c0010cc4] handle_page_fault+0x7c/0x80

[ 4963.256861] [e6865e10] [c0638260] 0xc0638260

[ 4963.261129] [e6865e30] [c003e2bc] try_to_wake_up+0x40/0x3a8

[ 4963.266698] [e6865e70] [c0049920] trigger_softirqs+0x94/0xb0

[ 4963.272353] [e6865e90] [c0004ca4] do_softirq+0x60/0x64

[ 4963.277489] [e6865ea0] [c004a394] irq_exit+0x98/0xc4

[ 4963.282449] [e6865eb0] [c0004e3c] do_IRQ+0xcc/0xf4

[ 4963.287237] [e6865ed0] [c0010e6c] ret_from_except+0x0/0x18

[ 4963.292720] [e6865f90] [c0008758] cpu_idle+0x60/0x17c

[ 4963.297768] [e6865fb0] [c04d79e0] start_secondary+0x340/0x358

[ 4963.303510] [e6865ff0] [c0001c60] __secondary_start+0x30/0x84

[ 4963.309256] Rebooting in 180 seconds..

Labels (1)
Tags (1)
0 Kudos
Reply
1 Reply

490 Views
lunminliang
NXP Employee
NXP Employee

See below technical support comment:

It could be recommended to doublecheck the DDR controller settings referring the "AN4039: PowerQUICC and QorIQ DDR3 settings" and the SDRAM device datasheet.

0 Kudos
Reply