linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Felix Radensky <felix@embedded-sol.com>
Subject: Re: Long boot delay on 460EX with 2.6.28-rc8
Date: Thu, 18 Dec 2008 22:01:36 +0300	[thread overview]
Message-ID: <20081218190136.GA7752@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <A53D4E40-E15F-433B-A9DE-9359533C17F8@kernel.crashing.org>

On Thu, Dec 18, 2008 at 12:51:29PM -0600, Kumar Gala wrote:
>
> On Dec 18, 2008, at 10:02 AM, Anton Vorontsov wrote:
>
>> On Thu, Dec 18, 2008 at 02:29:52AM -0800, Felix Radensky wrote:
>>>
>>> Hi,
>>>
>>> I'm experiencing a long (around 20 sec) delay from the moment
>>> u-boot-1.3.4 passes control to linux and until the first kernel  
>>> message
>>> appears on console.
>>
>> 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).

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

  reply	other threads:[~2008-12-18 19:01 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 [this message]
2008-12-18 22:57       ` Michael Ellerman
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=20081218190136.GA7752@oksana.dev.rtsoft.ru \
    --to=avorontsov@ru.mvista.com \
    --cc=felix@embedded-sol.com \
    --cc=galak@kernel.crashing.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).