Re: aarch64 broken on qemu

[Jason Thorpe <thorpej%me.com@localhost>]

> On Jul 27, 2020, at 5:50 AM, Maxime Villard <max%m00nbsd.net@localhost> wrote:
> 
> Is it normal that netbsd-aarch64 doesn't work on qemu?
> 
> Launching the latest current with:
> 
> 	qemu-system-aarch64 -M virt -cpu max -m 4g -drive if=none,file=arm64.img,id=hd0 -device virtio-blk-device,drive=hd0 -bios QEMU_EFI.fd
> 
> Gives:
> 
> 	[   1.0000000] panic: kernel diagnostic assertion "dv != NULL" failed: file "/home/source/ab/HEAD/src/sys/kern/subr_prf.c", line 757
> 	[   1.0000000] cpu0: Begin traceback...
> 	[   1.0000000] trace fp ffffc00000f89680
> 	[   1.0000000] fp ffffc00000f896a0 vpanic() at ffffc000004b3fe4 netbsd:vpanic+0x15c
> 	[   1.0000000] fp ffffc00000f89710 kern_assert() at ffffc000007d33ac netbsd:kern_assert+0x5c
> 	[   1.0000000] fp ffffc00000f897a0 aprint_normal_dev() at ffffc000004b5310 netbsd:aprint_normal_dev+0x90
> 	[   1.0000000] fp ffffc00000f89830 gic_v2m_acpi_find_msi_frame() at ffffc0000000f8a0 netbsd:gic_v2m_acpi_find_msi_frame+0x1b0
> 	[   1.0000000] fp ffffc00000f89880 acpi_madt_walk() at ffffc0000006ac18 netbsd:acpi_madt_walk+0x60
> 	[   1.0000000] fp ffffc00000f898b0 gic_acpi_attach() at ffffc0000000f100 netbsd:gic_acpi_attach+0xf0

Can you provide the full boot messages just up to the panic?  Seems like the only way that can happen is if the "armgic" device doesn't get attached ... commented out in the config file?

-- thorpej