From: Peter Hurley <peter@hurleysoftware.com>
To: Pranith Kumar <bobby.prani@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: "open list:LINUX FOR POWERPC..." <linuxppc-dev@lists.ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux panic on 4.0.0-rc4
Date: Mon, 16 Mar 2015 22:58:33 -0400 [thread overview]
Message-ID: <55079859.1020205@hurleysoftware.com> (raw)
In-Reply-To: <CAJhHMCDCoo7g5WrXKPEbemoChQn6BGZOXD00z4kZqVE5boEBhA@mail.gmail.com>
On 03/16/2015 10:02 PM, Pranith Kumar wrote:
> On Mon, Mar 16, 2015 at 7:22 PM, Michael Ellerman <mpe@ellerman.id.au> wrote:
>>
>> The log shows that init is being killed, that's what's causing the panic.
>>
>> The exitcode of init is 0x200, which due to the vagaries of UNIX is I think an
>> "exit status" of 2 in the common usage.
>>
>> But it suggests that your init is just exiting for some reason?
>>
>
> Yeah, seems like that. Not sure why though. git bisect seems to be the
> only option.
>
>> What is your init?
>
> I am using systemd from debian unstable.
Do you have a stdout-path property defined in your dts to a serial
console you're not actually using?
next prev parent reply other threads:[~2015-03-17 2:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 5:11 linux panic on 4.0.0-rc4 Pranith Kumar
2015-03-16 5:34 ` Pranith Kumar
2015-03-16 8:16 ` Michael Ellerman
2015-03-16 13:30 ` Pranith Kumar
2015-03-16 14:01 ` Peter Hurley
2015-03-16 23:22 ` Michael Ellerman
2015-03-17 2:02 ` Pranith Kumar
2015-03-17 2:58 ` Peter Hurley [this message]
2015-03-17 3:12 ` Pranith Kumar
2015-03-17 3:18 ` Peter Hurley
2015-03-17 6:33 ` Pranith Kumar
2015-03-17 20:03 ` Peter Hurley
2015-03-17 20:07 ` Pranith Kumar
2015-03-17 20:13 ` Peter Hurley
2015-03-17 20:16 ` Pranith Kumar
2015-03-17 20:23 ` Peter Hurley
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=55079859.1020205@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=bobby.prani@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).