https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286059
Bug ID: 286059
Summary: iwx(4): panic on resume, "iwx0 not locked"
Product: Base System
Version: 15.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: tr...@freebsd.org
When resuming from S3 suspend, the iwx(4) driver (on 15-CURRENT with
https://reviews.freebsd.org/D49759, wouldn't attach otherwise) panics like
this:
panic: lock (sleep mutex) iwx0 not locked @
/usr/home/trasz/git/freebsd-src/sys/dev/iwx/if_iwx.c: 4012
cpuid = 2
time = 1744390217
KDB: stack backtrace:
db_trace_self_rapper () at db_trace_self_urapper+0x2b/frame ßxfffffe00fb36e510
vpanic() at vpanic+0x136/frame 0xfffffe00fb36e640
panic() at panic+0x43/frame 0xfffffe00fb3бeбa0
witness_unlock() at witness_unlock+x154/frame 0xfffffe00fb3бe6d0
_mtx_unlock_flags() at -_mtx_unlock_flags+0x3f/frame ßxfffffe00fb3бe6fĐ
iwx_run_init_mvm_ucode() at iwx_run_init_mvm_ucode+0x82/frame
Oxfffffe00fb36e7el
iux_init_hu() at iux_init_hu+0xlb/frame Bxfffffe00fb36eB80
lux_resume() at iux_resume+0x22/frame Bxfffffe00fb3бeBa0
bus_gener ic_resume_child() at bus_generic_resume_child+0x3d/frame
Axfffffe0@fb36eBc®
pci_resume_child() at pci_resume_child+Bx6b/frame Bxfffffe00fb36eßf0
pci_resume() at pci_resume+0x117/frame Bxfffffe00fb3бe940
bus_gener ic_resume_child() at bus_generic_resume_child+0x3d/frame
0xfffffe00fb36960
bus_gener ic_resume() at bus_generic_resume+0x29/frame Oxfffffe00fb36980
pcib_resume() at pcib_resume+Bxcb/frame 0xfffffe00fb36e9b0
bus_gener ic_resume_child() at bus_gener ic_resume_child+0x3d/frame
xfffffeD0fb359d0
pci_resume_child) at pci_resume_child+0x6b/frame 0xfffffe00fb36ea00
pci_resume() at pci_resume+0x49/frame 0xfffffe00fb36ea50
bus_generic_resume_child() at bus_generic_resume_child+0x3d/frame
Bxfffffe00fb3бea70
bus_gener ic_resume() at bus_generic_resume+0x29/frame 0xfffffe0@fb36ea90
bus_gener ic_resume_child) at bus_generic_resume_child+0x3d/frame
Oxfffffeu@fb36eabl
bus_generic_resume() at bus_generic_resume+0x29/frame 0xfffffe00fb36ead®
bus_gener ic_resume_child() at bus_generic_resume_child+0x3d/frame
0xfffffe00fb36eafO
bus_generic_resume() at bus_generic_resume+0x29/frame 0xfffffe00fb35eb10
bus_gener ic_resume_child() at bus_generic_resume_child+0x3d/frame
Oxfffffe00fb36eb30
root_resume() at root_resume+0x29/frame 0xfffffe00fb36eb50
acpi_EnterSleepState() at acpi_EnterSleepState+0x7d2/frame 0xfffffe00fb36ebd0
acpi_AckSleepState() at acpi_AckSleepState+0x131/frame @xfffffe00fb36ec00
devfs_ioctl() at devfs_ioctl+0xd1/frame Axfffffe00fb36ec50
vn_locti( at vn_ioctl+0xb6/frame @xfffffe00fb3бecc0
devfs_ioctl_f() at devfs_ioctl_f+Bxle/frame Bxfffffe00fb36ece0
kern_ioctl() at kern_ioctl+0x286/frame 0xfffffe00fb36ed40
sys_ioctl() at sys_ioctl+0x12f/frame 0xfffffe00fb3бeeß0
amd64_syscall() at amd64_syscal 1+0x15a/frame 0xfffffe00fb36ef30
(Note the traceback is OCR-ed.)
When it panics, the system is _very_ slow, you can see characters being output
one by one. Crashdumps don't work either; interrupt problem? The panic
doesn't happen if if_iwx(4) is not loaded.
--
You are receiving this mail because:
You are the assignee for the bug.
