⬢ DragonFlyBSD Kernel Audit
DF-4171 / env.txt
← back to finding ↓ download raw
# Guest environment (verify run, 2026-10-15)
# captured: dfbsd-qemu/vm.sh (guest up for the whole run; left up and clean)

$ uname -a
DragonFly dfbsd 6.5-DEVELOPMENT DragonFly 6.5-DEVELOPMENT #0: Thu Jul  2 06:02:54 UTC 2026  root@dfbsd:/usr/obj/usr/src/sys/X86_64_GENERIC  x86_64

$ sysctl -n kern.osrelease kern.osrevision
6.5-DEVELOPMENT
600519

$ md5 /usr/src/sys/dev/drm/amd/powerplay/hwmgr/smu8_hwmgr.c
a0cb59b723434a78e88bf0580d5a5508
# == repo sys/dev/drm/amd/powerplay/hwmgr/smu8_hwmgr.c (verified before AND after
#    the run: the guest /usr/src tree is pristine; fix.diff was never applied there)

$ pciconf -lv | grep -c "vendor=.0x1002"
0
$ ls /dev/dri
ls: /dev/dri: No such file or directory
# -> NO AMD/ATI PCI device, no DRM node: the amdgpu/smu8 powerplay stack can never
#    probe in this guest; the in-kernel defect path is ASIC-gated (verbatim-rig
#    evidence class per DF-4165/4247/4388/4396).

$ cc --version | head -1
cc 8.3 [DragonFly] Release/2019-02-22

$ grep -n mc_err /usr/include/machine/ucontext.h
69:	__register_t	mc_err;
# -> the rig's fault classifier reads the x86 #PF error code (read vs write bit)
#    from the DragonFly ucontext.

$ ls /root/pack4169 /root/pack4171
# -> both packs' rigs built and run in this same guest session (same evidence run)