All of lore.kernel.org
 help / color / mirror / Atom feed
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 10:01:12 -0400	[thread overview]
Message-ID: <5506E228.3050204@hurleysoftware.com> (raw)
In-Reply-To: <CAJhHMCC06H-BRFBBcD_PfumyvHoFAjbi_MOn7gSeq5y093FSEQ@mail.gmail.com>

On 03/16/2015 09:30 AM, Pranith Kumar wrote:
> On Mon, Mar 16, 2015 at 4:16 AM, Michael Ellerman <mpe@ellerman.id.au> wrote:
>> 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" ?
> 
> I tried this and got to the same place as in the first mail:
> http://imgur.com/s1lH15g
> 
> There is a kernel panic with the message printed. Any more suggestions
> to how to debug this?

git bisect.

Regards,
Peter Hurley
 

  reply	other threads:[~2015-03-16 14:01 UTC|newest]

Thread overview: 24+ 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 [this message]
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:12               ` Pranith Kumar
2015-03-17  3:18               ` Peter Hurley
2015-03-17  3:18                 ` Peter Hurley
2015-03-17  6:33                 ` Pranith Kumar
2015-03-17  6:33                   ` Pranith Kumar
2015-03-17 20:03                   ` Peter Hurley
2015-03-17 20:03                     ` Peter Hurley
2015-03-17 20:07                     ` Pranith Kumar
2015-03-17 20:07                       ` Pranith Kumar
2015-03-17 20:13                       ` Peter Hurley
2015-03-17 20:13                         ` Peter Hurley
2015-03-17 20:16                         ` Pranith Kumar
2015-03-17 20:16                           ` Pranith Kumar
2015-03-17 20:23                           ` Peter Hurley
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=5506E228.3050204@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 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.