Re: [PATCH v3] console: use first console if stdout-path device doesn't appear
From: Paul Burton <hidden>
Date: 2016-11-07 17:21:54
Also in:
linuxppc-dev
Possibly related (same subject, not in this thread)
- 2016-11-04 · Re: [PATCH v3] console: use first console if stdout-path device doesn't appear · Sergey Senozhatsky <hidden>
- 2016-11-04 · Re: [PATCH v3] console: use first console if stdout-path device doesn't appear · Andreas Schwab <hidden>
- 2016-11-03 · Re: [PATCH v3] console: use first console if stdout-path device doesn't appear · Paul Burton <hidden>
- 2016-11-03 · Re: [PATCH v3] console: use first console if stdout-path device doesn't appear · Sergey Senozhatsky <hidden>
- 2016-11-03 · [PATCH v3] console: use first console if stdout-path device doesn't appear · Paul Burton <hidden>
Hi Larry, On Monday, 7 November 2016 09:26:37 GMT Larry Finger wrote:
quoted
A revert was already submitted by Hans de Goede & is being discussed over here: https://marc.info/?l=linux-kernel&m=147826151427455&w=2I am a little surprised that I was not CCd on that thread.
Hans started that thread without copying you just as you started your thread without copying Andreas, who reported issues first.
To reiterate, my PowerBook G4 with a PPC32 processor CRASHES on boot. That is a lot more serious than the console output disappearing.
Crashes as in init dies due to lack of a console, right?
As it seems unlikely that this regression will be fixed in the current cycle, I recommend that the reversion of commit 05fd007e4629 until a proper fix is available.
I agree that reverting is probably the best option for now, and have replied
with that in the other thread too.
Thanks,
Paul Attachments
- signature.asc [application/pgp-signature] 801 bytes