[Bug 289930] Booting FreeBSD 16-CURRENT on riscv64 with QEMU hangs indefinitely

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 30 Sep 2025 22:30:03 UTC 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289930

            Bug ID: 289930
           Summary: Booting FreeBSD 16-CURRENT on riscv64 with QEMU hangs
                    indefinitely
           Product: Base System
           Version: 16.0-CURRENT
          Hardware: riscv
                OS: Any
            Status: New
          Keywords: crash, regression
          Severity: Affects Only Me
          Priority: ---
         Component: riscv
          Assignee: Andrew@FreeBSD.org
          Reporter: me@svmhdvn.name
                CC: br@FreeBSD.org, riscv@FreeBSD.org, testing@FreeBSD.org

Created attachment 264179
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=264179&action=edit
boot log

Booting FreeBSD 16-CURRENT on riscv64 with QEMU causes an indefinite hang here:


---<<BOOT>>---
[...]
vtblk0: 32772MB (67117123 512 byte sectors)
virtio_pci2: <VirtIO PCI (legacy) Block adapter> port 0x1100-0x117f mem
0x40010000-0x40010fff,0x40014000-0x40017fff irq 22 at device 3.0 on pci0
vtblk1: <VirtIO Block Adapter> on virtio_pci2 <---- HANGS HERE


To reproduce this, I used Bricoler with qemu-system-riscv64 10.1.0 and attached
the boot log in this bug:

bricoler run freebsd-src-regression-suite \
  --param freebsd-src:url=/usr/src \
  --param freebsd-src:branch= \
  --param freebsd-src-build:machine=riscv/riscv64 \
  --param freebsd-src-regression-suite:hypervisor=qemu \
  --param freebsd-src-regression-suite:memory=4096 \
  --param freebsd-src-regression-suite:ncpus=2 \
  --param freebsd-src-regression-suite:parallelism=1 \
  --param freebsd-src-regression-suite:tests='bin/ls' \
  --param freebsd-src-regression-suite-vm-image:packages=


@andrew I've bisected this to your commit
https://cgit.freebsd.org/src/commit/?id=ad17789a8569c6712c6d789232df2703a21088a4
(virtio: Remove the unused poll method). It boots successfully on this commit's
parent, and hangs at this commit and current HEAD at the time of writing.
Please triage as necessary.

-- 
You are receiving this mail because:
You are on the CC list for the bug.