[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zill13z8.fsf@concordia.ellerman.id.au>
Date: Mon, 31 Oct 2016 16:28:59 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Andreas Schwab <schwab@...ux-m68k.org>,
Paul Burton <paul.burton@...tec.com>
Cc: Petr Mladek <pmladek@...e.com>, linux-kernel@...r.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Tejun Heo <tj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Borislav Petkov <bp@...e.de>, linuxppc-dev@...ts.ozlabs.org,
Thorsten Leemhuis <regressions@...mhuis.info>
Subject: Re: [PATCH] console: use first console if stdout-path device doesn't appear
Andreas Schwab <schwab@...ux-m68k.org> writes:
> Any news?
We discovered it also breaks VGA on qemu, which presumably is not the
type of news you were hoping for.
To reproduce you just need to build a ppc64le kernel:
$ apt-get install gcc-powerpc64le-linux-gnu
$ make ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- pseries_le_defconfig
$ make ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu-
And then run qemu:
$ qemu-system-ppc64 -M pseries -m 1G -kernel vmlinux
Which will display the Tux logo but then nothing else and then reboot
after 10 seconds or so.
If you revert 05fd007e4629 on top of rc3 it boots fine.
Paul I tried your "console: use first console if stdout-path device
doesn't appear" patch, but it didn't help. I'll try and work out why,
but it's a bit hard with no output :)
If we can't come up with a fix soon I'm inclined to ask for a revert.
cheers
Powered by blists - more mailing lists