From: masami.hiramatsu.pt@hitachi.com (Masami Hiramatsu)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG][arm-soc] kernel panic in boot on Openblocks with the latest kernel
Date: Thu, 28 Feb 2013 20:50:26 +0900 [thread overview]
Message-ID: <512F4482.9070302@hitachi.com> (raw)
In-Reply-To: <20130228113419.GB5688@xps8300>
(2013/02/28 20:34), Heikki Krogerus wrote:
> Hi,
>
> On Thu, Feb 28, 2013 at 08:13:30PM +0900, Masami Hiramatsu wrote:
>> 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
>
> I'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!
--
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt at hitachi.com
WARNING: multiple messages have this Message-ID (diff)
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Gregory CLEMENT <gregory.clement@free-electrons.com>,
linux-arm-kernel@lists.infradead.org, alan@linux.intel.com,
linux-kernel@vger.kernel.org,
thomas.petazzoni@free-electrons.com,
yrl.pp-manager.tt@hitachi.com, iwamatsu@nigauri.org
Subject: Re: Re: [BUG][arm-soc] kernel panic in boot on Openblocks with the latest kernel
Date: Thu, 28 Feb 2013 20:50:26 +0900 [thread overview]
Message-ID: <512F4482.9070302@hitachi.com> (raw)
In-Reply-To: <20130228113419.GB5688@xps8300>
(2013/02/28 20:34), Heikki Krogerus wrote:
> Hi,
>
> On Thu, Feb 28, 2013 at 08:13:30PM +0900, Masami Hiramatsu wrote:
>> 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
>
> I'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!
--
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2013-02-28 11:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 11:13 [BUG][arm-soc] kernel panic in boot on Openblocks with the latest kernel Masami Hiramatsu
2013-02-28 11:13 ` Masami Hiramatsu
2013-02-28 11:34 ` Heikki Krogerus
2013-02-28 11:34 ` Heikki Krogerus
2013-02-28 11:50 ` Masami Hiramatsu [this message]
2013-02-28 11:50 ` Masami Hiramatsu
2013-02-28 14:29 ` Jason Cooper
2013-02-28 14:29 ` Jason Cooper
2013-03-01 8:00 ` Heikki Krogerus
2013-03-01 8:00 ` Heikki Krogerus
2013-03-01 8:05 ` Gregory CLEMENT
2013-03-01 8:05 ` Gregory CLEMENT
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=512F4482.9070302@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.