Re: oops .. looks like the FreeBSD snapshot for 07 Oct 2022 is still a tad fried

On 10/10/22 00:33, Dennis Clarke wrote:
> 
> Looking at : https://cgit.freebsd.org/src/log/
> 
> I see a bunch of goodness from Mitchel Horne there for the
> pmap_remove_pages() code but the install disk images for
> FreeBSD CURRENT snapshot still blow up.
> 
> Are there going to be some new install images soonish?
> This week maybe?
> 
> Found 4 CPUs in the device tree
> Copyright (c) 1992-2022 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>          The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 14.0-CURRENT #0 main-n258483-b05b1ecbef0: Fri Oct  7 05:52:47 
> UTC 2022
> 
> root@releng1.nyi.freebsd.org:/usr/obj/usr/src/riscv.riscv64/sys/GENERIC 
> riscv
> FreeBSD clang version 14.0.5 (https://github.com/llvm/llvm-project.git 
> llvmorg-14.0.5-0-gc12386ae247c)
> WARNING: WITNESS option enabled, expect reduced performance.
> VT: init without driver.
> Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffc002bff000.
> Preloaded TSLOG data "TSLOG" at 0xffffffc002c08288.
> .
> .
> .
> avail memory = 16649957376 (15878 MB)
> No static device mappings.
> Starting CPU 2 (hart 0)
> Starting CPU 3 (hart 1)
> Starting CPU 1 (hart 3)
> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
> panic: ISA string truncated

Hi,

This one is known too. There are some shortcomings with how we handle 
the ISA string provided by QEMU, that became apparent with the recent 
update to version 7.1.0.

Fixing this is a priority for me this week, ideally before the next 
snapshot build. For progress, subscribe to:
https://reviews.freebsd.org/D36601

As a workaround in the meantime, you can downgrade to the qemu6 or 
qemu70 packages. These versions will not cause this panic.

Cheers,
Mitchell

> cpuid = 0
> time = 1
> KDB: stack backtrace:
> db_trace_self() at db_trace_self
> db_trace_self_wrapper() at db_trace_self_wrapper+0x38
> kdb_backtrace() at kdb_backtrace+0x2c
> vpanic() at vpanic+0x126
> panic() at panic+0x2a
> fill_elf_hwcap() at fill_elf_hwcap+0x220
> mi_startup() at mi_startup+0x1d2
> va() at va+0x7e
> KDB: enter: panic
> [ thread pid 0 tid 0 ]
> Stopped at      kdb_enter+0x4a: sd      zero,0(s1)
> db>
> 
> yikes.
>