On 22.08.22 00:56, James Dutton wrote: > I see these messages in the syslog during the suspend/resume cycle: > <6>1 2022-08-21T23:18:57+01:00 nvme2 kernel - - - [ 1127.688557] usb > 4-2: reset SuperSpeed USB device number 2 using xhci_hcd > <4>1 2022-08-21T23:18:57+01:00 nvme2 kernel - - - [ 1127.782252] usb > 4-2: Enable of device-initiated U1 failed. > <4>1 2022-08-21T23:18:57+01:00 nvme2 kernel - - - [ 1127.784263] usb > 4-2: Enable of device-initiated U2 failed. > > Is U1/U2 failing a problem that could maybe be causing the problems I have seen? > The error is in the logs, but the resume works, and the disk is accessible. That is power management. And for a disk to use only power managementunder the host's control is not a problem. > When the real problem occurs (not during suspend/resume), an extract here: > <6>1 2022-05-04T14:32:53+01:00 nvme2 kernel - - - [20782.100705] sd > 0:0:0:0: [sda] tag#8 uas_eh_abort_handler 0 uas-tag 2 inflight: CM A timeout has happened. > <6>1 2022-05-04T14:32:53+01:00 nvme2 kernel - - - [20782.100707] sd > 0:0:0:0: [sda] tag#8 CDB: Write(10) 2a 00 1c 51 11 20 00 00 20 00 > <6>1 2022-05-04T14:32:53+01:00 nvme2 kernel - - - [20782.115321] scsi > host0: uas_eh_device_reset_handler start At that time the SCSI layer does not know why a timeout has happened, so it starts generic error hanfdling, involving a reset. > <6>1 2022-05-04T14:32:53+01:00 nvme2 kernel - - - [20782.248337] usb > 4-1: reset SuperSpeed USB device number 2 using xhci_hcd > <4>1 2022-05-04T14:32:58+01:00 nvme2 kernel - - - [20787.463620] > xhci_hcd 0000:00:14.0: Trying to add endpoint 0x83 without dropping > it. This should not happen > <3>1 2022-05-04T14:32:58+01:00 nvme2 kernel - - - [20787.463633] usb > 4-1: failed to restore interface 0 altsetting 1 (error=-110) > <6>1 2022-05-04T14:32:58+01:00 nvme2 kernel - - - [20787.471524] scsi > host0: uas_eh_device_reset_handler FAILED err -19 > <6>1 2022-05-04T14:32:58+01:00 nvme2 kernel - - - [20787.471540] sd > 0:0:0:0: Device offlined - not ready after error recovery In this case the kernel does not think that your device has been disconnected. All error handling has failed. It gives up on the device but it is still know to the system. > So, it is attempting to recover, but the recovery fails. > What is error -110 and err -19 ? -19 is ENODEV -110 is ETIMEDOUT Those numbers are to be found in include/uapi/asm-generic/errno-base.h include/uapi/asm-generic/errno.h > Are there any "quirks" that I could try enabling in relation to reset problems? Probably not. Is this log complete? Regards Oliver
