kernel panic in boot on Openblocks with the latest kernel
Hi,
I tried the latest "fixes" branch of arm-soc.git on OpenBlocks AX3 (Marvel Armada-XP) and got below kernel panic in boot sequence. It seems that we have an exception while cpu is in idle.
----
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200 Backtrace: [<c00113d4>] (dump_backtrace+0x0/0x110) from [<c04a7324>] (dump_stack+0x18/0x1c) r6:ef2bcc00 r5:c06532b0 r4:ef2bcc00 r3:00000001 [<c04a730c>] (dump_stack+0x0/0x1c) from [<c04a7434>] (panic+0x90/0x1ec) [<c04a73a4>] (panic+0x0/0x1ec) from [<c002613c>] (do_exit+0x500/0x960) r3:ef2c0dc0 r2:ef2bcc00 r1:00000200 r0:c0584be1 r7:c063e040 [<c0025c3c>] (do_exit+0x0/0x960) from [<c0026790>] (do_group_exit+0xa4/0xd0) r7:000000f8 [<c00266ec>] (do_group_exit+0x0/0xd0) from [<c00267d4>] (__wake_up_parent+0x0/0x28) r7:000000f8 r6:0000003c r5:bee6bf14 r4:000703ae [<c00267bc>] (sys_exit_group+0x0/0x18) from [<c000d8c0>] (ret_fast_syscall+0x0/0x30) CPU0: stopping Backtrace: [<c00113d4>] (dump_backtrace+0x0/0x110) from [<c04a7324>] (dump_stack+0x18/0x1c) r6:c063df48 r5:00000000 r4:c0688e98 r3:c064def4 [<c04a730c>] (dump_stack+0x0/0x1c) from [<c00128f4>] (handle_IPI+0xc8/0x12c) [<c001282c>] (handle_IPI+0x0/0x12c) from [<c00085a0>] (armada_370_xp_handle_irq+0x98/0xb0) r5:c0689070 r4:00000005 [<c0008508>] (armada_370_xp_handle_irq+0x0/0xb0) from [<c04ae680>] (__irq_svc+0x40/0x50) Exception stack(0xc063df48 to 0xc063df90)
df40: ffffffed 00000000 027ac000 60000013 c063c000 c0688c88
df60: c04b5518 c2ddffc0 0000406a 562f5842 00000000 c063dfac c063df90 c063df90
df80: c000e588 c000e590 60000013 ffffffff
[<c000e4d8>] (cpu_idle+0x0/0x104) from [<c04a266c>] (rest_init+0x64/0x7c)
r6:c0625a50 r5:00000000 r4:c06450e0 r3:00000000
[<c04a2608>] (rest_init+0x0/0x7c) from [<c05fb848>] (start_kernel+0x2d4/0x32c) [<c05fb574>] (start_kernel+0x0/0x32c) from [<00008074>] (0x8074)
----
And I found that this panic also happened on the latest linus tree. Git-bisect told me that the 8250 serial driver patch is the first bad commit.
serial: 8250_dw: Don't use UPF_FIXED_TYPE
966c4e39b5f7f249d7bb4c409176c9e6c5d48025
https://patchwork.kernel.org/patch/1958931/
Thank you,
Signature · 4 lines
Masami HIRAMATSU IT Management Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: masami.hiramatsu.pt at hitachi.com
Hi,
Quoted 41 lines · Masami Hiramatsu
Hi,
I tried the latest "fixes" branch of arm-soc.git on OpenBlocks AX3 (Marvel Armada-XP) and got below kernel panic in boot sequence. It seems that we have an exception while cpu is in idle.
----
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200 Backtrace: [<c00113d4>] (dump_backtrace+0x0/0x110) from [<c04a7324>] (dump_stack+0x18/0x1c) r6:ef2bcc00 r5:c06532b0 r4:ef2bcc00 r3:00000001 [<c04a730c>] (dump_stack+0x0/0x1c) from [<c04a7434>] (panic+0x90/0x1ec) [<c04a73a4>] (panic+0x0/0x1ec) from [<c002613c>] (do_exit+0x500/0x960) r3:ef2c0dc0 r2:ef2bcc00 r1:00000200 r0:c0584be1 r7:c063e040 [<c0025c3c>] (do_exit+0x0/0x960) from [<c0026790>] (do_group_exit+0xa4/0xd0) r7:000000f8 [<c00266ec>] (do_group_exit+0x0/0xd0) from [<c00267d4>] (__wake_up_parent+0x0/0x28) r7:000000f8 r6:0000003c r5:bee6bf14 r4:000703ae [<c00267bc>] (sys_exit_group+0x0/0x18) from [<c000d8c0>] (ret_fast_syscall+0x0/0x30) CPU0: stopping Backtrace: [<c00113d4>] (dump_backtrace+0x0/0x110) from [<c04a7324>] (dump_stack+0x18/0x1c) r6:c063df48 r5:00000000 r4:c0688e98 r3:c064def4 [<c04a730c>] (dump_stack+0x0/0x1c) from [<c00128f4>] (handle_IPI+0xc8/0x12c) [<c001282c>] (handle_IPI+0x0/0x12c) from [<c00085a0>] (armada_370_xp_handle_irq+0x98/0xb0) r5:c0689070 r4:00000005 [<c0008508>] (armada_370_xp_handle_irq+0x0/0xb0) from [<c04ae680>] (__irq_svc+0x40/0x50) Exception stack(0xc063df48 to 0xc063df90)df40: ffffffed 00000000
027ac00060000013c063c000c0688c88
df60:c04b5518c2ddffc00000406a562f584200000000c063dfacc063df90c063df90
df80:c000e588c000e59060000013 ffffffff
[<c000e4d8>] (cpu_idle+0x0/0x104) from [<c04a266c>] (rest_init+0x64/0x7c)
r6:c0625a50 r5:00000000 r4:c06450e0 r3:00000000
[<c04a2608>] (rest_init+0x0/0x7c) from [<c05fb848>] (start_kernel+0x2d4/0x32c) [<c05fb574>] (start_kernel+0x0/0x32c) from [<00008074>] (0x8074)
----
Quoted 7 lines
And I found that this panic also happened on the latest linus tree. Git-bisect told me that the 8250 serial driver patch is the first bad commit.
serial: 8250_dw: Don't use
UPF_FIXED_TYPE
966c4e39b5f7f249d7bb4c409176c9e6c5d48025
I'm assuming this is the same issue Gregory already reported. Can you try the attached diff, and tell if it fixes the issue?
Thanks,
Signature · 8 lines
heikki -------------- next part -------------- A non-text attachment was scrubbed... Name: reg-io_width_to_one.diff Type: text/x-diff Size: 1148 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130228/ca2f5a1a/attachment.bin>
Quoted 48 lines · Heikki Krogerus
Hi,
Quoted 45 lines · Masami Hiramatsu
Hi,
I tried the latest "fixes" branch of arm-soc.git on OpenBlocks AX3 (Marvel Armada-XP) and got below kernel panic in boot sequence. It seems that we have an exception while cpu is in idle.
----
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200 Backtrace: [<c00113d4>] (dump_backtrace+0x0/0x110) from [<c04a7324>] (dump_stack+0x18/0x1c) r6:ef2bcc00 r5:c06532b0 r4:ef2bcc00 r3:00000001 [<c04a730c>] (dump_stack+0x0/0x1c) from [<c04a7434>] (panic+0x90/0x1ec) [<c04a73a4>] (panic+0x0/0x1ec) from [<c002613c>] (do_exit+0x500/0x960) r3:ef2c0dc0 r2:ef2bcc00 r1:00000200 r0:c0584be1 r7:c063e040 [<c0025c3c>] (do_exit+0x0/0x960) from [<c0026790>] (do_group_exit+0xa4/0xd0) r7:000000f8 [<c00266ec>] (do_group_exit+0x0/0xd0) from [<c00267d4>] (__wake_up_parent+0x0/0x28) r7:000000f8 r6:0000003c r5:bee6bf14 r4:000703ae [<c00267bc>] (sys_exit_group+0x0/0x18) from [<c000d8c0>] (ret_fast_syscall+0x0/0x30) CPU0: stopping Backtrace: [<c00113d4>] (dump_backtrace+0x0/0x110) from [<c04a7324>] (dump_stack+0x18/0x1c) r6:c063df48 r5:00000000 r4:c0688e98 r3:c064def4 [<c04a730c>] (dump_stack+0x0/0x1c) from [<c00128f4>] (handle_IPI+0xc8/0x12c) [<c001282c>] (handle_IPI+0x0/0x12c) from [<c00085a0>] (armada_370_xp_handle_irq+0x98/0xb0) r5:c0689070 r4:00000005 [<c0008508>] (armada_370_xp_handle_irq+0x0/0xb0) from [<c04ae680>] (__irq_svc+0x40/0x50) Exception stack(0xc063df48 to 0xc063df90)df40: ffffffed 00000000
027ac00060000013c063c000c0688c88
df60:c04b5518c2ddffc00000406a562f584200000000c063dfacc063df90c063df90
df80:c000e588c000e59060000013 ffffffff
[<c000e4d8>] (cpu_idle+0x0/0x104) from [<c04a266c>] (rest_init+0x64/0x7c)
r6:c0625a50 r5:00000000 r4:c06450e0 r3:00000000
[<c04a2608>] (rest_init+0x0/0x7c) from [<c05fb848>] (start_kernel+0x2d4/0x32c) [<c05fb574>] (start_kernel+0x0/0x32c) from [<00008074>] (0x8074)
----And I found that this panic also happened on the latest linus tree. Git-bisect told me that the 8250 serial driver patch is the first bad commit.
Quoted 6 lines
Quoted 3 lines
serial: 8250_dw: Don't use
UPF_FIXED_TYPE
966c4e39b5f7f249d7bb4c409176c9e6c5d48025I'm assuming this is the same issue Gregory already reported. Can you try the attached diff, and tell if it fixes the issue?
I've tested and ensured this diff fixed the problem. :D
Thank you!
Signature · 4 lines
Masami HIRAMATSU IT Management Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: masami.hiramatsu.pt at hitachi.com
Heikki,
Quoted 48 lines · Heikki Krogerus
Hi,
Quoted 45 lines · Masami Hiramatsu
Hi,
I tried the latest "fixes" branch of arm-soc.git on OpenBlocks AX3 (Marvel Armada-XP) and got below kernel panic in boot sequence. It seems that we have an exception while cpu is in idle.
----
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200 Backtrace: [<c00113d4>] (dump_backtrace+0x0/0x110) from [<c04a7324>] (dump_stack+0x18/0x1c) r6:ef2bcc00 r5:c06532b0 r4:ef2bcc00 r3:00000001 [<c04a730c>] (dump_stack+0x0/0x1c) from [<c04a7434>] (panic+0x90/0x1ec) [<c04a73a4>] (panic+0x0/0x1ec) from [<c002613c>] (do_exit+0x500/0x960) r3:ef2c0dc0 r2:ef2bcc00 r1:00000200 r0:c0584be1 r7:c063e040 [<c0025c3c>] (do_exit+0x0/0x960) from [<c0026790>] (do_group_exit+0xa4/0xd0) r7:000000f8 [<c00266ec>] (do_group_exit+0x0/0xd0) from [<c00267d4>] (__wake_up_parent+0x0/0x28) r7:000000f8 r6:0000003c r5:bee6bf14 r4:000703ae [<c00267bc>] (sys_exit_group+0x0/0x18) from [<c000d8c0>] (ret_fast_syscall+0x0/0x30) CPU0: stopping Backtrace: [<c00113d4>] (dump_backtrace+0x0/0x110) from [<c04a7324>] (dump_stack+0x18/0x1c) r6:c063df48 r5:00000000 r4:c0688e98 r3:c064def4 [<c04a730c>] (dump_stack+0x0/0x1c) from [<c00128f4>] (handle_IPI+0xc8/0x12c) [<c001282c>] (handle_IPI+0x0/0x12c) from [<c00085a0>] (armada_370_xp_handle_irq+0x98/0xb0) r5:c0689070 r4:00000005 [<c0008508>] (armada_370_xp_handle_irq+0x0/0xb0) from [<c04ae680>] (__irq_svc+0x40/0x50) Exception stack(0xc063df48 to 0xc063df90)df40: ffffffed 00000000
027ac00060000013c063c000c0688c88
df60:c04b5518c2ddffc00000406a562f584200000000c063dfacc063df90c063df90
df80:c000e588c000e59060000013 ffffffff
[<c000e4d8>] (cpu_idle+0x0/0x104) from [<c04a266c>] (rest_init+0x64/0x7c)
r6:c0625a50 r5:00000000 r4:c06450e0 r3:00000000
[<c04a2608>] (rest_init+0x0/0x7c) from [<c05fb848>] (start_kernel+0x2d4/0x32c) [<c05fb574>] (start_kernel+0x0/0x32c) from [<00008074>] (0x8074)
----And I found that this panic also happened on the latest linus tree. Git-bisect told me that the 8250 serial driver patch is the first bad commit.
Quoted 6 lines
Quoted 3 lines
serial: 8250_dw: Don't use
UPF_FIXED_TYPE
966c4e39b5f7f249d7bb4c409176c9e6c5d48025I'm assuming this is the same issue Gregory already reported. Can you try the attached diff, and tell if it fixes the issue?
If you have a moment, could you put this into a formal patch and send to lakml? If I could Gregory and Masami's Tested-by's on that, I'll queue it up for -rc1/2.
thx,
Jason.
Quoted 55 lines
Thanks,
Signature · 1 line
heikkiarch/arm/boot/dts/armada-370-xp.dtsi +2
-2@@ -54,7 +54,7 @@ reg = <0xd0012000 0x100>; reg-shift = <2>; interrupts = <41>; - reg-io-width = <4>; + reg-io-width = <1>; status = "disabled"; }; serial at d0012100 {@@ -62,7 +62,7 @@ reg = <0xd0012100 0x100>; reg-shift = <2>; interrupts = <42>; - reg-io-width = <4>; + reg-io-width = <1>; status = "disabled"; };arch/arm/boot/dts/armada-xp.dtsi +2
-2@@ -46,7 +46,7 @@ reg = <0xd0012200 0x100>; reg-shift = <2>; interrupts = <43>; - reg-io-width = <4>; + reg-io-width = <1>; status = "disabled"; }; serial at d0012300 {@@ -54,7 +54,7 @@ reg = <0xd0012300 0x100>; reg-shift = <2>; interrupts = <44>; - reg-io-width = <4>; + reg-io-width = <1>; status = "disabled"; };_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Hi Jason,
Quoted 3 lines · Jason Cooper
If you have a moment, could you put this into a formal patch and send to lakml? If I could Gregory and Masami's Tested-by's on that, I'll queue it up for -rc1/2.
OK, I'll prepare the patch. I thought that Gregory was going to create a patch for this.
Br,
Signature · 1 line
heikki
Quoted 9 lines · Heikki Krogerus
Hi Jason,
Quoted 3 lines · Jason Cooper
If you have a moment, could you put this into a formal patch and send to lakml? If I could Gregory and Masami's Tested-by's on that, I'll queue it up for -rc1/2.
OK, I'll prepare the patch. I thought that Gregory was going to create a patch for this.
If you want I still can take care of it.
Quoted 3 lines
Br,
Signature · 4 lines
Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com