[email protected] (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes:
> [ 10753.947813] DEBUG: module: unload requested for 'usbverbose' (TRUE)
> [ 10753.947813] DEBUG: module: unloaded module `usbverbose'
>After, all requests returns FALSE :
> [ 10787.090445] DEBUG: module: unload requested for 'usbverbose' (FALSE)
> Another question : what is the signification of " [ 10767.042803]
>DEBUG: module: plist load returned error 2 for
> `/stand/amd64/9.0/modules/usbverbose/usbverbose.kmod'" ? 2 for ENOENT ?
The module loader also checks for a plist file with optional module parameters.
It logs 2 (ENOENT) because there is no such plist file.
Loading the usbverbose manually by listing it in /etc/modules.conf
or using a kernel with the usbverbose module compiled in would be a
workaround.
Your panic message lists PID 160 as the failing process. Was that
the bacula process or something else ?
With
sysctl -w ddb.onpanic=1
you can make the system enter DDB when the panic occurs. You can then
identify the process that caused the panic.
--
--
Michael van Elst
Internet: [email protected]
"A potential Snark may lurk in every tree."
