Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: Suspend - waking up takes a while.

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

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by kitman View Post
    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.
    Just for avoiding any confusion and for facilitating troubleshooting:

    • remove any media
    • reboot the machine
    • suspend and resume the machine
    • report the outcome. Does waking up still take a while?
    • If so post output of command 'journal -b', see 'man susepaste'.
    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

  2. #12

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by karlmistelberger View Post
    Just for avoiding any confusion and for facilitating troubleshooting:

    • remove any media
    • reboot the machine
    • suspend and resume the machine
    • report the outcome. Does waking up still take a while?
    • If so post output of command 'journal -b', see 'man susepaste'.
    Hi Karl,

    PC was rebooted with all USB etc removed at 14:05, suspended at 14:17 and woken up at 14:45. Hope it makes sense to you.

    here tis - https://susepaste.org/10361094

  3. #13
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,414
    Blog Entries
    1

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by kitman View Post
    Hi Karl,

    PC was rebooted with all USB etc removed at 14:05, suspended at 14:17 and woken up at 14:45. Hope it makes sense to you.

    here tis - https://susepaste.org/10361094
    That looks like disk trouble on ata4. To find out the drive associated with ata4 run:

    Code:
    erlangen:~ # systemctl list-units '*ata4*' 
      UNIT                                                                                     LOAD   ACTIVE SUB     DESCRIPTION             
      sys-devices-pci0000:00-0000:00:17.0-ata4-host3-target3:0:0-3:0:0:0-block-sdb-sdb1.device loaded active plugged CT2000BX500SSD1 Home-SSD 
      sys-devices-pci0000:00-0000:00:17.0-ata4-host3-target3:0:0-3:0:0:0-block-sdb.device      loaded active plugged CT2000BX500SSD1          
    
    LOAD   = Reflects whether the unit definition was properly loaded. 
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB. 
    SUB    = The low-level unit activation state, values depend on unit type. 
    
    2 loaded units listed. Pass --all to see loaded but inactive units, too. 
    To show all installed unit files use 'systemctl list-unit-files'. 
    erlangen:~ #
    Check cables and the drive. Could indicate a looming failure. A working drives doesn't issue messages as observed with your system. Logs are pretty terse here:

    Code:
    erlangen:~ # journalctl -b -u systemd-suspend.service 
    -- Logs begin at Wed 2021-02-17 13:00:05 CET, end at Sat 2021-02-27 10:03:02 CET. -- 
    Feb 27 09:43:35 erlangen systemd[1]: Starting Suspend... 
    Feb 27 09:43:35 erlangen systemd-sleep[2716]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 
    Feb 27 09:43:35 erlangen systemd-sleep[2714]: Suspending system... 
    Feb 27 09:43:49 erlangen systemd-sleep[2714]: System resumed. 
    Feb 27 09:43:49 erlangen systemd-sleep[2770]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 
    Feb 27 09:43:49 erlangen systemd[1]: systemd-suspend.service: Succeeded. 
    Feb 27 09:43:49 erlangen systemd[1]: Finished Suspend. 
    erlangen:~ # journalctl -b |grep ata4                   
    Feb 27 09:41:54 erlangen kernel: ata4: SATA max UDMA/133 abar m2048@0xdff4b000 port 0xdff4b280 irq 125 
    Feb 27 09:41:54 erlangen kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) 
    Feb 27 09:41:54 erlangen kernel: ata4.00: ATA-10: CT2000BX500SSD1, M6CR030, max UDMA/133 
    Feb 27 09:41:54 erlangen kernel: ata4.00: 3907029168 sectors, multi 1: LBA48 NCQ (depth 32), AA 
    Feb 27 09:41:54 erlangen kernel: ata4.00: configured for UDMA/133 
    Feb 27 09:43:49 erlangen kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) 
    Feb 27 09:43:49 erlangen kernel: ata4.00: configured for UDMA/133 
    erlangen:~ #
    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

  4. #14

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by karlmistelberger View Post
    That looks like disk trouble on ata4. To find out the drive associated with ata4 run:

    Code:
    erlangen:~ # systemctl list-units '*ata4*' 
      UNIT                                                                                     LOAD   ACTIVE SUB     DESCRIPTION             
      sys-devices-pci0000:00-0000:00:17.0-ata4-host3-target3:0:0-3:0:0:0-block-sdb-sdb1.device loaded active plugged CT2000BX500SSD1 Home-SSD 
      sys-devices-pci0000:00-0000:00:17.0-ata4-host3-target3:0:0-3:0:0:0-block-sdb.device      loaded active plugged CT2000BX500SSD1          
    
    LOAD   = Reflects whether the unit definition was properly loaded. 
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB. 
    SUB    = The low-level unit activation state, values depend on unit type. 
    
    2 loaded units listed. Pass --all to see loaded but inactive units, too. 
    To show all installed unit files use 'systemctl list-unit-files'. 
    erlangen:~ #
    Check cables and the drive. Could indicate a looming failure. A working drives doesn't issue messages as observed with your system. Logs are pretty terse here:

    Code:
    erlangen:~ # journalctl -b -u systemd-suspend.service 
    -- Logs begin at Wed 2021-02-17 13:00:05 CET, end at Sat 2021-02-27 10:03:02 CET. -- 
    Feb 27 09:43:35 erlangen systemd[1]: Starting Suspend... 
    Feb 27 09:43:35 erlangen systemd-sleep[2716]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 
    Feb 27 09:43:35 erlangen systemd-sleep[2714]: Suspending system... 
    Feb 27 09:43:49 erlangen systemd-sleep[2714]: System resumed. 
    Feb 27 09:43:49 erlangen systemd-sleep[2770]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 
    Feb 27 09:43:49 erlangen systemd[1]: systemd-suspend.service: Succeeded. 
    Feb 27 09:43:49 erlangen systemd[1]: Finished Suspend. 
    erlangen:~ # journalctl -b |grep ata4                   
    Feb 27 09:41:54 erlangen kernel: ata4: SATA max UDMA/133 abar m2048@0xdff4b000 port 0xdff4b280 irq 125 
    Feb 27 09:41:54 erlangen kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) 
    Feb 27 09:41:54 erlangen kernel: ata4.00: ATA-10: CT2000BX500SSD1, M6CR030, max UDMA/133 
    Feb 27 09:41:54 erlangen kernel: ata4.00: 3907029168 sectors, multi 1: LBA48 NCQ (depth 32), AA 
    Feb 27 09:41:54 erlangen kernel: ata4.00: configured for UDMA/133 
    Feb 27 09:43:49 erlangen kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) 
    Feb 27 09:43:49 erlangen kernel: ata4.00: configured for UDMA/133 
    erlangen:~ #
    ata4 is indeed my 2TB HDD at /dev/sdb

    Code:
    chris@asus-roc:~> systemctl list-units '*ata4*'
    UNIT                                                                                     LOAD   ACTIVE SUB     DESCRIPTION                   
    sys-devices-pci0000:00-0000:00:17.0-ata4-host3-target3:0:0-3:0:0:0-block-sdb-sdb1.device loaded active plugged WDC_WD20EZRX-00D8PB0 wd2tgreen
    sys-devices-pci0000:00-0000:00:17.0-ata4-host3-target3:0:0-3:0:0:0-block-sdb.device      loaded active plugged WDC_WD20EZRX-00D8PB0          
    
    LOAD   = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB    = The low-level unit activation state, values depend on unit type.
    
    2 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    chris@asus-roc:~>
    Code:
    chris@asus-roc:~> sudo journalctl -b |grep ata4
    Feb 27 15:52:46 asus-roc kernel: ata4: SATA max UDMA/133 abar m2048@0xf724b000 port 0xf724b280 irq 127
    Feb 27 15:52:46 asus-roc kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ATA-9: WDC WD20EZRX-00D8PB0, 80.00A80, max UDMA/133
    Feb 27 15:52:46 asus-roc kernel: ata4.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Feb 27 15:52:46 asus-roc kernel: ata4.00: configured for UDMA/133
    Feb 27 16:50:41 asus-roc.lan kernel: ata4: link is slow to respond, please be patient (ready=0)
    Feb 27 16:50:46 asus-roc.lan kernel: ata4: COMRESET failed (errno=-16)
    Feb 27 16:50:51 asus-roc.lan kernel: ata4: link is slow to respond, please be patient (ready=0)
    Feb 27 16:50:56 asus-roc.lan kernel: ata4: COMRESET failed (errno=-16)
    Feb 27 16:51:01 asus-roc.lan kernel: ata4: link is slow to respond, please be patient (ready=0)
    Feb 27 16:51:30 asus-roc.lan kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: configured for UDMA/133
    chris@asus-roc:~>
    Funny that the recorded fail times don;t line up with coming out of Suspend mode at 14:45.

    A potential HDD failure worries me (as it should). Is there a test I can do with S.M.A.R.T. tools to confirm?

    Thanks.

  5. #15
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,414
    Blog Entries
    1

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by kitman View Post
    ata4 is indeed my 2TB HDD at /dev/sdb

    Code:
    chris@asus-roc:~> systemctl list-units '*ata4*'
    UNIT                                                                                     LOAD   ACTIVE SUB     DESCRIPTION                   
    sys-devices-pci0000:00-0000:00:17.0-ata4-host3-target3:0:0-3:0:0:0-block-sdb-sdb1.device loaded active plugged WDC_WD20EZRX-00D8PB0 wd2tgreen
    sys-devices-pci0000:00-0000:00:17.0-ata4-host3-target3:0:0-3:0:0:0-block-sdb.device      loaded active plugged WDC_WD20EZRX-00D8PB0          
    
    LOAD   = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB    = The low-level unit activation state, values depend on unit type.
    
    2 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    chris@asus-roc:~>
    Code:
    chris@asus-roc:~> sudo journalctl -b |grep ata4
    Feb 27 15:52:46 asus-roc kernel: ata4: SATA max UDMA/133 abar m2048@0xf724b000 port 0xf724b280 irq 127
    Feb 27 15:52:46 asus-roc kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ATA-9: WDC WD20EZRX-00D8PB0, 80.00A80, max UDMA/133
    Feb 27 15:52:46 asus-roc kernel: ata4.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Feb 27 15:52:46 asus-roc kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Feb 27 15:52:46 asus-roc kernel: ata4.00: configured for UDMA/133
    Feb 27 16:50:41 asus-roc.lan kernel: ata4: link is slow to respond, please be patient (ready=0)
    Feb 27 16:50:46 asus-roc.lan kernel: ata4: COMRESET failed (errno=-16)
    Feb 27 16:50:51 asus-roc.lan kernel: ata4: link is slow to respond, please be patient (ready=0)
    Feb 27 16:50:56 asus-roc.lan kernel: ata4: COMRESET failed (errno=-16)
    Feb 27 16:51:01 asus-roc.lan kernel: ata4: link is slow to respond, please be patient (ready=0)
    Feb 27 16:51:30 asus-roc.lan kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    Feb 27 16:51:31 asus-roc.lan kernel: ata4.00: configured for UDMA/133
    chris@asus-roc:~>
    Funny that the recorded fail times don;t line up with coming out of Suspend mode at 14:45.

    A potential HDD failure worries me (as it should). Is there a test I can do with S.M.A.R.T. tools to confirm?

    Thanks.
    Your disk is a 'green' WD20EZRX. I have a WD40EZRX, which also has some 'green' features and caused headache in the past. I fixed that by disabling the idle3 timer using http://idle3-tools.sourceforge.net/

    Replace the SATA cable by a new one or exchange cables between the drives. Errors now should occur with sda and no longer with sdb.

    Errors could also be caused by bad connectors. I successfully cleaned several connectors using an interdental brush and 99.9% isopropyl alcohol.

    Use 'smartctl --all /dev/sdb' to display smart information.

    Run an extended test 'smartctl --test=long /dev/sdb'.
    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

  6. #16

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by karlmistelberger View Post
    Your disk is a 'green' WD20EZRX. I have a WD40EZRX, which also has some 'green' features and caused headache in the past. I fixed that by disabling the idle3 timer using http://idle3-tools.sourceforge.net/

    Replace the SATA cable by a new one or exchange cables between the drives. Errors now should occur with sda and no longer with sdb.

    Errors could also be caused by bad connectors. I successfully cleaned several connectors using an interdental brush and 99.9% isopropyl alcohol.

    Use 'smartctl --all /dev/sdb' to display smart information.

    Run an extended test 'smartctl --test=long /dev/sdb'.
    I read that idle3 article. I think I exceed 1000

    Code:
    chris@asus-roc:~> sudo smartctl -A /dev/sdb | grep "^193"
    193 Load_Cycle_Count        0x0032   010   010   000    Old_age   Always       -       571785
    Will get that utility and have a go (after backing up).

    Thanks.

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

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by kitman View Post
    I read that idle3 article. I think I exceed 1000

    Code:
    chris@asus-roc:~> sudo smartctl -A /dev/sdb | grep "^193"
    193 Load_Cycle_Count        0x0032   010   010   000    Old_age   Always       -       571785
    Will get that utility and have a go (after backing up).

    Thanks.
    This is a really huge count. The maximum design value is 300,000. Your disk is worn out. I fixed the disk early:

    Code:
    erlangen:~ # smartctl -A /dev/sda | grep "^193"              
    193 Load_Cycle_Count        0x0032   198   198   000    Old_age   Always       -       6274 
    erlangen:~ #
    https://software.opensuse.org/package/idle3-tools

    You may consider replacing the HDD by a SSD of the same size. My disk has been replaced last year and is used as a backup drive now:

    Code:
    erlangen:~ # inxi -D 
    Drives:    Local Storage:total: 6.38 TiB used: 3.12 TiB (48.9%)  
               ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 950 PRO 512GB size: 476.94 GiB  
               ID-2: /dev/sda vendor: Western Digital model: WD40EZRX-22SPEB0 size: 3.64 TiB  
               ID-3: /dev/sdb vendor: Crucial model: CT2000BX500SSD1 size: 1.82 TiB  
               ID-4: /dev/sdc vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB  
    erlangen:~ #
    
    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. #18

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by karlmistelberger View Post
    This is a really huge count. The maximum design value is 300,000. Your disk is worn out. I fixed the disk early:
    Hm, buy a new disk or get my tooth fixed? 2TB SSD is not cheap.
    These are hard decisions

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

    Default Re: Suspend - waking up takes a while.

    Quote Originally Posted by kitman View Post
    Hm, buy a new disk or get my tooth fixed? 2TB SSD is not cheap.
    These are hard decisions
    I bought the CT2000BX500SSD1 last summer for 199€. Now it's down to 169€. 1TB is now 91€. Speed, lifetime and reliability in an average desktop are much higher than HDD (2TB WD blue 57€).
    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

Page 2 of 2 FirstFirst 12

Posting Permissions

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