From: Sebastian Reichel <sre@kernel.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Hurley <peter@hurleysoftware.com>,
Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: debug tip after earlycon is closed?
Date: Wed, 27 Jul 2016 04:17:49 +0200 [thread overview]
Message-ID: <20160727021748.GA9857@earth> (raw)
In-Reply-To: <CAK7LNASrqbt+RzD64zcAMjmBjJqa2sc2UG+mnEX8npZ9DBJodQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
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.
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: sre@kernel.org (Sebastian Reichel)
To: linux-arm-kernel@lists.infradead.org
Subject: debug tip after earlycon is closed?
Date: Wed, 27 Jul 2016 04:17:49 +0200 [thread overview]
Message-ID: <20160727021748.GA9857@earth> (raw)
In-Reply-To: <CAK7LNASrqbt+RzD64zcAMjmBjJqa2sc2UG+mnEX8npZ9DBJodQ@mail.gmail.com>
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.
-- Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160727/9697ab95/attachment.sig>
next prev parent reply other threads:[~2016-07-27 2:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 1:23 debug tip after earlycon is closed? Masahiro Yamada
2016-07-27 1:23 ` Masahiro Yamada
2016-07-27 2:17 ` Sebastian Reichel [this message]
2016-07-27 2:17 ` Sebastian Reichel
2016-07-27 3:26 ` Masahiro Yamada
2016-07-27 3:26 ` Masahiro Yamada
2016-07-27 7:32 ` Arnd Bergmann
2016-07-27 7:32 ` Arnd Bergmann
2016-07-27 7:32 ` Arnd Bergmann
2016-07-28 2:08 ` Masahiro Yamada
2016-07-28 2:08 ` Masahiro Yamada
2016-07-28 7:44 ` Arnd Bergmann
2016-07-28 7:44 ` Arnd Bergmann
2016-07-28 12:20 ` Russell King - ARM Linux
2016-07-28 12:20 ` Russell King - ARM Linux
2016-08-08 9:08 ` Rabin Vincent
2016-08-08 9:08 ` Rabin Vincent
2016-08-12 3:44 ` Masahiro Yamada
2016-08-12 3:44 ` Masahiro Yamada
2016-08-12 3:44 ` Masahiro Yamada
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=20160727021748.GA9857@earth \
--to=sre@kernel.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=robh+dt@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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.