=== PATCHED KERNEL (#1) TEST: RW mount of corrupted HAMMER2 image ===
Kernel: DragonFly 6.5-DEVELOPMENT #1: Thu Jul  9 20:29:43 UTC 2026

Serial console output after mount_hammer2 /dev/vn0 /mnt/h2test (RW):
---
hammer2_mount: devstr="/dev/vn0@DATA"
hammer2_mount: device="/dev/vn0" label="DATA" rdonly=0
hammer2_ondisk: "/dev/vn0" zone=0 id=0 offset=0x0 size=0x20000000
hammer2_mount: "/dev/vn0": no recovery needed
hammer2: Non-inode chain type 3 under super-root, skipping    <-- FIX FIRED, loop advanced
Non inode chain type 3 under super-root                        <-- hammer2_update_pmps (sibling)
HAMMER2: VOLDATA DUMP
HAMMER2: INITIATE SPANs                                        <-- mount proceeded PAST fixup_pfses
kdmsg: iocom_un_init: shitcanning unresponsive pipe
---

Guest responsiveness check:
  $ ssh dfbsd 'uptime'
  8:36PM  up 4 mins, 0 users, load averages: 0.01, 0.03, 0.00
  (ssh responsive, load avg 0.01 = NO CPU spinning, NO infinite loop)

=== CONTRAST: BASELINE (#0) unpatched kernel ===
Serial log stops at: "hammer2_mount: "/dev/vn0": no recovery needed"
  (SILENCE = infinite loop in hammer2_fixup_pfses)
Guest completely unresponsive (ssh times out, load avg 1.59+)