Re: Kernel panic with usbverbose (?)

[BERTRAND Joël <joel.bertrand%systella.fr@localhost>]

Michael van Elst a écrit :
> joel.bertrand%systella.fr@localhost (=?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 ?

	No. This PID is a kernel thread (ioflush). This morning, I have seen
several panics in ioflush.

> 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.

	I have rebuilt a kernel (9 oct 2020) and even with kern.module.verbose
= 1, I haven't see any message about usbverbose load and unload.

	That's being said, I've got some other messages on console :
[   481.957605] re0: watchdog timeout
[   494.632228] S2C1: *** Connection Error, status=24, logout=-1, state=3
[   503.975605] re0: watchdog timeout
[   519.481139] S2C1: *** Connection Error, status=18, logout=2, state=6
[   525.663327] S2C1: ccb_timeout: num=1 total=1 disp=5
[   525.663327] S2C1: *** Connection Error, status=24, logout=2, state=6
[   525.683334] S2C1: ccb_timeout: num=1 total=1 disp=5
[   525.683334] S2C1: *** Connection Error, status=24, logout=2, state=6
[   525.683334] S2C1: ccb_timeout: num=1 total=1 disp=5
[   525.683334] S2C1: *** Connection Error, status=24, logout=2, state=6
[   526.683688] S2C1: ccb_timeout: num=1 total=1 disp=5
[   526.683688] S2C1: *** Connection Error, status=24, logout=2, state=6
[   526.683688] S2C1: ccb_timeout: num=1 total=1 disp=5
[   526.683688] S2C1: *** Connection Error, status=24, logout=2, state=6
[   526.683688] S2C1: ccb_timeout: num=1 total=1 disp=5
[   526.683688] S2C1: *** Connection Error, status=24, logout=2, state=6
[   528.644381] S2C1: ccb_timeout: num=1 total=1 disp=3
[   528.644381] S2C1: *** Connection Error, status=24, logout=2, state=6
[   530.645090] S2C1: ccb_timeout: num=1 total=1 disp=3
[   530.645090] S2C1: *** Connection Error, status=24, logout=2, state=6
[   531.995569] re0: watchdog timeout
[   532.495745] S2C1: Write failed sock 0xffffa6bf802ca940 (ret: 32,
req: 65584, resid: 16234)
[   532.495745] S2C1: *** Connection Error, status=18, logout=-1, state=6
[   534.506456] S2C1: Resend ccb 0xffffd88020ad1d00 (37) - updating
CmdSN old 92, new 95
[   534.506456] S2C1: Resend ccb 0xffffd88020ad1b88 (37) - updating
CmdSN old 93, new 96
[   534.506456] S2C1: Resend ccb 0xffffd88020ad1a10 (37) - updating
CmdSN old 94, new 97
[   534.506456] S2C1: Connection ReCreated successfully - status 0
[   542.009111] re0: watchdog timeout
[   553.023009] re0: watchdog timeout
[   554.533544] S2C1: *** Connection Error, status=24, logout=-1, state=3
[   561.055852] S2C1: *** Connection Error, status=18, logout=2, state=6
[   563.116581] S2C1: Resend ccb 0xffffd88020ad0870 (37) - updating
CmdSN old 104, new 114
[   563.116581] S2C1: Resend ccb 0xffffd88020ad06f8 (37) - updating
CmdSN old 105, new 115
[   563.116581] S2C1: Resend ccb 0xffffd88020ad0580 (37) - updating
CmdSN old 106, new 116
[   563.116581] S2C1: Resend ccb 0xffffd88020ad0408 (37) - updating
CmdSN old 107, new 117
[   563.116581] S2C1: Resend ccb 0xffffd88020ad0290 (37) - updating
CmdSN old 108, new 118
[   563.116581] S2C1: Resend ccb 0xffffd88020ad3018 (37) - updating
CmdSN old 109, new 119
[   563.116581] S2C1: Resend ccb 0xffffd88020ad2ea0 (37) - updating
CmdSN old 110, new 120
[   563.116581] S2C1: Resend ccb 0xffffd88020ad2d28 (37) - updating
CmdSN old 111, new 121
[   563.116581] S2C1: Resend ccb 0xffffd88020ad2bb0 (37) - updating
CmdSN old 112, new 122
[   563.116581] S2C1: Resend ccb 0xffffd88020ad25d0 (37) - updating
CmdSN old 113, new 123
[   563.116581] S2C1: Connection ReCreated successfully - status 0
[   574.110473] S2C1: *** Connection Error, status=24, logout=-1, state=3
[   580.042571] re0: watchdog timeout
[   590.056116] S2C1: *** Connection Error, status=24, logout=-1, state=6
[   597.188640] S2C1: Resend ccb 0xffffd88020ad0580 (37) - updating
CmdSN old 116, new 126
[   597.188640] S2C1: Resend ccb 0xffffd88020ad0408 (37) - updating
CmdSN old 117, new 127
[   597.188640] S2C1: Resend ccb 0xffffd88020ad0290 (37) - updating
CmdSN old 118, new 128
[   597.188640] S2C1: Resend ccb 0xffffd88020ad3018 (37) - updating
CmdSN old 119, new 129
[   597.188640] S2C1: Resend ccb 0xffffd88020ad2ea0 (37) - updating
CmdSN old 120, new 130
[   597.188640] S2C1: Resend ccb 0xffffd88020ad2d28 (37) - updating
CmdSN old 121, new 131
[   597.188640] S2C1: Resend ccb 0xffffd88020ad2bb0 (37) - updating
CmdSN old 122, new 132
[   597.188640] S2C1: Resend ccb 0xffffd88020ad25d0 (37) - updating
CmdSN old 123, new 133
[   597.198644] S2C1: Resend ccb 0xffffd88020ad15a8 (37) - updating
CmdSN old 124, new 134
[   597.198644] S2C1: Resend ccb 0xffffd88020ad1430 (37) - updating
CmdSN old 125, new 135
[   597.198644] S2C1: Connection ReCreated successfully - status 0
[   617.205725] S2C1: *** Connection Error, status=24, logout=-1, state=3
[   618.066028] re0: watchdog timeout

re0's MTU is 7418. I have tried some different segment-length (7000,
6000, 5000) and iSCSI was unstable. Now, segment-length is the default
value (1484 if I remember).

	Best regards,

	JKB