Re: debug tip after earlycon is closed?

From: Sebastian Reichel
Date: Tue Jul 26 2016 - 22:18:10 EST


On Wed, Jul 27, 2016 at 10:23:09AM +0900, Masahiro Yamada wrote:
> When the kernel fails to boot and its log console is silent,
> I use earlycon and I often find the cause of error with it.
> But, I have been wondering if there is an easy-to-use
> debug tip which is available after earlycon is disabled.
> I noticed the current mainline would not boot on my ARMv8 board.
> According to the following log, I am guessing something wrong
> is happening after the "bootconsole [uniphier0] disabled" log.
> Is there a good practice to see more log?

keep_bootcon [KNL]
Do not unregister boot console at start. This is only
useful for debugging when something happens in the window
between unregistering the boot console and initializing
the real console.

-- Sebastian

Attachment: signature.asc
Description: PGP signature