From: Jon Masters <jonathan@jonmasters.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-serial@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Hurley <peter@hurleysoftware.com>,
Rob Herring <robherring2@gmail.com>
Subject: Re: The console log is doubled if earlycon is enabled
Date: Mon, 21 Dec 2015 02:54:39 -0500 [thread overview]
Message-ID: <5677B03F.1030506@jonmasters.org> (raw)
In-Reply-To: <20151130171034.GA14366@kroah.com>
On 11/30/15, 12:10 PM, Greg Kroah-Hartman wrote:
> On Mon, Nov 30, 2015 at 02:53:49PM +0900, Masahiro Yamada wrote:
>> 2015-11-28 9:04 GMT+09:00 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
>>> On Fri, Nov 27, 2015 at 07:21:06PM +0900, Masahiro Yamada wrote:
>>>> Hi,
>>>>
>>>>
>>>> If I add "earlycon" to the kernel parameter, the log message
>>>> on the earlycon is also displayed to the regular console.
>>>> In other words, the same log messages are displayed twice.
>>>>
>>>> I noticed this problem on v4.4-rc1.
>>>> It has not been fixed in the mainline yet, I think.
>>>>
>>>> Anybody who has a clue?
>>>> (I have not done git-bisect yet.)
>>>
>>> Can you do 'git bisect'?
>>
>>
>> The same problem happened on v4.3.
>> (I think I just did not notice the problem before.)
>>
>> So, the bad commit is not in the last merge window.
>
> Is it ok for 4.2? 4.1? Finding out where this started to "fail" would
> be good to know...
Just as a data point, on our internal systems earlycon is known good in
combination with regular console (provided by SPCR ACPI patch) on 4.2.
Jon.
next prev parent reply other threads:[~2015-12-21 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 10:21 The console log is doubled if earlycon is enabled Masahiro Yamada
2015-11-28 0:04 ` Greg Kroah-Hartman
2015-11-30 5:53 ` Masahiro Yamada
2015-11-30 17:10 ` Greg Kroah-Hartman
2015-12-21 7:54 ` Jon Masters [this message]
2015-11-29 2:30 ` Andy Shevchenko
2015-11-30 2:27 ` 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=5677B03F.1030506@jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=robherring2@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox