linux-kernel - Re: linux-next: qemu boot failures with today's linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 16 Oct 2018 10:52:40 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Michael Ellerman <mpe@...erman.id.au>
Cc:     Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        PowerPC <linuxppc-dev@...ts.ozlabs.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: qemu boot failures with today's linux-next

Hi Michael,

On Mon, 15 Oct 2018 23:45:10 +1100 Michael Ellerman <mpe@...erman.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

Content of type "application/pgp-signature" skipped