linux-kernel - Re: linux-next: boot failure after merge of the dma-mapping 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: <20250710094612.53f2d85b@canb.auug.org.au>
Date: Thu, 10 Jul 2025 09:46:12 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Leon Romanovsky <leon@...nel.org>
Cc: Marek Szyprowski <m.szyprowski@...sung.com>, Linux Kernel Mailing List
 <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>, Christoph Hellwig <hch@....de>, Jason
 Gunthorpe <jgg@...dia.com>
Subject: Re: linux-next: boot failure after merge of the dma-mapping tree

Hi Leon,

On Wed, 9 Jul 2025 20:41:08 +0300 Leon Romanovsky <leon@...nel.org> wrote:
>
> Can you please provide the kernel command line to determine which DMA
> path is taken?

Sorry I did not respond earlier (your email arrived at 3:41am my time
:-)) but you seem to have figured it out, thanks.  I will let you know
this evening if it has not worked.

For reference the qemu command line was

qemu-system-ppc64 -M pseries,cap-hpt-max-page-size=4k,accel=kvm -m 2G -vga none -nographic -enable-kvm -kernel $vmlinux -initrd $initrd

The kernel was a powercp pseries_le_defconfig build (but setting
CONFIG_PPC_4K_PAGES=y instead of CONFIG_PPC_64K_PAGES=y).
-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped