All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: bug report: Sun Blade 100 kernel panics during boot under 3.0.3
Date: Fri, 26 Aug 2011 01:39:56 +0000	[thread overview]
Message-ID: <20110825.213956.1506607934023206694.davem@davemloft.net> (raw)
In-Reply-To: <20110822233839.GA7793@alumni-linux.ccs.neu.edu>

From: Jim Faulkner <jfaulkne@ccs.neu.edu>
Date: Thu, 25 Aug 2011 13:48:55 -0400

> Yes I agree that there's something screwy in the detection logic.  I get
> a "console [tty0] enabled, bootconsole disabled" when I don't use the
> keep_bootcon kernel parameter, even though I have the
> input-device=keyboard and output-device=screen openprom variables set.
> So add bootconsole detection to the list of things that are screwy.

That's not the problem, this is a known issue.

Early in boot the firmware based console attaches.

Then the generic VT layer attaches and takes over the console, but
because the framebuffer and serial layer hasn't probed devices yet you
get a period during the boot during which no console output occurs.

  parent reply	other threads:[~2011-08-26  1:39 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
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 [this message]
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=20110825.213956.1506607934023206694.davem@davemloft.net \
    --to=davem@davemloft.net \
    --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.