From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: No output on console despite ignore_loglevel earlyprintk
Date: Fri, 3 Mar 2017 17:59:06 +0100 [thread overview]
Message-ID: <6cc48f5c-b028-2bb7-c09b-92c36554fe07@suse.de> (raw)
In-Reply-To: <6d16a384-1a4c-bf27-fd81-ea3caf3de6b0@sigmadesigns.com>
Hi,
Am 03.03.2017 um 17:42 schrieb Marc Gonzalez:
> I'm confused about early consoles and earlyprintk, and all that good stuff.
> When my kernel panics, I don't get the expected output.
>
> Using "mem=256M ignore_loglevel earlyprintk"
[...]
> [ 0.014325] Console: colour dummy device 80x30
> [ 0.018885] console [tty0] enabled
> [ 0.022396] bootconsole [earlycon0] disabled
>
> And it hangs there.
>
>
> If I use an explicit console= configuration, I do see the panic.
> Using "mem=256M ignore_loglevel console=ttyS0,115200 earlyprintk"
[...]
> [ 0.014325] Console: colour dummy device 80x30
> [ 0.018899] Calibrating delay loop (skipped), value calculated using timer frequency.. 54.25 BogoMIPS (lpj=90000)
[...]
I have reported a similar phenomenon for multiple new SoCs.
> I suppose this is related to my DT description?
>
> chosen {
> stdout-path = "serial:115200n8";
> };
>
> Isn't stdout-path = "serial:115200n8" supposed to be equivalent to
> console=ttyS0,115200 ?
First of all, that should probably be serial0, and it needs to be
defined as an alias. In my case that's a given.
And yes, AFAIU stdout-path = "serialX:115200n8" should lead to
ttyFOOX,115200n8 being used, in your case it may be ttyS0.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2017-03-03 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 16:42 No output on console despite ignore_loglevel earlyprintk Marc Gonzalez
2017-03-03 16:55 ` Russell King - ARM Linux
2017-03-03 17:26 ` Andreas Färber
2017-03-03 17:46 ` Russell King - ARM Linux
2017-04-05 14:02 ` Marc Gonzalez
2017-04-05 16:37 ` Marc Gonzalez
2017-03-03 16:59 ` Andreas Färber [this message]
2017-03-03 17:07 ` Marc Gonzalez
2017-03-03 17:17 ` Andreas Färber
2017-03-03 17:18 ` Russell King - ARM Linux
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=6cc48f5c-b028-2bb7-c09b-92c36554fe07@suse.de \
--to=afaerber@suse.de \
--cc=linux-arm-kernel@lists.infradead.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