# DF-4895 patched-kernel run — 2026-09-24, same guest, fix.diff applied
# (cd /usr/src && git apply fix.diff && make -j6 quickkernel KERNCONF=X86_64_GENERIC
#  && make installkernel KERNCONF=X86_64_GENERIC), rebooted.
# /boot/kernel/kernel mtime Sep 24 20:32, md5 29a0c51c2e9202a7b626b3416d39
# (uname version string is stale from quickkernel's cached vers.c; the
#  installed/running binary is the 20:32 build.)

[setup]
  SANITY: 32KB roundtrip OK
== [1] vinum stop -f d2 (daemon closes vp) ==
== [2] poke states up (vp stays NULL) ==
== [3] THE WRITE (patched: dev_dstrategy via cdev) ==
32768 bytes transferred in 0.000632 secs (51812849 bytes/sec)     <-- NO PANIC
== [4] did second phase physically land on the down-vp drive? ==
  md1s0 @425 (s1 block):  cc cc cc cc ...   <- landed
  md1s0 @4521 (s2 block): cc cc cc cc ...   <- landed
== [5] full roundtrip still correct ==
ROUNDTRIP OK
PATCHED_RUN_COMPLETE

# Baseline (unpatched) same steps: Fatal trap 12, vn_strategy+0x38,
#   fault address 0x5c, current process = dd, guest dead (panic.txt).
# Patched: identical trigger completes; second-phase data reaches the
#   raw device through the cdev route (proving the fixed launch path is
#   exercised, not merely skipped); normal RAID-5 operation intact.
# Caveat: clean shutdown of the patched guest after this deliberately
#   corrupted administrative state (stopped drive, poked states) needed
#   the force-kill path in vm.sh reset; same as baseline resets.  No
#   panic signature on the serial console (vs. baseline's Fatal trap 12).