From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: qemu boot failures with today's linux-next
Date: Tue, 16 Oct 2018 10:52:40 +1100 [thread overview]
Message-ID: <20181016105240.70369b98@canb.auug.org.au> (raw)
In-Reply-To: <87murfz8dl.fsf@concordia.ellerman.id.au>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
Hi Michael,
On Mon, 15 Oct 2018 23:45:10 +1100 Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> > Preparing to boot Linux version 4.19.0-rc7 (sfr@ash) (gcc version 8.2.0 (Debian 8.2.0-4)) #2 SMP Mon Oct 15 18:53:28 AEDT 2018
> ^^^^^^^^^^
> I assume that's wrong, this is actually linux-next you're booting?
Yes, it was just before -rc8 came out and I suppress the extra version
information to save rebuilding things that depend on the version.
> > Booting Linux via __start() @ 0x0000000000400000 ...
>
> If you git Ctrl-a-c you should get the qemu prompt. Then you can run
> 'info registers' to print the regs and maybe see where it's stuck.
>
> And/or build with EARLY_DEBUG_LPAR to get early console output.
That gave one more line:
[ 0.000000] printk: bootconsole [udbg0] enabled
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-15 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 8:18 linux-next: qemu boot failures with today's linux-next Stephen Rothwell
2018-10-15 8:20 ` Stephen Rothwell
2018-10-15 12:45 ` Michael Ellerman
2018-10-15 23:52 ` Stephen Rothwell [this message]
2018-10-16 9:36 ` Michael Ellerman
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=20181016105240.70369b98@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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