[Bug 283285] Kernel panic at boot on Intel Atom C3758 w/ QAT module

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283285

Mateusz Guzik <mjg@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mjg@FreeBSD.org

--- Comment #6 from Mateusz Guzik <mjg@FreeBSD.org> ---
The panic stems from issuing a path lookup before vfs is initialized.

Interestingly firmware code does try to handle it (see firmware_mountroot()),
but debug shows this only executes *after* qat load attempt.

Here is what debug says about it:
qat0: <Intel c3xxx QuickAssist> mem 0x81600000-0x8163ffff,0x81640000-0x8167ffff
at device 0.0 on pci1
firmware_get_flags: no rootvnode
qat0: Failed to load UOF FW qat_c3xxx_fw
qat0: Failed to load acceleration FW
qat0: Resetting device qat_dev0
device_attach: qat0 attach returned 14
qat0: <Intel c3xxx QuickAssist> mem 0x81600000-0x8163ffff,0x81640000-0x8167ffff
at device 0.0 on pci1
firmware_get_flags: no rootvnode ### FAILED LOAD HERE
qat0: Failed to load UOF FW qat_c3xxx_fw
qat0: Failed to load acceleration FW
qat0: Resetting device qat_dev0
device_attach: qat0 attach returned 14
Trying to mount root from
zfs:pfSense/ROOT/default_20250409154013_20250411211410 []...
uhub0: 8 ports with 8 removable, self powered
firmware_mountroot: queueing set_rootvnode
set_rootvnode: running ### attempting to sort it out here

Since firmware loading is deferred to a taskqueue, I'm going to patch it up to
wait for fs to become available.

-- 
You are receiving this mail because:
You are the assignee for the bug.