linux-next: qemu boot failures with today's linux-next
Stephen Rothwell
sfr at canb.auug.org.au
Tue Oct 16 10:52:40 AEDT 2018
Hi Michael,
On Mon, 15 Oct 2018 23:45:10 +1100 Michael Ellerman <mpe at ellerman.id.au> wrote:
>
> > Preparing to boot Linux version 4.19.0-rc7 (sfr at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20181016/3ef7404f/attachment.sig>
More information about the Linuxppc-dev
mailing list