On Sun, 21 Aug 2022 at 22:26, Matthew Dharm <mdharm-usb@xxxxxxxxxxxxxxxxxx> wrote: > > The next level of deeper power savings would be a system-wide suspend > / resume, which we've already discussed and is a path which is already > handled (and also different from the original scenario you described). > I tried a suspend / resume cycle. 1) The laptop suspends in that the screen blanks and the power LED fades in/out as an indicator of suspend mode. 2) Power to the USB device is powered on while suspended. (LED light on USB device remains on during suspend.) 3) I can remove and reinsert the USB during suspend and it still resumes ok. 4) On exit from suspend everything looks to work ok. 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. 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: CMD <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 <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. <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 So, it is attempting to recover, but the recovery fails. What is error -110 and err -19 ? Are there any "quirks" that I could try enabling in relation to reset problems? Kind Regards James
