⬢ DragonFlyBSD Kernel Audit
DF-3836 / env.txt
← back to finding ↓ download raw
Guest: DragonFly dfbsd 6.5-DEVELOPMENT #0: Thu Jul 2 06:02:54 UTC 2026 (X86_64_GENERIC, x86_64)
Kernel: stock X86_64_GENERIC — bwn compiled in (kldstat -v: "62 siba_bwn/bwn"); trm NOT in GENERIC (module-only, sys/dev/disk/trm/Makefile KMOD=trm).

PCI inventory (pciconf -l, 7 devices total):
  hostb0@pci0:0:0:0  chip=0x12378086 (Intel i440FX)
  isab1@pci0:0:1:0   chip=0x70008086 (PIIX3 ISA)
  atapci0@pci0:0:1:1 chip=0x70108086 (PIIX3 IDE)
  none0@pci0:0:1:3   chip=0x71138086 (PIIX4 power mgmt)
  vgapci0@pci0:2:0   chip=0x11111234 (QEMU VGA)
  virtio_pci0        chip=0x10001af4 (virtio-net)
  virtio_pci1        chip=0x10011af4 (virtio-blk)

=> NO Tekram PCI device (vendor 0x1DE1 / PCI_DEVICEID_TRMS1040 0x03911DE1 / TRMS2080 0x03921DE1)
=> NO Broadcom wireless PCI device (vendor 0x14E4) — bwn never attaches
=> trm(4) cannot attach: probe() matches only the two Tekram device IDs (sys/dev/disk/trm/trm.c:3677-3688)

Conclusion: every DF-3830..DF-3836 code path is hardware-gated and cannot be exercised on this guest;
verification is source-level (line-cited traces in each VERDICT.md).