From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Hurley <peter@hurleysoftware.com>,
Rob Herring <robherring2@gmail.com>
Subject: Re: The console log is doubled if earlycon is enabled
Date: Mon, 30 Nov 2015 11:27:41 +0900 [thread overview]
Message-ID: <CAK7LNATW2EtdKYWUOrFgynoyHP9k5gh9dAMzgUM3HwYTN=eNHQ@mail.gmail.com> (raw)
In-Reply-To: <CAHp75Ven8H1DYuTYcWRpt4rTxhS=P5r7VJ2ajpK8H7j+rgbMYg@mail.gmail.com>
Hi Andy,
2015-11-29 11:30 GMT+09:00 Andy Shevchenko <andy.shevchenko@gmail.com>:
> On Fri, Nov 27, 2015 at 12:21 PM, Masahiro Yamada
> <yamada.masahiro@socionext.com> 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.)
>
> Does adding the following line in
> drivers/tty/serial/8250/8250_early.c:: early_serial8250_setup() fix
> the issue?
>
> device->con->flags &= ~CON_PRINTBUFFER;
No. I tried that, but it did not fix the problem.
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2015-11-30 2:27 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
2015-11-29 2:30 ` Andy Shevchenko
2015-11-30 2:27 ` Masahiro Yamada [this message]
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='CAK7LNATW2EtdKYWUOrFgynoyHP9k5gh9dAMzgUM3HwYTN=eNHQ@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=robherring2@gmail.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;
as well as URLs for NNTP newsgroup(s).