public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: TW <dalzot@gmail.com>
To: stable@vger.kernel.org
Cc: regressions@lists.linux.dev
Subject: Scsi_bus_resume+0x0/0x90 returns -5 when resuming from s3 sleep
Date: Wed, 26 Jul 2023 05:54:34 -0600	[thread overview]
Message-ID: <0e272abe-292d-d58f-cf80-55868e793abc@gmail.com> (raw)

I have been having issues with the 6.x series of kernels resuming from 
suspend with one of my drives. Far as I can tell it has trouble with the 
cache on the drive when coming out of s3 sleep. Tried a few different 
distros (Manjaro, OpenMandriva Rome, EndeavourOS) all that give the same 
error message. It appears to work fine on the 5.15 kernel just fine however.


This is the error or errors that I have been getting and assume has been 
holding up the system from resuming from suspend.
Jul 20 04:13:41 rageworks kernel: ata10.00: device reported invalid CHS 
sector 0
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: [sdc] Start/Stop Unit 
failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: [sdc] Sense Key : Illegal 
Request [current]
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: [sdc] Add. Sense: 
Unaligned write command
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: PM: dpm_run_callback(): 
scsi_bus_resume+0x0/0x90 returns -5
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: PM: failed to resume 
async: error -5

The full suspend log.
Jul 20 04:12:50 rageworks systemd-logind[869]: The system will suspend now!
Jul 20 04:12:50 rageworks ModemManager[902]: <info> 
[sleep-monitor-systemd] system is about to suspend
Jul 20 04:12:50 rageworks NetworkManager[894]: <info> [1689847970.4923] 
manager: sleep: sleep requested (sleeping: no enabled: yes)
Jul 20 04:12:50 rageworks NetworkManager[894]: <info> [1689847970.4924] 
manager: NetworkManager state is now ASLEEP
Jul 20 04:12:50 rageworks NetworkManager[894]: <info> [1689847970.4926] 
device (enp9s0): state change: activated -> deactivating (reason 
'sleeping', sys-iface-state: 'managed')
Jul 20 04:12:50 rageworks dbus-daemon[866]: [system] Activating via 
systemd: service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' 
(uid=0 pid=894 comm="/usr/bin/NetworkManager --no-daemon")
Jul 20 04:12:50 rageworks systemd[1]: Starting Network Manager Script 
Dispatcher Service...
Jul 20 04:12:50 rageworks dbus-daemon[866]: [system] Successfully 
activated service 'org.freedesktop.nm_dispatcher'
Jul 20 04:12:50 rageworks systemd[1]: Started Network Manager Script 
Dispatcher Service.
Jul 20 04:12:50 rageworks NetworkManager[894]: <info> [1689847970.6544] 
device (enp9s0): state change: deactivating -> disconnected (reason 
'sleeping', sys-iface-state: 'managed')
Jul 20 04:12:50 rageworks avahi-daemon[864]: Withdrawing address record 
for fe80::881:c55d:1583:20f5 on enp9s0.
Jul 20 04:12:50 rageworks avahi-daemon[864]: Leaving mDNS multicast 
group on interface enp9s0.IPv6 with address fe80::881:c55d:1583:20f5.
Jul 20 04:12:50 rageworks avahi-daemon[864]: Interface enp9s0.IPv6 no 
longer relevant for mDNS.
Jul 20 04:12:50 rageworks NetworkManager[894]: <info> [1689847970.6726] 
dhcp4 (enp9s0): canceled DHCP transaction
Jul 20 04:12:50 rageworks NetworkManager[894]: <info> [1689847970.6726] 
dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
Jul 20 04:12:50 rageworks NetworkManager[894]: <info> [1689847970.6727] 
dhcp4 (enp9s0): state changed no lease
Jul 20 04:12:50 rageworks avahi-daemon[864]: Withdrawing address record 
for 192.168.1.3 on enp9s0.
Jul 20 04:12:50 rageworks avahi-daemon[864]: Leaving mDNS multicast 
group on interface enp9s0.IPv4 with address 192.168.1.3.
Jul 20 04:12:50 rageworks avahi-daemon[864]: Interface enp9s0.IPv4 no 
longer relevant for mDNS.
Jul 20 04:12:50 rageworks NetworkManager[894]: <info> [1689847970.7576] 
device (enp9s0): state change: disconnected -> unmanaged (reason 
'sleeping', sys-iface-state: 'managed')
Jul 20 04:12:50 rageworks kernel: r8169 0000:09:00.0 enp9s0: Link is Down
Jul 20 04:12:50 rageworks systemd[1]: Reached target Sleep.
Jul 20 04:12:50 rageworks systemd[1]: Starting NVIDIA system suspend 
actions...
Jul 20 04:12:50 rageworks suspend[2051]: nvidia-suspend.service
Jul 20 04:12:50 rageworks logger[2051]: <13>Jul 20 04:12:50 suspend: 
nvidia-suspend.service
Jul 20 04:12:51 rageworks systemd[1]: nvidia-suspend.service: 
Deactivated successfully.
Jul 20 04:12:51 rageworks systemd[1]: Finished NVIDIA system suspend 
actions.
Jul 20 04:12:51 rageworks systemd[1]: Starting System Suspend...
Jul 20 04:12:51 rageworks systemd-sleep[2059]: Entering sleep state 
'suspend'...
Jul 20 04:12:51 rageworks kernel: PM: suspend entry (deep)
Jul 20 04:13:41 rageworks kernel: Filesystems sync: 0.284 seconds
Jul 20 04:13:41 rageworks kernel: Freezing user space processes
Jul 20 04:13:41 rageworks kernel: Freezing user space processes 
completed (elapsed 0.001 seconds)
Jul 20 04:13:41 rageworks kernel: OOM killer disabled.
Jul 20 04:13:41 rageworks kernel: Freezing remaining freezable tasks
Jul 20 04:13:41 rageworks kernel: Freezing remaining freezable tasks 
completed (elapsed 0.001 seconds)
Jul 20 04:13:41 rageworks kernel: printk: Suspending console(s) (use 
no_console_suspend to debug)
Jul 20 04:13:41 rageworks kernel: serial 00:05: disabled
Jul 20 04:13:41 rageworks kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 20 04:13:41 rageworks kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: [sdc] Synchronizing SCSI cache
Jul 20 04:13:41 rageworks kernel: sd 1:0:0:0: [sdb] Stopping disk
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: [sdc] Stopping disk
Jul 20 04:13:41 rageworks kernel: sd 0:0:0:0: [sda] Stopping disk
Jul 20 04:13:41 rageworks kernel: ACPI: PM: Preparing to enter system 
sleep state S3
Jul 20 04:13:41 rageworks kernel: ACPI: PM: Saving platform NVS memory
Jul 20 04:13:41 rageworks kernel: Disabling non-boot CPUs ...
Jul 20 04:13:41 rageworks kernel: smpboot: CPU 1 is now offline
Jul 20 04:13:41 rageworks kernel: smpboot: CPU 2 is now offline
Jul 20 04:13:41 rageworks kernel: smpboot: CPU 3 is now offline
Jul 20 04:13:41 rageworks kernel: ACPI: PM: Low-level resume complete
Jul 20 04:13:41 rageworks kernel: ACPI: PM: Restoring platform NVS memory
Jul 20 04:13:41 rageworks kernel: Enabling non-boot CPUs ...
Jul 20 04:13:41 rageworks kernel: x86: Booting SMP configuration:
Jul 20 04:13:41 rageworks kernel: smpboot: Booting Node 0 Processor 1 
APIC 0x1
Jul 20 04:13:41 rageworks kernel: microcode: CPU1: patch_level=0x08101016
Jul 20 04:13:41 rageworks kernel: CPU1 is up
Jul 20 04:13:41 rageworks kernel: smpboot: Booting Node 0 Processor 2 
APIC 0x2
Jul 20 04:13:41 rageworks kernel: microcode: CPU2: patch_level=0x08101016
Jul 20 04:13:41 rageworks kernel: CPU2 is up
Jul 20 04:13:41 rageworks kernel: smpboot: Booting Node 0 Processor 3 
APIC 0x3
Jul 20 04:13:41 rageworks kernel: microcode: CPU3: patch_level=0x08101016
Jul 20 04:13:41 rageworks kernel: CPU3 is up
Jul 20 04:13:41 rageworks kernel: ACPI: PM: Waking up from system sleep 
state S3
Jul 20 04:13:41 rageworks kernel: xhci_hcd 0000:02:00.0: xHC error in 
resume, USBSTS 0x401, Reinit
Jul 20 04:13:41 rageworks kernel: usb usb1: root hub lost power or was reset
Jul 20 04:13:41 rageworks kernel: usb usb2: root hub lost power or was reset
Jul 20 04:13:41 rageworks kernel: serial 00:05: activated
Jul 20 04:13:41 rageworks kernel: sd 0:0:0:0: [sda] Starting disk
Jul 20 04:13:41 rageworks kernel: sd 1:0:0:0: [sdb] Starting disk
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: [sdc] Starting disk
Jul 20 04:13:41 rageworks kernel: ata5: SATA link down (SStatus 0 
SControl 330)
Jul 20 04:13:41 rageworks kernel: ata9: SATA link down (SStatus 0 
SControl 300)
Jul 20 04:13:41 rageworks kernel: ata6: SATA link down (SStatus 0 
SControl 330)
Jul 20 04:13:41 rageworks kernel: usb 1-7: reset full-speed USB device 
number 2 using xhci_hcd
Jul 20 04:13:41 rageworks kernel: usb 1-10: reset full-speed USB device 
number 4 using xhci_hcd
Jul 20 04:13:41 rageworks kernel: usb 1-8: reset full-speed USB device 
number 3 using xhci_hcd
Jul 20 04:13:41 rageworks kernel: ata2: found unknown device (class 0)
Jul 20 04:13:41 rageworks kernel: ata1: found unknown device (class 0)
Jul 20 04:13:41 rageworks kernel: ata10: found unknown device (class 0)
Jul 20 04:13:41 rageworks kernel: ata2: SATA link up 6.0 Gbps (SStatus 
133 SControl 300)
Jul 20 04:13:41 rageworks kernel: ata2.00: configured for UDMA/133
Jul 20 04:13:41 rageworks kernel: ata1: SATA link up 6.0 Gbps (SStatus 
133 SControl 300)
Jul 20 04:13:41 rageworks kernel: ata1.00: configured for UDMA/133
Jul 20 04:13:41 rageworks kernel: ata10: SATA link up 6.0 Gbps (SStatus 
133 SControl 300)
Jul 20 04:13:41 rageworks kernel: ata10.00: configured for UDMA/133
Jul 20 04:13:41 rageworks kernel: ata10: SATA link up 6.0 Gbps (SStatus 
133 SControl 300)
Jul 20 04:13:41 rageworks kernel: ata10.00: configured for UDMA/133
Jul 20 04:13:41 rageworks kernel: ata10.00: device reported invalid CHS 
sector 0
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: [sdc] Start/Stop Unit 
failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: [sdc] Sense Key : Illegal 
Request [current]
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: [sdc] Add. Sense: 
Unaligned write command
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: PM: dpm_run_callback(): 
scsi_bus_resume+0x0/0x90 returns -5
Jul 20 04:13:41 rageworks kernel: sd 9:0:0:0: PM: failed to resume 
async: error -5
Jul 20 04:13:41 rageworks kernel: OOM killer enabled.
Jul 20 04:13:41 rageworks kernel: Restarting tasks ... done.
Jul 20 04:13:41 rageworks kernel: random: crng reseeded on system resumption
Jul 20 04:13:41 rageworks kernel: PM: suspend exit
Jul 20 04:13:41 rageworks rtkit-daemon[1349]: The canary thread is 
apparently starving. Taking action.
Jul 20 04:13:41 rageworks systemd-sleep[2059]: System returned from 
sleep state.
Jul 20 04:13:41 rageworks rtkit-daemon[1349]: Demoting known real-time 
threads.
Jul 20 04:13:41 rageworks systemd[1]: NetworkManager-dispatcher.service: 
Deactivated successfully.
Jul 20 04:13:41 rageworks rtkit-daemon[1349]: Successfully demoted 
thread 1597 of process 1342.
Jul 20 04:13:41 rageworks rtkit-daemon[1349]: Successfully demoted 
thread 1342 of process 1342.
Jul 20 04:13:41 rageworks rtkit-daemon[1349]: Demoted 2 threads.
Jul 20 04:13:42 rageworks systemd[1]: systemd-suspend.service: 
Deactivated successfully.
Jul 20 04:13:42 rageworks systemd[1]: Finished System Suspend.
Jul 20 04:13:42 rageworks systemd[1]: Stopped target Sleep.
Jul 20 04:13:42 rageworks systemd[1]: Reached target Suspend.
Jul 20 04:13:42 rageworks systemd[1]: Stopped target Suspend.
Jul 20 04:13:42 rageworks systemd-logind[869]: Operation 'sleep' finished.


Thanks

             reply	other threads:[~2023-07-26 11:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 11:54 TW [this message]
2023-07-26 13:47 ` Scsi_bus_resume+0x0/0x90 returns -5 when resuming from s3 sleep Thorsten Leemhuis
2023-07-26 23:39   ` Damien Le Moal
2023-07-27 10:06     ` TW
2023-07-27 10:22       ` TW
2023-07-27 10:25         ` Damien Le Moal
2023-07-27 10:27         ` Damien Le Moal
2023-07-27 12:25           ` TW
2023-07-28  2:33             ` Damien Le Moal
2023-07-28  2:49               ` TW
2023-07-28  4:09                 ` Damien Le Moal
2023-07-31  0:41                 ` Damien Le Moal
2023-07-31  3:47                   ` TW
2023-07-27 10:24       ` Damien Le Moal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0e272abe-292d-d58f-cf80-55868e793abc@gmail.com \
    --to=dalzot@gmail.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox