Results 1 to 5 of 5

Thread: Suspend-to-RAM fails with quadcore processor

  1. #1

    Default Suspend-to-RAM fails with quadcore processor

    I did quite a lot of research into this topic but I feel this might be beyond my capabilities.

    The story: I've been running Tumbleweed with KDE (on X11) for a couple weeks. The DE and display server may not be relevant though, as this problem happens even in runlevel 1. PC fails to suspend.

    Other OSes: Suspend-to-RAM worked fine on Windows 7-11, Pop!OS and Siduction (therefore up-to-date kernels, in the case of Siduction the latest available, as with Tumbleweed). The limitation with Siduction was that it would wake up only from pressing the power button. Can't remember if Pop!OS worked the same way. All S-state functionality is there on Windows as far as I can tell. This seems to be openSUSE, or even Tumbleweed specific.

    My hardware: Gigabyte Ga-B75m-D3H motherboard with F15 bios (latest), 16GB of RAM,
    Intel i5-3450 (4) @ 3.500GHz using the integrated graphics, Samsung 860 Evo SSD with other three mechanical drives.

    Tumbleweed install is using Btrfs (with snapper, secure boot) for /, XFS for /home and a swap partition of ~6GB. It happens on a fresh install with no additional changes in software selection after choosing the Plasma desktop in the installer.

    Symptoms: After trying to suspend, I see the KDE lockscreen briefly, then the display goes off, then about a second or so later on again, I see the lockscreen, and then the screen finally powers down for good. Fans keep spinning, and cabinet LED is still on. Upon pressing the keyboard or power button, I hear the mechanical drives starting, screen turns on leading me to the lockscreen.

    What I tried:
    1) Disabling all devices in /proc/acpi/wakeup
    2) Various boot options. Right now: GRUB_CMDLINE_LINUX_DEFAULT='splash=silent quiet security=apparmor mem_sleep_default=deep acpi=force apm=power_off acpi_osi=! acpi_osi="Windows 2012" loglevel=3 libata.force=noncq mitigations=auto'
    3) Booting to Tumbleweed with Xen Hypervisor. Don't know why, but suspend works (all CPU cores work). Desktop with Xen only has 2GB of RAM available though, otherwise I'd have called it a day at this point and make it the default Grub2 selection. I also noticed that resume sometimes triggers a reboot with this option.
    4) Boot with the maxcpus=0 option. Suspend works. I get only one CPU core to work with.
    5) Disabling cores while running the OS (echo0>/sys/devices/system/cpu/cpu1/online - for CPU cores 1 to 3). Doesn't work, but I don't seem to get any dmesg error message in particular, as can be seen below.

    Here is the dmesg output when I try suspend:


    Code:
                 ] PM: suspend entry (deep)
    [   65.710818] Filesystems sync: 0.074 seconds
    [   67.742618] Bluetooth: hci0: Timed out waiting for suspend events
    [   67.742626] Bluetooth: hci0: Suspend timeout bit: 6
    [   67.742642] Bluetooth: hci0: Suspend notifier action (3) failed: -110
    [   67.742780] Freezing user space processes ... (elapsed 0.001 seconds) done.
    [   67.744623] OOM killer disabled.
    [   67.744624] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [   67.745918] printk: Suspending console(s) (use no_console_suspend to debug)
    [   67.774628] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
    [   67.774649] sd 3:0:0:0: [sdc] Synchronizing SCSI cache
    [   67.774667] sd 5:0:0:0: [sdd] Synchronizing SCSI cache
    [   67.774673] sd 0:0:0:0: [sda] Synchronizing SCSI cache
    [   67.774802] sd 3:0:0:0: [sdc] Stopping disk
    [   67.774809] sd 5:0:0:0: [sdd] Stopping disk
    [   67.774877] sd 2:0:0:0: [sdb] Stopping disk
    [   67.774905] sd 0:0:0:0: [sda] Stopping disk
    [   68.954888] ACPI: PM: Preparing to enter system sleep state S3
    [   68.955500] ACPI: PM: Saving platform NVS memory
    [   68.955540] Disabling non-boot CPUs ...
    [   68.955541] Wakeup pending. Abort CPU freeze
    [   68.955542] Non-boot CPUs are not disabled
    [   68.955546] ACPI: PM: Waking up from system sleep state S3
    [   69.006176] sd 5:0:0:0: [sdd] Starting disk
    [   69.006204] sd 0:0:0:0: [sda] Starting disk
    [   69.006221] sd 2:0:0:0: [sdb] Starting disk
    [   69.006231] sd 3:0:0:0: [sdc] Starting disk
    [   69.170587] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
    [   69.353032] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [   69.353066] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [   69.353095] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [   69.353112] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [   69.353779] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210930/psargs-330)
    [   69.353786] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20210930/psparse-529)
        ...(other ACPI errors)...
    [   69.356311] ata1.00: supports DRM functions and may not be fully accessible
    [   69.357039] ata1.00: configured for UDMA/133
    [   71.944901] ata3.00: configured for UDMA/133
    [   71.978877] OOM killer enabled.
    [   71.978880] Restarting tasks ... done.
    [   71.986048] video LNXVIDEO:00: Restoring backlight state
    [   71.986086] PM: suspend exit
    [   71.986132] PM: suspend entry (s2idle)
    [   72.030760] Filesystems sync: 0.044 seconds
    [   72.032431] Freezing user space processes ... (elapsed 0.022 seconds) done.
    [   72.054670] OOM killer disabled.
    [   72.054671] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [   72.055908] printk: Suspending console(s) (use no_console_suspend to debug)
    [   72.250616] sd 5:0:0:0: [sdd] Synchronizing SCSI cache
    [   72.250651] sd 3:0:0:0: [sdc] Synchronizing SCSI cache
    [   72.250653] sd 0:0:0:0: [sda] Synchronizing SCSI cache
    [   72.250730] sd 5:0:0:0: [sdd] Stopping disk
    [   72.250730] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
    [   72.250821] sd 3:0:0:0: [sdc] Stopping disk
    [   72.250894] sd 0:0:0:0: [sda] Stopping disk
    [   72.250938] sd 2:0:0:0: [sdb] Stopping disk
    [  102.791692] sd 0:0:0:0: [sda] Starting disk
    [  102.791709] sd 3:0:0:0: [sdc] Starting disk
    [  102.791715] sd 2:0:0:0: [sdb] Starting disk
    [  102.791717] sd 5:0:0:0: [sdd] Starting disk
    [  102.926195] logitech-hidpp-device 0003:046D:2010.0004: HID++ 1.0 device connected.
    [  103.142445] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [  103.142469] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [  103.142499] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [  103.142521] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [  103.143261] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210930/psargs-330)
    [  103.143274] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20210930/psparse-529)
    [  103.143751] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20210930/psargs-330)
    [  103.143766] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20210930/psparse-529)
    [  103.144116] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20210930/psargs-330)
    [  103.144127] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20210930/psparse-529)
    [  103.144296] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210930/psargs-330)
    [  103.144312] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20210930/psparse-529)
    [  103.144430] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20210930/psargs-330)
    [  103.144441] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20210930/psparse-529)
    [  103.144459] ata1.00: supports DRM functions and may not be fully accessible
    [  103.144464] ata6.00: configured for UDMA/133
    [  103.145094] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20210930/psargs-330)
    [  103.145108] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20210930/psparse-529)
    [  103.145289] ata4.00: configured for UDMA/133
    [  103.145532] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20210930/psargs-330)
    [  103.145539] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20210930/psparse-529)
    [  103.145578] ata1.00: supports DRM functions and may not be fully accessible
    [  103.146397] ata1.00: configured for UDMA/133
    [  103.168424] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20210930/psargs-330)
    [  103.168439] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20210930/psparse-529)
    [  103.168696] ata3.00: configured for UDMA/133
    [  110.216231] OOM killer enabled.
    [  110.216234] Restarting tasks ... done.
    [  110.235499] video LNXVIDEO:00: Restoring backlight state
    [  110.235527] PM: suspend exit
    (The ACPI errors are all there with Siduction too)

    When trying to suspend with the other three cores manually suspended:


    Code:
    [  319.380769] ACPI: PM: Preparing to enter system sleep state S3
    [  319.381106] ACPI: PM: Saving platform NVS memory
    [  319.381131] Disabling non-boot CPUs ...
    [  319.381134] ACPI: PM: Waking up from system sleep state S3
    [  319.437012] sd 0:0:0:0: [sda] Starting disk
    [  319.437022] sd 3:0:0:0: [sdc] Starting disk
    [  319.437026] sd 5:0:0:0: [sdd] Starting disk
    [  319.437036] sd 2:0:0:0: [sdb] Starting disk
    [  319.786741] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [  319.786777] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [  319.786791] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [  319.786803] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    etc.


    Normal output when booting with maxcpus=0:

    Code:
    [  763.860722] PM: suspend entry (deep)
    [  764.308759] Filesystems sync: 0.448 seconds
    [  766.336548] Bluetooth: hci0: Timed out waiting for suspend events
    [  766.336553] Bluetooth: hci0: Suspend timeout bit: 6
    [  766.336561] Bluetooth: hci0: Suspend notifier action (3) failed: -110
    [  766.336567] Freezing user space processes ... (elapsed 0.003 seconds) done.
    [  766.340189] OOM killer disabled.
    [  766.340190] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [  766.341428] printk: Suspending console(s) (use no_console_suspend to debug)
    [  766.352581] sd 0:0:0:0: [sda] Synchronizing SCSI cache
    [  766.352593] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
    [  766.352598] sd 3:0:0:0: [sdc] Synchronizing SCSI cache
    [  766.352603] sd 5:0:0:0: [sdd] Synchronizing SCSI cache
    [  766.352707] sd 5:0:0:0: [sdd] Stopping disk
    [  766.352778] sd 2:0:0:0: [sdb] Stopping disk
    [  766.354500] sd 0:0:0:0: [sda] Stopping disk
    [  766.384795] sd 3:0:0:0: [sdc] Stopping disk
    [  771.520461] xpad 1-1.3:1.6: timed out waiting for output URB to complete, killing
    [  776.640372] xpad 1-1.3:1.4: timed out waiting for output URB to complete, killing
    [  781.760287] xpad 1-1.3:1.2: timed out waiting for output URB to complete, killing
    [  786.880191] xpad 1-1.3:1.0: timed out waiting for output URB to complete, killing
    [  786.984438] ACPI: PM: Preparing to enter system sleep state S3
    [  786.984775] ACPI: PM: Saving platform NVS memory
    [  786.984801] Disabling non-boot CPUs ...
    [  786.985276] ACPI: PM: Low-level resume complete
    [  786.985294] ACPI: PM: Restoring platform NVS memory
    [  786.986669] ACPI: PM: Waking up from system sleep state S3


    Other outputs that may be of interest:

    Code:
    cat/sys/power/state
    freeze mem disk
    
    Code:
    cat/sys/power/mem_sleep
    s2idle [deep]


    Code:
    lscpu
    
    Arquitetura:                  x86_64 
      Modo(s) operacional da CPU: 32-bit, 64-bit 
      Tamanhos de endereço:       36 bits physical, 48 bits virtual 
      Ordem dos bytes:            Little Endian 
    CPU(s):                       4 
      Lista de CPU(s) on-line:    0-3 
    ID de fornecedor:             GenuineIntel 
      ID de fornecedor da BIOS:   Intel 
      Nome do modelo:             Intel(R) Core(TM) i5-3450 CPU @ 3.10GHz 
        Nome do modelo da BIOS:   Intel(R) Core(TM) i5-3450 CPU @ 3.10GHz 
        Família da CPU:           6 
        Modelo:                   58 
        Thread(s) per núcleo:     1 
        Núcleo(s) por soquete:    4 
        Soquete(s):               1 
        Step:                     9 
        CPU MHz máx.:             3500,0000 
        CPU MHz mín.:             1600,0000 
        BogoMIPS:                 6185.89 
        Opções:                   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
                                   ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc  
                                  cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 p 
                                  opcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_sh 
                                  adow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d 
    Recursos de virtualização:     
      Virtualização:              VT-x 
    Caches (soma de todos):        
      L1d:                        128 KiB (4 instâncias) 
      L1i:                        128 KiB (4 instâncias) 
      L2:                         1 MiB (4 instâncias) 
      L3:                         6 MiB (1 instância) 
    NUMA:                          
      Nó(s) de NUMA:              1 
      CPU(s) de nó0 NUMA:         0-3 
    Vulnerabilidades:              
      Itlb multihit:              KVM: Mitigation: VMX disabled 
      L1tf:                       Mitigation; PTE Inversion; VMX conditional cache flushes, SMT disabled 
      Mds:                        Mitigation; Clear CPU buffers; SMT disabled 
      Meltdown:                   Mitigation; PTI 
      Spec store bypass:          Mitigation; Speculative Store Bypass disabled via prctl 
      Spectre v1:                 Mitigation; usercopy/swapgs barriers and __user pointer sanitization 
      Spectre v2:                 Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP disabled, RSB filling 
      Srbds:                      Vulnerable: No microcode 
      Tsx async abort:            Not affected
    
    Last edited by pedroh7; 25-Jan-2022 at 17:37. Reason: formatting

  2. #2
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    4,003
    Blog Entries
    1

    Default Re: Suspend-to-RAM fails with quadcore processor

    For troubleshooting purposes only, try suspending from an IceWM session. Most installations already have it installed. It's very lightweight.
    Reg. Linux User 211409 *** multibooting since 1992
    Primary: 15.3, TW, 15.1 & 13.1 on Haswell @earthlink.net
    Secondary: eComStation (OS/2) &15.2 on i965P/Radeon
    Tertiary: Debian, Fedora, Mageia, more on Rocket Lake & older Intel, AMD, NVidia....

  3. #3

    Default Re: Suspend-to-RAM fails with quadcore processor

    Quote Originally Posted by mrmazda View Post
    For troubleshooting purposes only, try suspending from an IceWM session. Most installations already have it installed. It's very lightweight.
    Tried. It doesn't work. Doesn't work in KDE (Wayland) either for that matter.

  4. #4

    Default Re: Suspend-to-RAM fails with quadcore processor

    Try to update BIOS (choose needed revision).

  5. #5
    Join Date
    May 2020
    Location
    Melbourne, FL, USA
    Posts
    14

    Question Re: Suspend-to-RAM fails with quadcore processor

    I have the same problem since doing a fresh install of Leap 15.3 using KDE. It is driving me crazy. System was sleeping/suspending fine using Leap 15.2 also KDE.

    AMD Ryzen Threadripper 1950X, Graphics card = EVGA GeoForce GTX 1060 (Nouveau drivers), Motherboard = Asus Prime X399-A

    The original poster knows a lot more about diagnostics than I do. I am a mere Physics Ph.D. just trying to get something done on my workstation.

    How to problem solve this???

    I also have an Intel HP laptop. That suspends fine.

    Parenthetically, with openSUSE fairly mature and aligning with SUSE Enterprise, why is a basic behavior like this a problem.

    I have seen this problem phase in and out since Leap 42 and Leap 15 started, but this is the worst.

    Thanks for any insight.

Tags for this Thread

Posting Permissions

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