Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1699539 > unrolled thread
| Started by | Andy Shevchenko <andy.shevchenko@gmail.com> |
|---|---|
| First post | 2017-07-30 16:40 +0200 |
| Last post | 2017-07-30 16:40 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 0/5] earlycon hang under some conditions Andy Shevchenko <andy.shevchenko@gmail.com> - 2017-07-30 16:40 +0200
| From | Andy Shevchenko <andy.shevchenko@gmail.com> |
|---|---|
| Date | 2017-07-30 16:40 +0200 |
| Subject | Re: [PATCH 0/5] earlycon hang under some conditions |
| Message-ID | <u8XxU-1uh-9@gated-at.bofh.it> |
On Tue, Jul 18, 2017 at 9:02 AM, Jeffy Chen <jeffy.chen@rock-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
Back to top | Article view | linux.kernel
csiph-web