All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Faulkner <jfaulkne@ccs.neu.edu>
To: sparclinux@vger.kernel.org
Subject: Re: bug report: Sun Blade 100 kernel panics during boot under 3.0.3
Date: Wed, 24 Aug 2011 19:50:53 +0000	[thread overview]
Message-ID: <20110824195053.GA12537@alumni-linux.ccs.neu.edu> (raw)
In-Reply-To: <20110822233839.GA7793@alumni-linux.ccs.neu.edu>

On Mon, Aug 22, 2011 at 05:36:02PM -0700, David Miller wrote:

> Unfortunately we need the very first crash message that happens, but
> even your first snapshot is after other crashes have occurred.
> 
> You'll need to build a kernel with CONFIG_BOOT_PRINTK_DELAYED enabled
> and then you can boot with boot_delay=xxx (where "xxx" is something
> like 100, it's in milliseconds) to slow down the message printing so
> that you can capture the first message cleanly.

OK, I've attached several images of the kernel panic w/ boot_delay to
the bug:

https://bugzilla.kernel.org/show_bug.cgi?idA522


  parent reply	other threads:[~2011-08-24 19:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 23:38 bug report: Sun Blade 100 kernel panics during boot under 3.0.3 Jim Faulkner
2011-08-23  0:36 ` David Miller
2011-08-24 19:50 ` Jim Faulkner [this message]
2011-08-24 19:53 ` David Miller
2011-08-24 21:03 ` Sam Ravnborg
2011-08-24 23:17 ` David Miller
2011-08-25  9:58 ` Josip Rodin
2011-08-25 10:06 ` Josip Rodin
2011-08-25 17:32 ` Jim Faulkner
2011-08-25 17:48 ` Jim Faulkner
2011-08-25 18:28 ` Josip Rodin
2011-08-26  1:39 ` David Miller
2011-08-30 23:01 ` Jim Faulkner
2011-08-30 23:26 ` David Miller
2011-08-31  0:47 ` Jim Faulkner
2011-08-31  7:04 ` bug report: Sun Blade 100 kernel panics during boot under Meelis Roos
2011-08-31 19:59 ` bug report: Sun Blade 100 kernel panics during boot under 3.0.3 David Miller
2011-09-02  1:10 ` Jim Faulkner

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=20110824195053.GA12537@alumni-linux.ccs.neu.edu \
    --to=jfaulkne@ccs.neu.edu \
    --cc=sparclinux@vger.kernel.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.