debug tip after earlycon is closed?
Masahiro Yamada
yamada.masahiro at socionext.com
Tue Jul 26 20:26:27 PDT 2016
Hi Sebastian,
2016-07-27 11:17 GMT+09:00 Sebastian Reichel <sre at kernel.org>:
> Hi,
>
> 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?
>
> Documentation/kernel-parameters.txt
> 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.
I did not know this kernel parameter, and it is exactly what I wanted.
Thanks a lot!
--
Best Regards
Masahiro Yamada
More information about the linux-arm-kernel
mailing list