linux-kernel - Re: linux-next: boot failure after merge of the memblock tree

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20241024092338.6a8f10c7@canb.auug.org.au>
Date: Thu, 24 Oct 2024 09:23:38 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Su Hua <suhua.tanke@...il.com>
Cc: Mike Rapoport <rppt@...nel.org>, Linux Kernel Mailing List
 <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>
Subject: Re: linux-next: boot failure after merge of the memblock tree

Hi,

On Wed, 23 Oct 2024 11:20:43 +0800 Su Hua <suhua.tanke@...il.com> wrote:
>
> Thanks, I'd also like to set up the environment for testing; could you
> please share the command line instructions or XML files used for
> testing?

Sorry for the delay.  I run the following qemu command line:

qemu-system-ppc64 -M pseries -m 2G -vga none -nographic -kernel $vmlinux -initrd $initrd

where $vmlinux is the result of a PowerPC pseries_le_defconfig build
and $initrd is just sufficient to get into user mode and then shutdown
again.  This latter is not really relevant here since we don't get to
user mode.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped