All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org, Felix Radensky <felix@embedded-sol.com>
Subject: Re: Long boot delay on 460EX with 2.6.28-rc8
Date: Fri, 19 Dec 2008 09:57:43 +1100	[thread overview]
Message-ID: <1229641063.8584.1.camel@localhost> (raw)
In-Reply-To: <20081218190136.GA7752@oksana.dev.rtsoft.ru>

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

On Thu, 2008-12-18 at 22:01 +0300, Anton Vorontsov wrote:
> On Thu, Dec 18, 2008 at 12:51:29PM -0600, Kumar Gala wrote:

> >> I saw somewhat similar behaviour on 83xx target, the cause was
> >> that my .config file contained bogus UDBG_RTAS_CONSOLE=y symbol
> >> (or was it PPC_EARLY_DEBUG_RTAS_PANEL=y? Or HVC_UDBG=y? I don't
> >> quite remember).
> >>
> >> Obviously, on 83xx we don't have RTAS or HVC stuff, but kernel
> >> didn't oops or hang completely, it was busy with executing various
> >> delays in those drivers and then just continued to load.
> >
> > Why are these drivers even doing anything on 83xx?  Seems like they need 
> > something to bind against or some detection of "HW".
> 
> Early console/UDBG is known to cause problems if enabled on
> inappropriate hardware. They start working very early, so it's hard
> for them to do the hw detection (no device tree yet, I presume).

Yes that's the whole point, it's _EARLY_ debug, there's even a big fat
warning in the Kconfig.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-12-18 22:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18 10:29 Long boot delay on 460EX with 2.6.28-rc8 Felix Radensky
2008-12-18 16:02 ` Anton Vorontsov
2008-12-18 18:51   ` Kumar Gala
2008-12-18 19:01     ` Anton Vorontsov
2008-12-18 22:57       ` Michael Ellerman [this message]
2008-12-18 19:02 ` Josh Boyer
2008-12-19  7:36   ` Felix Radensky
2008-12-19  7:56     ` Stefan Roese
2008-12-19  8:30       ` Felix Radensky
2008-12-19  8:30       ` Felix Radensky
2008-12-19 21:23       ` Felix Radensky
2008-12-20  5:37         ` Sean MacLennan
2008-12-20  6:51           ` Felix Radensky
2008-12-22 22:22             ` Leon Woestenberg
2008-12-24 21:40               ` Felix Radensky
2008-12-18 20:04 ` Wolfgang Denk

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=1229641063.8584.1.camel@localhost \
    --to=michael@ellerman.id.au \
    --cc=avorontsov@ru.mvista.com \
    --cc=felix@embedded-sol.com \
    --cc=linuxppc-dev@ozlabs.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.