From: Michael Ellerman <mpe@ellerman•id.au>
To: Pranith Kumar <bobby.prani@gmail•com>
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 19:16:50 +1100 [thread overview]
Message-ID: <1426493810.4716.0.camel@ellerman.id.au> (raw)
In-Reply-To: <CAJhHMCBcyVbNRQSpsyVfk8HMzZ=NXKkknjDRuch+e+yJGB3T5Q@mail.gmail.com>
On Mon, 2015-03-16 at 01:34 -0400, Pranith Kumar wrote:
> On Mon, Mar 16, 2015 at 1:11 AM, Pranith Kumar <bobby.prani@gmail•com> wrote:
> > Hello,
> >
> > I have a power mac mini 32-bit system.
> >
> ...
> > You can see the panic message here: http://imgur.com/s1lH15g. (there
> > is no log and I have no serial console).
>
> There was some debug code in there when it hit. The actual hang seems
> to be in printk_late_init(). It does not return from this. May be this
> is a hint?
That is where the boot consoles get disabled and it switches to the "real"
console. It suggests that the system is not "hung" there but you just lost
output.
Try booting with "keep_bootcon" ?
If that doesn't help try booting with "udbg-immortal".
cheers
next prev parent reply other threads:[~2015-03-16 8:16 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 [this message]
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
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=1426493810.4716.0.camel@ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=bobby.prani@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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