linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Andreas Schwab <schwab@linux-m68k.org>,
	Paul Burton <paul.burton@imgtec.com>
Cc: Petr Mladek <pmladek@suse.com>,
	linux-kernel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Tejun Heo <tj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Borislav Petkov <bp@suse.de>,
	linuxppc-dev@lists.ozlabs.org,
	Thorsten Leemhuis <regressions@leemhuis.info>
Subject: Re: [PATCH] console: use first console if stdout-path device doesn't appear
Date: Mon, 31 Oct 2016 16:28:59 +1100	[thread overview]
Message-ID: <87zill13z8.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <878tt6np85.fsf@linux-m68k.org>

Andreas Schwab <schwab@linux-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

  reply	other threads:[~2016-10-31  5:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 12:50 [PATCH] console: Don't prefer first registered if DT specifies stdout-path Paul Burton
2016-08-09 14:12 ` kbuild test robot
2016-08-09 15:10 ` kbuild test robot
2016-08-09 15:19 ` [PATCH v2] " Paul Burton
2016-08-09 21:57   ` Andrew Morton
2016-10-16 18:07   ` Andreas Schwab
2016-10-17 10:33     ` Paul Burton
2016-10-17 17:39       ` Andreas Schwab
2016-10-18  9:18         ` [PATCH] console: use first console if stdout-path device doesn't appear Paul Burton
2016-10-18 18:58           ` Andreas Schwab
2016-10-30  9:46             ` Andreas Schwab
2016-10-31  5:28               ` Michael Ellerman [this message]
2016-10-31 12:14                 ` [PATCH v2] " Paul Burton
2016-10-31 15:50                   ` Paul Burton
2016-10-31 19:21                     ` Larry Finger
2016-10-31 23:09                     ` Sergey Senozhatsky
2016-10-31 23:31                       ` Larry Finger
2016-11-03 12:57                         ` [PATCH v3] " Paul Burton
2016-11-03 17:40                           ` Sergey Senozhatsky
2016-11-03 21:17                             ` Paul Burton
2016-11-04 15:44                               ` Sergey Senozhatsky
2016-11-04  8:05                           ` Andreas Schwab
     [not found]                           ` <8737j3n18r.fsf@concordia.ellerman.id.au>
2016-11-07  9:18                             ` Paul Burton
2016-11-07 15:26                               ` Larry Finger
2016-11-07 17:21                                 ` Paul Burton
2016-11-07 18:27                                   ` Larry Finger
2016-11-08 13:21                                     ` revert 05fd007e46296afb (was: [PATCH v3] console: use first console if stdout-path device doesn't appear) Sergey Senozhatsky
2016-11-03 13:04                         ` [PATCH v2] console: use first console if stdout-path device doesn't appear Paul Burton
2016-11-01  4:39                       ` Michael Ellerman
2016-10-31 15:58                   ` Larry Finger
2016-10-31 12:23                 ` [PATCH] " Paul Burton
2016-10-18  9:21         ` [PATCH v2] console: Don't prefer first registered if DT specifies stdout-path Paul Burton

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=87zill13z8.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paul.burton@imgtec.com \
    --cc=pmladek@suse.com \
    --cc=regressions@leemhuis.info \
    --cc=schwab@linux-m68k.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=tj@kernel.org \
    /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).