[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75VdHqD67jcoaQ5EwdTVdoyLNF0DCTQDvTxWikiaOnPs75g@mail.gmail.com>
Date: Sun, 30 Jul 2017 17:31:03 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Jeffy Chen <jeffy.chen@...k-chips.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Brian Norris <briannorris@...omium.org>,
Douglas Anderson <dianders@...omium.org>,
Peter Hurley <peter@...leysoftware.com>,
Sören Brinkmann <soren.brinkmann@...inx.com>,
Michal Simek <michal.simek@...inx.com>,
Marc Gonzalez <marc_gonzalez@...madesigns.com>,
Jiri Slaby <jslaby@...e.com>,
Vineet Gupta <vgupta@...opsys.com>,
"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
linux-snps-arc@...ts.infradead.org,
linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 0/5] earlycon hang under some conditions
On Tue, Jul 18, 2017 at 9:02 AM, Jeffy Chen <jeffy.chen@...k-chips.com> wrote:
> I was testing earlycon with 8250 dw serial console. And it hangs in
> these cases:
> 1/ kernel hang when calling early write function after free_initmem:
> a) the earlycon not disabled after the init code(due to keep_bootcon or
> not specify a real console to switch to)
> b) the early write func is marked as __init, for example 8250_early.
> This serial fix 1/ case only.
Here is another opinion.
I can tell that conditions to get into the trouble are quite unusual or rare.
Any rationale behind why one needs such a combination of parameters?
P.S. For doulble output ask Sergey and Petr (they are quite concerned
about it). Actually strange I didn't see their names in Cc list for
console related stuff,
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists