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

Thread: Resume failure

  1. #11
    Join Date
    Oct 2014
    Location
    Italy
    Posts
    1,659

    Default Re: Resume failure

    Quote Originally Posted by elfroggio View Post
    Yes, it works most of the time, approximately 4 out of 5
    Do you have an Nvidia card with the nouveau driver? With some chips nouveau has problems to resume properly.
    Main: Leap 15 Gnome on i7 4720HQ + Geforce GTX960M
    Test: Leap 42.3 (& others) on Core2Duo + GM965

  2. #12

    Default Re: Resume failure

    Quote Originally Posted by tannington View Post
    In general...

    suspend to RAM is usually called "suspend"
    suspend to disk is usually called "hibernate"
    I always use the suspend

    Thanks

  3. #13

    Default Re: Resume failure

    Quote Originally Posted by OrsoBruno View Post
    Do you have an Nvidia card with the nouveau driver? With some chips nouveau has problems to resume properly.
    No, I use amdgpu with a radeon 570 (MSI)

    Code:
    > inxi -Gxx
    Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
    Graphics:  Card: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580]
               bus-ID: 01:00.0 chip-ID: 1002:67df
               Display Server: x11 (X.org 1.19.6 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon)
               tty size: 127x34
    >
    Thanks

  4. #14
    Join Date
    Sep 2012
    Posts
    4,926

    Default Re: Resume failure

    Quote Originally Posted by elfroggio View Post
    I always use the suspend [to RAM]
    In this case all those posts about swap size are irrelevant and you need to provide more detailed description of what happens. When you resume from STR computer just wakes up; it never looks at your resume partition. And if your system reboots instead of waking up, "error" message is correct - there is no hibernation image saved in swap. But this "error" is not the root cause of issue.

    So start with describing your problem so that others can understand it.

  5. #15

    Default Re: Resume failure

    Quote Originally Posted by arvidjaar View Post
    So start with describing your problem so that others can understand it.
    I hoped I did, obviously not (English is not my first nor second language).

    The problem happens once out 5 suspends, when I press on the power button to resume:

    1. The power button while suspend is flashing blue
    2. I press the power button
    3. The power button becomes continuous blue
    4. But nothing shows on the screens. Both monitors stay in the sleeping mode.


    I have tried every keystroke, nothing. I have to shutdown by pressing the power button for 4 seconds, then it shuts down, then I can restart the computer.

    Hopefully, this describes what's happening.

    The only message that I saw in the journals was:

    Code:
    systemd-hiberna[385] Could not resume from '/dev/disk/by-id-ata-WDC_WD30ERX-68EUN0_WD_WCC4N3TA3RK-part4' (8:4).
    with

    Code:
    ls -alF /dev/disk/by-id/
    total 0
    drwxr-xr-x 2 root root 1000 May 17 13:23 ./
    drwxr-xr-x 8 root root  160 May 17 13:23 ../
    lrwxrwxrwx 1 root root    9 May 17 13:23 ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N3TA43RK -> ../../sda
    lrwxrwxrwx 1 root root   10 May 17 13:23 ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N3TA43RK-part1 -> ../../sda1
    lrwxrwxrwx 1 root root   10 May 17 13:23 ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N3TA43RK-part2 -> ../../sda2
    lrwxrwxrwx 1 root root   10 May 17 13:24 ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N3TA43RK-part3 -> ../../sda3
    lrwxrwxrwx 1 root root   10 May 17 13:23 ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N3TA43RK-part4 -> ../../sda4
    
    and
    
    > lsblk
    
    NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
    sda      8:0    0  2.7T  0 disk  
    ├─sda1   8:1    0    8M  0 part  
    ├─sda2   8:2    0  120G  0 part /
    ├─sda3   8:3    0  2.6T  0 part /home
    └─sda4   8:4    0 12.1G  0 part [SWAP]
    sdb      8:16   0  2.7T  0 disk  
    └─sdb1   8:17   0  2.7T  0 part /drive-b
    sr0     11:0    1 1024M  0 rom
    Thanks

  6. #16
    Join Date
    Oct 2014
    Location
    Italy
    Posts
    1,659

    Default Re: Resume failure

    OK, that's definitely "suspend to RAM". The "error" you quoted is part of a normal boot sequence, so nothing meaningful.
    When you press the suspend button you should see in the journal something like the following:
    Code:
    mag 19 15:10:50 LT_B systemd-logind[1406]: Suspend key pressed.
    ...
    mag 19 15:11:12 LT_B kernel: ACPI: Preparing to enter system sleep state S3
    mag 19 15:11:12 LT_B kernel: ACPI : EC: event blocked
    mag 19 15:11:12 LT_B kernel: ACPI : EC: EC stopped
    mag 19 15:11:12 LT_B kernel: PM: Saving platform NVS memory
    mag 19 15:11:12 LT_B kernel: Disabling non-boot CPUs ...
    mag 19 15:11:12 LT_B kernel: smpboot: CPU 1 is now offline
    mag 19 15:11:12 LT_B kernel: smpboot: CPU 2 is now offline
    mag 19 15:11:12 LT_B kernel: smpboot: CPU 3 is now offline
    mag 19 15:11:12 LT_B kernel: Broke affinity for irq 33
    ...
    mag 19 15:11:12 LT_B kernel: Broke affinity for irq 33
    mag 19 15:11:12 LT_B kernel: Broke affinity for irq 35
    mag 19 15:11:12 LT_B kernel: smpboot: CPU 7 is now offline
    with several other lines in between depending on your system configuration.
    A successful resume should write something like the following in the journal:
    Code:
    mag 19 15:11:12 LT_B kernel: ACPI: Low-level resume complete
    mag 19 15:11:12 LT_B kernel: ACPI : EC: EC started
    mag 19 15:11:12 LT_B kernel: PM: Restoring platform NVS memory
    mag 19 15:11:12 LT_B kernel: Suspended for 18.814 seconds
    mag 19 15:11:12 LT_B kernel: Enabling non-boot CPUs ...
    mag 19 15:11:12 LT_B kernel: x86: Booting SMP configuration:
    mag 19 15:11:12 LT_B kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
    mag 19 15:11:12 LT_B kernel:  cache: parent cpu1 should not be sleeping
    mag 19 15:11:12 LT_B kernel: microcode: sig=0x306c3, pf=0x20, revision=0x1c
    mag 19 15:11:12 LT_B kernel: microcode: updated to revision 0x27, date = 2019-02-26
    mag 19 15:11:12 LT_B kernel: CPU1 is up
    ...
    mag 19 15:11:13 LT_B systemd-sleep[3730]: System resumed.
    mag 19 15:11:13 LT_B systemd-sleep[3730]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
    mag 19 15:11:13 LT_B systemd[1]: Started Suspend.
    mag 19 15:11:13 LT_B systemd[1]: sleep.target: Unit not needed anymore. Stopping.
    mag 19 15:11:13 LT_B systemd[1]: Stopped target Sleep.
    mag 19 15:11:13 LT_B systemd[1]: suspend.target: Bound to unit systemd-suspend.service, but unit isn't active.
    mag 19 15:11:13 LT_B systemd[1]: Dependency failed for Suspend.
    mag 19 15:11:13 LT_B systemd-logind[1406]: Operation 'sleep' finished.
    mag 19 15:11:13 LT_B systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
    with several more lines depending on your configuration, network status etc.
    Try to look for differences between a "successful" resume and a "failed" one.
    To see the journal for the latter you need a persistent journal (not a default in LEAP): look if you have a directory named /var/log/journal
    If not so, you should create one, or edit the configuration file /etc/systemd/journald.conf so that it reads:
    Code:
    [Journal]
    Storage=persistent
    Please see "man journald.conf" for further details or ask here.
    Main: Leap 15 Gnome on i7 4720HQ + Geforce GTX960M
    Test: Leap 42.3 (& others) on Core2Duo + GM965

  7. #17
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,092

    Default Re: Resume failure

    Quote Originally Posted by elfroggio View Post
    ...
    The problem happens once out 5 suspends, when I press on the power button to resume:

    1. The power button while suspend is flashing blue
    2. I press the power button
    3. The power button becomes continuous blue
    4. But nothing shows on the screens. Both monitors stay in the sleeping mode.


    I have tried every keystroke, nothing. I have to shutdown by pressing the power button for 4 seconds, then it shuts down, then I can restart the computer.
    So... has the system actually resumed and you've just lost video?

    Can you use the computer "blind" ... for example try:

    Ctrl-Alt-F2 to take you to a virtual terminal
    Enter your normal user name, pause for a moment, enter the user's password.
    Then "sudo /sbin/shutdown -r now"

    If the system the shuts down and reboots the resume was successful but you lost video on resume.


    The only message that I saw in the journals was:

    Code:
    systemd-hiberna[385] Could not resume from '/dev/disk/by-id-ata-WDC_WD30ERX-68EUN0_WD_WCC4N3TA3RK-part4' (8:4).
    As you're suspending to RAM that "error" message is not relevant to the problem.
    Regards, Paul

    Tumbleweed (Snapshot: 20190621) KDE Plasma 5
    Leap 15.0 KDE Plasma 5
    [Non-Tumbling Tumblweed (20150508) KDE 4 - Resurrected]

  8. #18

    Default Re: Resume failure

    Quote Originally Posted by tannington View Post
    So... has the system actually resumed and you've just lost video?

    Can you use the computer "blind" ... for example try:

    Ctrl-Alt-F2 to take you to a virtual terminal
    Enter your normal user name, pause for a moment, enter the user's password.
    Then "sudo /sbin/shutdown -r now"

    If the system the shuts down and reboots the resume was successful but you lost video on resume.
    No, it doesn't. I have tried all key combination that I could think of, including the ctrl-alt-F..., the ctrl-alt-backpspace, alt-ctrl-del and plenty of others, nothing.

    The only thing is a hard power off.

    Thanks

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
  •