⬢ DragonFlyBSD Kernel Audit
DF-2316 / env.txt
← back to finding ↓ download raw
DF-2316 verification environment (QEMU/KVM guest, dfbsd-qemu/vm.sh)
=====================================================================

Guest OS       : DragonFly dfbsd 6.5-DEVELOPMENT x86_64
Kernel (fixed) : DragonFly 6.5-DEVELOPMENT #0: Sun Oct 18 17:35:42 UTC 2026
                 root@dfbsd:/usr/obj/usr/src/sys/PNPH  (fix-validation boot)
Kernel (base)  : same PNPH config; pnpparse.c TU pristine (see below);
                 decisive baseline boots #2 17:09:41 UTC (scenarios 9-26) and
                 the 17:24 UTC boot (scenario 25 panic)
Compiler       : cc 8.3 [DragonFly] Release/2019-02-22
CPUs           : 5 (ncpus; send_ipiq traces show cpu ids 0,2,4)
physmem        : 4257742848 bytes (~4 GB)
debug.debugger_on_panic = 0 (set by prep.sh so the panic prints and reboots
                            instead of dropping into DDB)
kern.bootverbose: not set (0) at run time

Harness kernel : sys/config/PNPH = X86_64_GENERIC + "device pnp_harness";
                 conf/files: bus/isa/pnp.c optional isa (STOCK),
                 bus/isa/pnpparse.c optional pnp_stock_disabled (dropped),
                 bus/isa/pnp_harness.c optional pnp_harness (this rig).
Verbatim gate  : baseline build sha256(pnpparse.c) =
                 4b13638c30fcb3cfae135711d2e4275f500edfc0cb3d35857e777399b25696a3
                 (== pristine audit-tree sys/bus/isa/pnpparse.c; prep.sh refuses
                 to prep anything else)
Fixed build    : same tree + fix.diff applied ->
                 sha256 fde2c7e119d2eba1d0427a7a1a559cc07ae6208150a80b43826a38b6190b32a1
Control device : /dev/pnph0 (root-only 0600), driver by pnp_harness.c
Real parents   : harness drives the REAL isa0 (devclass_find("isa")) children;
                 pnp.c remains the STOCK in-build unit and links against the
                 harness TU (which provides pnp_parse_resources etc.)

Note on crash dumps: the baseline panic dumped 551 MB to the vbd0s1b swap
slice ("Dumping 551 MB ... Dump complete") before wedging in the SMP reboot
path; the guest was then reset with-src for the fix-validation build.