> This allows me to use bluetooth again after the assertwaitok() cleanup.
While this patch has been shown to have some issues and may be a
different problem, this is a "me too" regarding bluetooth issues.
At some point between the September 20th and October 3rd amd64
snapshots, activating bluetooth on my Asus Eee PC 1005PE netbook
causes a repeatable kernel panic.
panic: assertwaitok: non-zero mutex count: 1
Stopped at Debugger+0x5: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS
PANIC! IF RUNNING SMP, USE 'mach ddbcpu <#>' AND 'trace' ON OTHER
PROCESSORS, TOO. DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING
THAT INFORMATION!
ddb{1}> trace
Debugger() at Debugger+0x5
panic() at panic+0xe4
assertwaitok() at assertwaitok+0x4e
malloc() at malloc+0x3c2
uhci_device_setintr() at uhci_device_setintr+0x8c
usbd_setup_pipe() at usbd_setup_pipe+0x9d
usbd_open_pipe_ival() at usbd_open_pipe_ival+0x9e
usbd_open_pipe_intr() at usbd_open_pipe_intr+0x43
ubt_enable() at ubt_enable+0xcb
hci_enable() at hci_enable+0xc9
hci_ioctl() at hci_ioctl+0x6ab
hci_usrreq() at hci_usrreq+0x124
sys_ioctl() at sys_ioctl+0x111
syscall() at syscall+0x235
--- syscall (number 54) ---
end of kernel
end trace frame: 0x7f7ffffe3776, count: -14
0x20a7c8daa:
I have opened PR #6480 with the details.
Benny
--
"Because you have arms like noodles, while I am vigorous and
burly." -- Hodgins, "Bones"
