Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: Suspend - waking up takes a while.

  1. #1

    Default Suspend - waking up takes a while.

    Hi.
    I noticed something odd over the last few weeks after having run 15.2 for a few months without issue. After a wake up my PC from Suspend mode I get the session back immediately (wallpaper, open apps etc). But things like -


    • navigation those open apps - like firefox or thunderbird, even PCManFM are frozen
    • the network reconnecting
    • even the system clock updating in the system tray


    takes around 30 seconds. After that everything is fine.

    To be honest I don;t know where to start looking for this odd 'extra delay'. Read the system logs but all greek to me.

    Any ideas what may be wrong or where to start looking?

    System is 16GB RAM, 250GB SSD SATA + 2TB HDD SATA , Asus Z370G motherboard, Nvidia GTX 1050Ti. Running LXDE.

    Thanks.

  2. #2
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,422
    Blog Entries
    1

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by kitman View Post
    Hi.
    I noticed something odd over the last few weeks after having run 15.2 for a few months without issue. After a wake up my PC from Suspend mode I get the session back immediately (wallpaper, open apps etc). But things like -


    • navigation those open apps - like firefox or thunderbird, even PCManFM are frozen
    • the network reconnecting
    • even the system clock updating in the system tray


    takes around 30 seconds. After that everything is fine.

    To be honest I don;t know where to start looking for this odd 'extra delay'. Read the system logs but all greek to me.

    Any ideas what may be wrong or where to start looking?

    System is 16GB RAM, 250GB SSD SATA + 2TB HDD SATA , Asus Z370G motherboard, Nvidia GTX 1050Ti. Running LXDE.

    Thanks.
    Could be caused by 2TB HDD SATA. Suspend and resume times are varying:

    Code:
    erlangen:~ # journalctl -b -u systemd-suspend.service -o short-monotonic  
    -- Logs begin at Wed 2021-02-17 13:00:05 CET, end at Thu 2021-02-25 11:32:05 CET. -- 
    [15472.906102] erlangen systemd[1]: Starting Suspend... 
    [15472.936006] erlangen systemd-sleep[30262]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 
    [15472.938795] erlangen systemd-sleep[30260]: Suspending system... 
    [15475.492448] erlangen systemd-sleep[30260]: System resumed. 
    [15475.502115] erlangen systemd-sleep[30358]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 
    [15475.503106] erlangen systemd[1]: systemd-suspend.service: Succeeded. 
    [15475.503454] erlangen systemd[1]: Finished Suspend. 
    [23558.045931] erlangen systemd[1]: Starting Suspend... 
    [23558.067896] erlangen systemd-sleep[29086]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 
    [23558.069821] erlangen systemd-sleep[29084]: Suspending system... 
    [23559.474336] erlangen systemd-sleep[29084]: System resumed. 
    [23559.478366] erlangen systemd-sleep[29152]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 
    [23559.494563] erlangen systemd[1]: systemd-suspend.service: Succeeded. 
    [23559.494806] erlangen systemd[1]: Finished Suspend. 
    erlangen:~ #
    
    What are your times?
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  3. #3

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by karlmistelberger View Post
    Could be caused by 2TB HDD SATA. Suspend and resume times are varying:


    What are your times?
    This is mine but how do I interpret the results?

    Code:
    asus-roc:/home/chris # journalctl -b -u systemd-suspend.service -o short-monotonic
    -- Logs begin at Thu 2021-02-25 08:31:10 AWST, end at Thu 2021-02-25 19:16:36 AWST. --
    [22853.794174] asus-roc.lan systemd[1]: Starting Suspend...
    [22853.800919] asus-roc.lan systemd-sleep[17569]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
    [22853.801330] asus-roc.lan systemd-sleep[17569]: Suspending system...
    [22858.542093] asus-roc.lan systemd-sleep[17569]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
    [22858.542431] asus-roc.lan systemd[1]: Started Suspend.
    [28026.694687] asus-roc.lan systemd[1]: Starting Suspend...
    [28026.700207] asus-roc.lan systemd-sleep[21581]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
    [28026.700524] asus-roc.lan systemd-sleep[21581]: Suspending system...
    [28029.256582] asus-roc.lan systemd-sleep[21581]: System resumed.
    [28029.259922] asus-roc.lan systemd-sleep[21581]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
    [28029.260581] asus-roc.lan systemd[1]: Started Suspend.
    asus-roc:/home/chris #

  4. #4
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,422
    Blog Entries
    1

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by kitman View Post
    This is mine but how do I interpret the results?

    Code:
    asus-roc:/home/chris # journalctl -b -u systemd-suspend.service -o short-monotonic
    -- Logs begin at Thu 2021-02-25 08:31:10 AWST, end at Thu 2021-02-25 19:16:36 AWST. --
    [22853.794174] asus-roc.lan systemd[1]: Starting Suspend...
    [22853.800919] asus-roc.lan systemd-sleep[17569]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
    [22853.801330] asus-roc.lan systemd-sleep[17569]: Suspending system...
    [22858.542093] asus-roc.lan systemd-sleep[17569]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
    [22858.542431] asus-roc.lan systemd[1]: Started Suspend.
    [28026.694687] asus-roc.lan systemd[1]: Starting Suspend...
    [28026.700207] asus-roc.lan systemd-sleep[21581]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
    [28026.700524] asus-roc.lan systemd-sleep[21581]: Suspending system...
    [28029.256582] asus-roc.lan systemd-sleep[21581]: System resumed.
    [28029.259922] asus-roc.lan systemd-sleep[21581]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
    [28029.260581] asus-roc.lan systemd[1]: Started Suspend.
    asus-roc:/home/chris #
    There is nothing wrong with your suspend/resume. Suspend spins down the HDD. Slow resume could be caused by slow response of HDD. Seems to me your processes are waiting for the drive to spin up. If in doubt show the lines of the journal following 'Started Suspend'.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  5. #5
    Join Date
    Sep 2012
    Posts
    6,313

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by kitman View Post
    To be honest I don;t know where to start looking for this odd 'extra delay'. Read the system logs but all greek to me.
    As delay happens in your desktop session, "journalctl --user -b" immediately after resume may offer some clue.

  6. #6

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by karlmistelberger View Post
    There is nothing wrong with your suspend/resume. Suspend spins down the HDD. Slow resume could be caused by slow response of HDD. Seems to me your processes are waiting for the drive to spin up. If in doubt show the lines of the journal following 'Started Suspend'.
    Thanks Karl, I think you hit the nail on the head about the HDD spinning up. Most of my files that are in use are on /data on this drive so the delay makes sense now.

    Code:
    2021-02-25T15:10:53.549169+08:00 asus-roc kernel: [22861.433592] ata4: link is slow to respond, please be patient (ready=0)
    2021-02-25T15:10:55.770452+08:00 asus-roc kernel: [22863.658885] snd_hdac_bus_update_rirb: 463 callbacks suppressed
    2021-02-25T15:10:55.770487+08:00 asus-roc kernel: [22863.658892] snd_hda_intel 0000:02:00.1: spurious response 0x3:0x0, last cmd=0x4f0700
    2021-02-25T15:10:55.770491+08:00 asus-roc kernel: [22863.658897] snd_hda_intel 0000:02:00.1: spurious response 0x0:0x0, last cmd=0x470700
    2021-02-25T15:10:55.770494+08:00 asus-roc kernel: [22863.658929] snd_hda_intel 0000:02:00.1: spurious response 0x40:0x0, last cmd=0x470700
    2021-02-25T15:10:55.770499+08:00 asus-roc kernel: [22863.658958] snd_hda_intel 0000:02:00.1: spurious response 0x0:0x0, last cmd=0x470700
    2021-02-25T15:10:55.889121+08:00 asus-roc kernel: [22863.774252] e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
    2021-02-25T15:10:55.889150+08:00 asus-roc kernel: [22863.774339] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    2021-02-25T15:10:55.901044+08:00 asus-roc kernel: [22863.786799] bridge0: port 1(eth0) entered blocking state
    2021-02-25T15:10:55.901052+08:00 asus-roc kernel: [22863.786800] bridge0: port 1(eth0) entered disabled state
    2021-02-25T15:10:55.901055+08:00 asus-roc kernel: [22863.786888] device eth0 entered promiscuous mode
    2021-02-25T15:10:55.901056+08:00 asus-roc kernel: [22863.786954] bridge0: port 1(eth0) entered blocking state
    2021-02-25T15:10:55.901057+08:00 asus-roc kernel: [22863.786954] bridge0: port 1(eth0) entered listening state
    2021-02-25T15:10:56.841284+08:00 asus-roc kernel: [22864.729722] snd_hda_intel 0000:02:00.1: spurious response 0x0:0x0, last cmd=0xa20000
    2021-02-25T15:10:56.841318+08:00 asus-roc kernel: [22864.729728] snd_hda_intel 0000:02:00.1: spurious response 0x0:0x0, last cmd=0xa20000
    2021-02-25T15:10:58.241164+08:00 asus-roc kernel: [22866.125662] ata4: COMRESET failed (errno=-16)
    2021-02-25T15:11:03.613162+08:00 asus-roc kernel: [22871.497657] ata4: link is slow to respond, please be patient (ready=0)
    2021-02-25T15:11:08.249135+08:00 asus-roc kernel: [22876.133628] ata4: COMRESET failed (errno=-16)
    2021-02-25T15:11:10.969165+08:00 asus-roc kernel: [22878.853695] bridge0: port 1(eth0) entered learning state
    2021-02-25T15:11:13.573168+08:00 asus-roc kernel: [22881.457699] ata4: link is slow to respond, please be patient (ready=0)
    2021-02-25T15:11:19.101162+08:00 asus-roc kernel: [22886.985694] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    2021-02-25T15:11:19.297136+08:00 asus-roc kernel: [22887.181858] ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    2021-02-25T15:11:19.297164+08:00 asus-roc kernel: [22887.181864] ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    2021-02-25T15:11:19.297167+08:00 asus-roc kernel: [22887.181868] ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    2021-02-25T15:11:19.297170+08:00 asus-roc kernel: [22887.184582] ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    2021-02-25T15:11:19.297173+08:00 asus-roc kernel: [22887.184588] ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    2021-02-25T15:11:19.297175+08:00 asus-roc kernel: [22887.184593] ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    2021-02-25T15:11:19.297196+08:00 asus-roc kernel: [22887.185079] ata4.00: configured for UDMA/133
    2021-02-25T15:11:26.069233+08:00 asus-roc kernel: [22893.957702] bridge0: port 1(eth0) entered forwarding state
    2021-02-25T15:11:26.069271+08:00 asus-roc kernel: [22893.957717] bridge0: topology change detected, propagating
    But I had to get that info directly from the /var/log/messages as yast's Journal Entries would not let me select and display yesterday's messages.


    Quote Originally Posted by arvidjaar
    As delay happens in your desktop session, "journalctl --user -b" immediately after resume may offer some clue.
    Nothing was returned.

    Code:
    chris@asus-roc:~> sudo journalctl --user -b
    [sudo] password for root: 
    No journal files were found.
    -- No entries --
    chris@asus-roc:~>
    I think I need to read more on Journalctl's command line technique's .

    Thanks all.

  7. #7
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,422
    Blog Entries
    1

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by kitman View Post
    Thanks Karl, I think you hit the nail on the head about the HDD spinning up. Most of my files that are in use are on /data on this drive so the delay makes sense now.

    Code:
    2021-02-25T15:10:53.549169+08:00 asus-roc kernel: [22861.433592] ata4: link is slow to respond, please be patient (ready=0)
    2021-02-25T15:10:55.770452+08:00 asus-roc kernel: [22863.658885] snd_hdac_bus_update_rirb: 463 callbacks suppressed
    2021-02-25T15:10:55.770487+08:00 asus-roc kernel: [22863.658892] snd_hda_intel 0000:02:00.1: spurious response 0x3:0x0, last cmd=0x4f0700
    2021-02-25T15:10:55.770491+08:00 asus-roc kernel: [22863.658897] snd_hda_intel 0000:02:00.1: spurious response 0x0:0x0, last cmd=0x470700
    2021-02-25T15:10:55.770494+08:00 asus-roc kernel: [22863.658929] snd_hda_intel 0000:02:00.1: spurious response 0x40:0x0, last cmd=0x470700
    2021-02-25T15:10:55.770499+08:00 asus-roc kernel: [22863.658958] snd_hda_intel 0000:02:00.1: spurious response 0x0:0x0, last cmd=0x470700
    2021-02-25T15:10:55.889121+08:00 asus-roc kernel: [22863.774252] e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
    2021-02-25T15:10:55.889150+08:00 asus-roc kernel: [22863.774339] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    2021-02-25T15:10:55.901044+08:00 asus-roc kernel: [22863.786799] bridge0: port 1(eth0) entered blocking state
    2021-02-25T15:10:55.901052+08:00 asus-roc kernel: [22863.786800] bridge0: port 1(eth0) entered disabled state
    2021-02-25T15:10:55.901055+08:00 asus-roc kernel: [22863.786888] device eth0 entered promiscuous mode
    2021-02-25T15:10:55.901056+08:00 asus-roc kernel: [22863.786954] bridge0: port 1(eth0) entered blocking state
    2021-02-25T15:10:55.901057+08:00 asus-roc kernel: [22863.786954] bridge0: port 1(eth0) entered listening state
    2021-02-25T15:10:56.841284+08:00 asus-roc kernel: [22864.729722] snd_hda_intel 0000:02:00.1: spurious response 0x0:0x0, last cmd=0xa20000
    2021-02-25T15:10:56.841318+08:00 asus-roc kernel: [22864.729728] snd_hda_intel 0000:02:00.1: spurious response 0x0:0x0, last cmd=0xa20000
    2021-02-25T15:10:58.241164+08:00 asus-roc kernel: [22866.125662] ata4: COMRESET failed (errno=-16)
    2021-02-25T15:11:03.613162+08:00 asus-roc kernel: [22871.497657] ata4: link is slow to respond, please be patient (ready=0)
    2021-02-25T15:11:08.249135+08:00 asus-roc kernel: [22876.133628] ata4: COMRESET failed (errno=-16)
    2021-02-25T15:11:10.969165+08:00 asus-roc kernel: [22878.853695] bridge0: port 1(eth0) entered learning state
    2021-02-25T15:11:13.573168+08:00 asus-roc kernel: [22881.457699] ata4: link is slow to respond, please be patient (ready=0)
    2021-02-25T15:11:19.101162+08:00 asus-roc kernel: [22886.985694] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    2021-02-25T15:11:19.297136+08:00 asus-roc kernel: [22887.181858] ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    2021-02-25T15:11:19.297164+08:00 asus-roc kernel: [22887.181864] ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    2021-02-25T15:11:19.297167+08:00 asus-roc kernel: [22887.181868] ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    2021-02-25T15:11:19.297170+08:00 asus-roc kernel: [22887.184582] ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    2021-02-25T15:11:19.297173+08:00 asus-roc kernel: [22887.184588] ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    2021-02-25T15:11:19.297175+08:00 asus-roc kernel: [22887.184593] ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    2021-02-25T15:11:19.297196+08:00 asus-roc kernel: [22887.185079] ata4.00: configured for UDMA/133
    2021-02-25T15:11:26.069233+08:00 asus-roc kernel: [22893.957702] bridge0: port 1(eth0) entered forwarding state
    2021-02-25T15:11:26.069271+08:00 asus-roc kernel: [22893.957717] bridge0: topology change detected, propagating
    But I had to get that info directly from the /var/log/messages as yast's Journal Entries would not let me select and display yesterday's messages.
    I am not sure about the error messages. Presumably there is a problem with the SSD ("SECURITY FREEZE LOCK") and not the HDD. You need to further investigate:

    • run 'fdisk -l'
    • run 'journalctl -b -0 _KERNEL_SUBSYSTEM=scsi'
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  8. #8

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by karlmistelberger View Post
    I am not sure about the error messages. Presumably there is a problem with the SSD ("SECURITY FREEZE LOCK") and not the HDD. You need to further investigate:

    • run 'fdisk -l'
    • run 'journalctl -b -0 _KERNEL_SUBSYSTEM=scsi'
    Oh?!
    Code:
    chris@asus-roc:~> fdisk -l
    Absolute path to 'fdisk' is '/usr/sbin/fdisk', so running it may require superuser privileges (eg. root).
    chris@asus-roc:~> sudo fdisk -l
    Disk /dev/sda: 111.8 GiB, 120040980480 bytes, 234455040 sectors
    Disk model: WDC WDS120G2G0A-
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 417FA6A7-602D-4DF4-9A5E-BD68E8E735C1
    
    Device         Start       End   Sectors  Size Type
    /dev/sda1       2048     18431     16384    8M BIOS boot
    /dev/sda2      18432  83904511  83886080   40G Linux filesystem
    /dev/sda3   83904512 230258687 146354176 69.8G Linux filesystem
    /dev/sda4  230258688 234455006   4196319    2G Linux swap
    
    
    Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk model: WDC WD20EZRX-00D
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 53A483D5-146F-11E4-8C40-001FE25801E0
    
    Device     Start        End    Sectors  Size Type
    /dev/sdb1   2048 3907028991 3907026944  1.8T Linux filesystem
    chris@asus-roc:~>

    Code:
    chris@asus-roc:~> sudo journalctl -b -0 _KERNEL_SUBSYSTEM=scsi
    -- Logs begin at Fri 2021-02-26 09:14:26 AWST, end at Fri 2021-02-26 15:59:04 AWST. --
    Feb 26 09:14:26 asus-roc kernel: scsi host0: ahci
    Feb 26 09:14:26 asus-roc kernel: scsi host1: ahci
    Feb 26 09:14:26 asus-roc kernel: scsi host2: ahci
    Feb 26 09:14:26 asus-roc kernel: scsi host3: ahci
    Feb 26 09:14:26 asus-roc kernel: scsi host4: ahci
    Feb 26 09:14:26 asus-roc kernel: scsi host5: ahci
    Feb 26 09:14:26 asus-roc kernel: scsi 2:0:0:0: Direct-Access     ATA      WDC WDS120G2G0A- 0000 PQ: 0 ANSI: 5
    Feb 26 09:14:26 asus-roc kernel: sd 2:0:0:0: [sda] 234455040 512-byte logical blocks: (120 GB/112 GiB)
    Feb 26 09:14:26 asus-roc kernel: sd 2:0:0:0: [sda] Write Protect is off
    Feb 26 09:14:26 asus-roc kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Feb 26 09:14:26 asus-roc kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb 26 09:14:26 asus-roc kernel: sd 2:0:0:0: [sda] Attached SCSI disk
    Feb 26 09:14:26 asus-roc kernel: scsi 3:0:0:0: Direct-Access     ATA      WDC WD20EZRX-00D 0A80 PQ: 0 ANSI: 5
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: [sdb] 4096-byte physical blocks
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: [sdb] Write Protect is off
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: [sdb] Attached SCSI disk
    Feb 26 09:14:26 asus-roc kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0
    Feb 26 09:14:27 asus-roc kernel: scsi host6: usb-storage 1-14:1.0
    Feb 26 09:14:28 asus-roc kernel: scsi 6:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
    Feb 26 09:14:28 asus-roc kernel: scsi 6:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
    Feb 26 09:14:28 asus-roc kernel: scsi 6:0:0:2: Direct-Access     Generic  USB xD/SM Reader 1.02 PQ: 0 ANSI: 0
    Feb 26 09:14:28 asus-roc kernel: scsi 6:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:1: Attached scsi generic sg3 type 0
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:2: Attached scsi generic sg4 type 0
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:3: Attached scsi generic sg5 type 0
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:2: [sde] Attached SCSI removable disk
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:1: [sdd] Attached SCSI removable disk
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:0: [sdc] Attached SCSI removable disk
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:3: [sdf] Attached SCSI removable disk
    Feb 26 13:43:46 asus-roc.lan kernel: scsi host7: usb-storage 1-11:1.0
    Feb 26 13:43:48 asus-roc.lan kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer Edge      1.20 PQ: 0 ANSI: 5
    Feb 26 13:43:48 asus-roc.lan kernel: sd 7:0:0:0: Attached scsi generic sg6 type 0
    Feb 26 13:43:48 asus-roc.lan kernel: sd 7:0:0:0: [sdg] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
    Feb 26 13:43:48 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Write Protect is off
    Feb 26 13:43:48 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Mode Sense: 43 00 00 00
    Feb 26 13:43:48 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    Feb 26 13:43:48 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Attached SCSI removable disk
    Feb 26 14:24:48 asus-roc.lan kernel: scsi host7: usb-storage 1-11:1.0
    Feb 26 14:24:49 asus-roc.lan kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer Edge      1.20 PQ: 0 ANSI: 5
    Feb 26 14:24:49 asus-roc.lan kernel: sd 7:0:0:0: Attached scsi generic sg6 type 0
    Feb 26 14:24:49 asus-roc.lan kernel: sd 7:0:0:0: [sdg] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
    Feb 26 14:24:49 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Write Protect is off
    Feb 26 14:24:49 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Mode Sense: 43 00 00 00
    Feb 26 14:24:49 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    Feb 26 14:24:49 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Attached SCSI removable disk
    Feb 26 14:30:51 asus-roc.lan kernel: scsi host7: usb-storage 1-11:1.0
    Feb 26 14:30:52 asus-roc.lan kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer Edge      1.20 PQ: 0 ANSI: 5
    Feb 26 14:30:52 asus-roc.lan kernel: sd 7:0:0:0: Attached scsi generic sg6 type 0
    Feb 26 14:30:52 asus-roc.lan kernel: sd 7:0:0:0: [sdg] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
    Feb 26 14:30:52 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Write Protect is off
    Feb 26 14:30:52 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Mode Sense: 43 00 00 00
    Feb 26 14:30:52 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    Feb 26 14:30:52 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Attached SCSI removable disk
    Feb 26 15:55:13 asus-roc.lan kernel: sd 2:0:0:0: [sda] Synchronizing SCSI cache
    Feb 26 15:55:13 asus-roc.lan kernel: sd 3:0:0:0: [sdb] Synchronizing SCSI cache
    Feb 26 15:55:13 asus-roc.lan kernel: sd 3:0:0:0: [sdb] Stopping disk
    Feb 26 15:55:13 asus-roc.lan kernel: sd 2:0:0:0: [sda] Stopping disk
    Feb 26 15:55:13 asus-roc.lan kernel: sd 2:0:0:0: [sda] Starting disk
    Feb 26 15:55:13 asus-roc.lan kernel: sd 3:0:0:0: [sdb] Starting disk
    chris@asus-roc:~>
    Those commands were run 5 minutes after I resumed from being Suspended. Superficially I don't see anything wrong.

  9. #9
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,422
    Blog Entries
    1

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by kitman View Post
    Oh?!
    Code:
    chris@asus-roc:~> fdisk -l
    Absolute path to 'fdisk' is '/usr/sbin/fdisk', so running it may require superuser privileges (eg. root).
    chris@asus-roc:~> sudo fdisk -l
    Disk /dev/sda: 111.8 GiB, 120040980480 bytes, 234455040 sectors
    Disk model: WDC WDS120G2G0A-
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 417FA6A7-602D-4DF4-9A5E-BD68E8E735C1
    
    Device         Start       End   Sectors  Size Type
    /dev/sda1       2048     18431     16384    8M BIOS boot
    /dev/sda2      18432  83904511  83886080   40G Linux filesystem
    /dev/sda3   83904512 230258687 146354176 69.8G Linux filesystem
    /dev/sda4  230258688 234455006   4196319    2G Linux swap
    
    
    Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk model: WDC WD20EZRX-00D
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 53A483D5-146F-11E4-8C40-001FE25801E0
    
    Device     Start        End    Sectors  Size Type
    /dev/sdb1   2048 3907028991 3907026944  1.8T Linux filesystem
    chris@asus-roc:~>

    Code:
    chris@asus-roc:~> sudo journalctl -b -0 _KERNEL_SUBSYSTEM=scsi
    -- Logs begin at Fri 2021-02-26 09:14:26 AWST, end at Fri 2021-02-26 15:59:04 AWST. --
    Feb 26 09:14:26 asus-roc kernel: scsi host0: ahci
    Feb 26 09:14:26 asus-roc kernel: scsi host1: ahci
    Feb 26 09:14:26 asus-roc kernel: scsi host2: ahci
    Feb 26 09:14:26 asus-roc kernel: scsi host3: ahci
    Feb 26 09:14:26 asus-roc kernel: scsi host4: ahci
    Feb 26 09:14:26 asus-roc kernel: scsi host5: ahci
    Feb 26 09:14:26 asus-roc kernel: scsi 2:0:0:0: Direct-Access     ATA      WDC WDS120G2G0A- 0000 PQ: 0 ANSI: 5
    Feb 26 09:14:26 asus-roc kernel: sd 2:0:0:0: [sda] 234455040 512-byte logical blocks: (120 GB/112 GiB)
    Feb 26 09:14:26 asus-roc kernel: sd 2:0:0:0: [sda] Write Protect is off
    Feb 26 09:14:26 asus-roc kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Feb 26 09:14:26 asus-roc kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb 26 09:14:26 asus-roc kernel: sd 2:0:0:0: [sda] Attached SCSI disk
    Feb 26 09:14:26 asus-roc kernel: scsi 3:0:0:0: Direct-Access     ATA      WDC WD20EZRX-00D 0A80 PQ: 0 ANSI: 5
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: [sdb] 4096-byte physical blocks
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: [sdb] Write Protect is off
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: [sdb] Attached SCSI disk
    Feb 26 09:14:26 asus-roc kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0
    Feb 26 09:14:26 asus-roc kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0
    Feb 26 09:14:27 asus-roc kernel: scsi host6: usb-storage 1-14:1.0
    Feb 26 09:14:28 asus-roc kernel: scsi 6:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
    Feb 26 09:14:28 asus-roc kernel: scsi 6:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
    Feb 26 09:14:28 asus-roc kernel: scsi 6:0:0:2: Direct-Access     Generic  USB xD/SM Reader 1.02 PQ: 0 ANSI: 0
    Feb 26 09:14:28 asus-roc kernel: scsi 6:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:1: Attached scsi generic sg3 type 0
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:2: Attached scsi generic sg4 type 0
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:3: Attached scsi generic sg5 type 0
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:2: [sde] Attached SCSI removable disk
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:1: [sdd] Attached SCSI removable disk
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:0: [sdc] Attached SCSI removable disk
    Feb 26 09:14:28 asus-roc kernel: sd 6:0:0:3: [sdf] Attached SCSI removable disk
    Feb 26 13:43:46 asus-roc.lan kernel: scsi host7: usb-storage 1-11:1.0
    Feb 26 13:43:48 asus-roc.lan kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer Edge      1.20 PQ: 0 ANSI: 5
    Feb 26 13:43:48 asus-roc.lan kernel: sd 7:0:0:0: Attached scsi generic sg6 type 0
    Feb 26 13:43:48 asus-roc.lan kernel: sd 7:0:0:0: [sdg] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
    Feb 26 13:43:48 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Write Protect is off
    Feb 26 13:43:48 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Mode Sense: 43 00 00 00
    Feb 26 13:43:48 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    Feb 26 13:43:48 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Attached SCSI removable disk
    Feb 26 14:24:48 asus-roc.lan kernel: scsi host7: usb-storage 1-11:1.0
    Feb 26 14:24:49 asus-roc.lan kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer Edge      1.20 PQ: 0 ANSI: 5
    Feb 26 14:24:49 asus-roc.lan kernel: sd 7:0:0:0: Attached scsi generic sg6 type 0
    Feb 26 14:24:49 asus-roc.lan kernel: sd 7:0:0:0: [sdg] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
    Feb 26 14:24:49 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Write Protect is off
    Feb 26 14:24:49 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Mode Sense: 43 00 00 00
    Feb 26 14:24:49 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    Feb 26 14:24:49 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Attached SCSI removable disk
    Feb 26 14:30:51 asus-roc.lan kernel: scsi host7: usb-storage 1-11:1.0
    Feb 26 14:30:52 asus-roc.lan kernel: scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer Edge      1.20 PQ: 0 ANSI: 5
    Feb 26 14:30:52 asus-roc.lan kernel: sd 7:0:0:0: Attached scsi generic sg6 type 0
    Feb 26 14:30:52 asus-roc.lan kernel: sd 7:0:0:0: [sdg] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
    Feb 26 14:30:52 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Write Protect is off
    Feb 26 14:30:52 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Mode Sense: 43 00 00 00
    Feb 26 14:30:52 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    Feb 26 14:30:52 asus-roc.lan kernel: sd 7:0:0:0: [sdg] Attached SCSI removable disk
    Feb 26 15:55:13 asus-roc.lan kernel: sd 2:0:0:0: [sda] Synchronizing SCSI cache
    Feb 26 15:55:13 asus-roc.lan kernel: sd 3:0:0:0: [sdb] Synchronizing SCSI cache
    Feb 26 15:55:13 asus-roc.lan kernel: sd 3:0:0:0: [sdb] Stopping disk
    Feb 26 15:55:13 asus-roc.lan kernel: sd 2:0:0:0: [sda] Stopping disk
    Feb 26 15:55:13 asus-roc.lan kernel: sd 2:0:0:0: [sda] Starting disk
    Feb 26 15:55:13 asus-roc.lan kernel: sd 3:0:0:0: [sdb] Starting disk
    chris@asus-roc:~>
    Those commands were run 5 minutes after I resumed from being Suspended. Superficially I don't see anything wrong.
    The fixed disks show the same messages as on my machine. What about the removable drives? Get rid of it and run suspend/resume. Does the lag still occur?

    Show the output of 'journalctl -b 0 _KERNEL_SUBSYSTEM=usb'.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  10. #10

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by karlmistelberger View Post
    The fixed disks show the same messages as on my machine. What about the removable drives? Get rid of it and run suspend/resume. Does the lag still occur?

    Show the output of 'journalctl -b 0 _KERNEL_SUBSYSTEM=usb'.
    That is very odd, that USB SanDisk drive had been ejected and physically removed about an hour prior. The other card reader devices are empty. There is only the SDD and HDD drives connected.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •