On Tue, Mar 11, 2025 at 09:33:29PM +0000, Mark Brown wrote: > On Tue, Mar 11, 2025 at 11:06:56PM +0200, Mike Rapoport wrote: > > On Tue, Mar 11, 2025 at 05:51:06PM +0000, Mark Brown wrote: > > > > This patch appears to be causing breakage on a number of 32 bit arm > > > platforms, including qemu's virt-2.11,gic-version=3. Affected platforms > > > die on boot with no output, a bisect with qemu points at this commit and > > > those for physical platforms appear to be converging on the same place. > > > Can you share how this can be reproduced with qemu? > > https://lava.sirena.org.uk/scheduler/job/1184953 > > Turns out it's actually producing output on qemu: > > [ 0.000000] Booting Linux on physical CPU 0x0 > [ 0.000000] Linux version 6.14.0-rc6-next-20250311 (tuxmake@tuxmake) (arm-linux-gnueabihf-gcc (Debian 13.3.0-5) 13.3.0, GNU ld (GNU Binutils for Debian) 2.43.1) #1 SMP @1741691801 > [ 0.000000] CPU: ARMv7 Processor [414fc0f0] revision 0 (ARMv7), cr=10c5387d > [ 0.000000] CPU: div instructions available: patching division code > [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache > [ 0.000000] OF: fdt: Machine model: linux,dummy-virt > [ 0.000000] random: crng init done > [ 0.000000] earlycon: pl11 at MMIO 0x09000000 (options '') > [ 0.000000] printk: legacy bootconsole [pl11] enabled > [ 0.000000] Memory policy: Data cache writealloc > [ 0.000000] efi: UEFI not found. > [ 0.000000] cma: Reserved 64 MiB at 0x00000000 > > - I'd only been sampling the logs for the physical platforms, none of > which had shown anything. > > (you dropped me from the CCs BTW!) That's because your emails contain a "Mail-Followup-To:" header. Please read: https://datatracker.ietf.org/doc/html/draft-ietf-drums-mail-followup-to-00.txt particularly 2.4. In effect, by including this header, you asked to be dropped. -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
