laptop does not go to suspend anymore with kernel version > 5.16.10

laptop does not go to suspend anymore with kernel version > 5.16.10

[Reinhold Mannsberger]

Dear kernel developers!

I am using Linux Mint Xfce 20.3 with kernel version 5.16. I had to use
kernel 5.16 because with the standard kernel version of Linux mit 20.3
(which is 5.13) my laptop did not correctly resume, when I closed the
lid.

With kernel 5.16 my laptop perfectly went to to suspend when I closed
the lid and it perfectly resumed, when I opened the lid again. This
means: I had to press the power button once when I reopened the lid -
and then the laptop resumed (to the login screen). This was true until
kernel version 5.16.10. With kernel version > 5.16.10 my laptop does
not go into suspend anymore. This means: When I open the lid I am back
at the login screen immediately (I don't have to press the power button
anymore).

System information for my laptop:
----------------------------------------------------------------------
System:    Kernel: 5.16.10-051610-generic x86_64 bits: 64 compiler: N/A
Desktop: Xfce 4.16.0
           tk: Gtk 3.24.20 wm: xfwm4 dm: LightDM Distro: Linux Mint
20.3 Una
           base: Ubuntu 20.04 focal
Machine:   Type: Laptop System: HP product: HP ProBook 455 G8 Notebook
PC v: N/A serial: <filter>
           Chassis: type: 10 serial: <filter>
           Mobo: HP model: 8864 v: KBC Version 41.1E.00 serial:
<filter> UEFI: HP
           v: T78 Ver. 01.07.00 date: 10/08/2021
Battery:   ID-1: BAT0 charge: 43.8 Wh condition: 44.5/45.0 Wh (99%)
volts: 13.0/11.4
           model: Hewlett-Packard Primary serial: <filter> status:
Unknown
CPU:       Topology: 8-Core model: AMD Ryzen 7 5800U with Radeon
Graphics bits: 64 type: MT MCP
           arch: Zen 3 L2 cache: 4096 KiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm bogomips: 60685
           Speed: 3497 MHz min/max: 1600/1900 MHz Core speeds (MHz): 1:
3474 2: 3464 3: 3473
           4: 3471 5: 4362 6: 4332 7: 3478 8: 3455 9: 3459 10: 3452 11:
3462 12: 3468 13: 3468
           14: 3468 15: 3467 16: 3472
Graphics:  Device-1: AMD vendor: Hewlett-Packard driver: amdgpu v:
kernel bus ID: 05:00.0
           chip ID: 1002:1638
           Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati
unloaded: fbdev,modesetting,vesa
           resolution: 1920x1080~60Hz
           OpenGL: renderer: AMD RENOIR (DRM 3.44.0 5.16.10-051610-
generic LLVM 12.0.0)
           v: 4.6 Mesa 21.2.6 direct render: Yes
----------------------------------------------------------------------


Best regards,

Reinhold Mannsberger

Re: laptop does not go to suspend anymore with kernel version > 5.16.10

[Thorsten Leemhuis]

Hi!

On 08.03.22 19:21, Reinhold Mannsberger wrote:
> 
> I am using Linux Mint Xfce 20.3 with kernel version 5.16. I had to use
> kernel 5.16 because with the standard kernel version of Linux mit 20.3
> (which is 5.13) my laptop did not correctly resume, when I closed the
> lid.
> 
> With kernel 5.16 my laptop perfectly went to to suspend when I closed
> the lid and it perfectly resumed, when I opened the lid again. This
> means: I had to press the power button once

That sounds odd to me, as most modern Laptops wake up automatically when
you open the lid. It's unlikely, but maybe that just that started to
work now?

> when I reopened the lid -
> and then the laptop resumed (to the login screen). This was true until
> kernel version 5.16.10. With kernel version > 5.16.10 my laptop does
> not go into suspend anymore. This means: When I open the lid I am back
> at the login screen immediately (I don't have to press the power button
> anymore).

You want to check dmesg if the system really didn't go to sleep; it will
likely also provide a hint of what went wrong. Just upload the output
(generated after a fresh start and where you suspend and resume once the
system booted) somewhere and send us a link or sent it as an attachment
in a reply. If that doesn't provide any hints of what might be wrong,
you might need to find the change that introduced the problem using a
bisection.

HTH, Ciao, Thorsten

> System information for my laptop:
> ----------------------------------------------------------------------
> System:    Kernel: 5.16.10-051610-generic x86_64 bits: 64 compiler: N/A
> Desktop: Xfce 4.16.0
>            tk: Gtk 3.24.20 wm: xfwm4 dm: LightDM Distro: Linux Mint
> 20.3 Una
>            base: Ubuntu 20.04 focal
> Machine:   Type: Laptop System: HP product: HP ProBook 455 G8 Notebook
> PC v: N/A serial: <filter>
>            Chassis: type: 10 serial: <filter>
>            Mobo: HP model: 8864 v: KBC Version 41.1E.00 serial:
> <filter> UEFI: HP
>            v: T78 Ver. 01.07.00 date: 10/08/2021
> Battery:   ID-1: BAT0 charge: 43.8 Wh condition: 44.5/45.0 Wh (99%)
> volts: 13.0/11.4
>            model: Hewlett-Packard Primary serial: <filter> status:
> Unknown
> CPU:       Topology: 8-Core model: AMD Ryzen 7 5800U with Radeon
> Graphics bits: 64 type: MT MCP
>            arch: Zen 3 L2 cache: 4096 KiB
>            flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
> ssse3 svm bogomips: 60685
>            Speed: 3497 MHz min/max: 1600/1900 MHz Core speeds (MHz): 1:
> 3474 2: 3464 3: 3473
>            4: 3471 5: 4362 6: 4332 7: 3478 8: 3455 9: 3459 10: 3452 11:
> 3462 12: 3468 13: 3468
>            14: 3468 15: 3467 16: 3472
> Graphics:  Device-1: AMD vendor: Hewlett-Packard driver: amdgpu v:
> kernel bus ID: 05:00.0
>            chip ID: 1002:1638
>            Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati
> unloaded: fbdev,modesetting,vesa
>            resolution: 1920x1080~60Hz
>            OpenGL: renderer: AMD RENOIR (DRM 3.44.0 5.16.10-051610-
> generic LLVM 12.0.0)
>            v: 4.6 Mesa 21.2.6 direct render: Yes
> ----------------------------------------------------------------------
> 
> 
> Best regards,
> 
> Reinhold Mannsberger
> 
> 
> 

Re: laptop does not go to suspend anymore with kernel version > 5.16.10

[Reinhold Mannsberger]

[-- Attachment #1.1: Type: text/plain, Size: 4454 bytes --]

Dear Thorsten!

Thank you for your quick response!

Now that you gave me the advice to check dmesg I found out that the
messages are the same with kernel version 5.16.10 and 5.16.12. But - as
I described - with kernel version 5.16.10 I had to press the power
button to resume from suspend. So I my conclusion that my laptop does
not go to suspend ist apparently wrong. In any case you find excerpts
from dmesg with both kernel versions attached.

Now there is one thing I really would like to understand. Concluding
from the time stamps in dmesg it seems that my laptop goes to suspend
only for a moment right before I re-open the lid. Of course I did not
close my laptop lid only for 3 seconds - as it could be concluded from
the time stamps for "PM: suspend entry (s2idle)" and "PM: suspend exit"
- but for a longer period of time. Can you please enlighten me about
that?


Thank you and best regards,

Reinhold

Am Mittwoch, dem 09.03.2022 um 07:51 +0100 schrieb Thorsten Leemhuis:
> Hi!
>
> On 08.03.22 19:21, Reinhold Mannsberger wrote:
> >
> > I am using Linux Mint Xfce 20.3 with kernel version 5.16. I had to use
> > kernel 5.16 because with the standard kernel version of Linux mit 20.3
> > (which is 5.13) my laptop did not correctly resume, when I closed the
> > lid.
> >
> > With kernel 5.16 my laptop perfectly went to to suspend when I closed
> > the lid and it perfectly resumed, when I opened the lid again. This
> > means: I had to press the power button once
>
> That sounds odd to me, as most modern Laptops wake up automatically when
> you open the lid. It's unlikely, but maybe that just that started to
> work now?
>
> > when I reopened the lid -
> > and then the laptop resumed (to the login screen). This was true until
> > kernel version 5.16.10. With kernel version > 5.16.10 my laptop does
> > not go into suspend anymore. This means: When I open the lid I am back
> > at the login screen immediately (I don't have to press the power button
> > anymore).
>
> You want to check dmesg if the system really didn't go to sleep; it will
> likely also provide a hint of what went wrong. Just upload the output
> (generated after a fresh start and where you suspend and resume once the
> system booted) somewhere and send us a link or sent it as an attachment
> in a reply. If that doesn't provide any hints of what might be wrong,
> you might need to find the change that introduced the problem using a
> bisection.
>
> HTH, Ciao, Thorsten
>
> > System information for my laptop:
> > ----------------------------------------------------------------------
> > System:    Kernel: 5.16.10-051610-generic x86_64 bits: 64 compiler: N/A
> > Desktop: Xfce 4.16.0
> >            tk: Gtk 3.24.20 wm: xfwm4 dm: LightDM Distro: Linux Mint
> > 20.3 Una
> >            base: Ubuntu 20.04 focal
> > Machine:   Type: Laptop System: HP product: HP ProBook 455 G8 Notebook
> > PC v: N/A serial: <filter>
> >            Chassis: type: 10 serial: <filter>
> >            Mobo: HP model: 8864 v: KBC Version 41.1E.00 serial:
> > <filter> UEFI: HP
> >            v: T78 Ver. 01.07.00 date: 10/08/2021
> > Battery:   ID-1: BAT0 charge: 43.8 Wh condition: 44.5/45.0 Wh (99%)
> > volts: 13.0/11.4
> >            model: Hewlett-Packard Primary serial: <filter> status:
> > Unknown
> > CPU:       Topology: 8-Core model: AMD Ryzen 7 5800U with Radeon
> > Graphics bits: 64 type: MT MCP
> >            arch: Zen 3 L2 cache: 4096 KiB
> >            flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
> > ssse3 svm bogomips: 60685
> >            Speed: 3497 MHz min/max: 1600/1900 MHz Core speeds (MHz): 1:
> > 3474 2: 3464 3: 3473
> >            4: 3471 5: 4362 6: 4332 7: 3478 8: 3455 9: 3459 10: 3452 11:
> > 3462 12: 3468 13: 3468
> >            14: 3468 15: 3467 16: 3472
> > Graphics:  Device-1: AMD vendor: Hewlett-Packard driver: amdgpu v:
> > kernel bus ID: 05:00.0
> >            chip ID: 1002:1638
> >            Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati
> > unloaded: fbdev,modesetting,vesa
> >            resolution: 1920x1080~60Hz
> >            OpenGL: renderer: AMD RENOIR (DRM 3.44.0 5.16.10-051610-
> > generic LLVM 12.0.0)
> >            v: 4.6 Mesa 21.2.6 direct render: Yes
> > ----------------------------------------------------------------------
> >
> >
> > Best regards,
> >
> > Reinhold Mannsberger
> >
> >
> >

[-- Attachment #1.2: Type: text/html, Size: 5746 bytes --]

[-- Attachment #2: dmesg_kernel_5.16.10.txt --]
[-- Type: text/plain, Size: 4358 bytes --]

[    0.000000] Linux version 5.16.10-051610-generic (buildd@lcy02-amd64-032) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #202202181155-Ubuntu SMP PREEMPT Fri Feb 18 12:03:54 UTC 2022
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.16.10-051610-generic root=UUID=6362c232-c289-4af4-af9c-4306cee22589 ro quiet splash
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Hygon HygonGenuine
[    0.000000]   Centaur CentaurHauls
[    0.000000]   zhaoxin   Shanghai  
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:    8
[    0.000000] x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format.

...

[  128.688884] PM: suspend entry (s2idle)
[  128.691320] Filesystems sync: 0.002 seconds
[  130.703777] Bluetooth: hci0: Timed out waiting for suspend events
[  130.703787] Bluetooth: hci0: Suspend timeout bit: 9
[  130.703812] Bluetooth: hci0: Suspend notifier action (3) failed: -110
[  130.703818] Freezing user space processes ... (elapsed 0.002 seconds) done.
[  130.705930] OOM killer disabled.
[  130.705930] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[  130.707007] printk: Suspending console(s) (use no_console_suspend to debug)
[  131.025701] ACPI: EC: interrupt blocked
[  131.096541] ACPI: EC: interrupt unblocked
[  131.138242] pci 0000:00:00.2: can't derive routing for PCI INT A
[  131.138246] pci 0000:00:00.2: PCI INT A: no GSI
[  131.139933] [drm] PCIE GART of 1024M enabled.
[  131.139937] [drm] PTB located at 0x000000F400900000
[  131.139953] amdgpu 0000:05:00.0: amdgpu: SMU is resuming...
[  131.142131] amdgpu 0000:05:00.0: amdgpu: dpm has been disabled
[  131.143246] amdgpu 0000:05:00.0: amdgpu: SMU is resumed successfully!
[  131.143840] [drm] DMUB hardware initialized: version=0x0101000A
[  131.146112] nvme nvme0: 16/0/0 default/read/poll queues
[  131.236873] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[  131.237353] [drm] JPEG decode initialized successfully.
[  131.237365] amdgpu 0000:05:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[  131.237369] amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[  131.237372] amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[  131.237374] amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[  131.237377] amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[  131.237379] amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[  131.237380] amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[  131.237382] amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[  131.237384] amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[  131.237387] amdgpu 0000:05:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[  131.237388] amdgpu 0000:05:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
[  131.237390] amdgpu 0000:05:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
[  131.237391] amdgpu 0000:05:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
[  131.237393] amdgpu 0000:05:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
[  131.237394] amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
[  131.473931] usb 1-3: reset full-speed USB device number 2 using xhci_hcd
[  131.638355] OOM killer enabled.
[  131.638356] Restarting tasks ... 
[  131.639577] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822
[  131.640043] done.
[  131.641513] Bluetooth: hci0: RTL: rom_version status=0 version=3
[  131.641520] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin
[  131.641579] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin
[  131.641613] Bluetooth: hci0: RTL: cfg_sz 6, total sz 31422
[  131.643004] PM: suspend exit

[-- Attachment #3: dmesg_kernel_5.16.12.txt --]
[-- Type: text/plain, Size: 4341 bytes --]

[    0.000000] Linux version 5.16.12-051612-generic (buildd@lcy02-amd64-012) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #202203030915-Ubuntu SMP PREEMPT Thu Mar 3 09:22:23 UTC 2022
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.16.12-051612-generic root=UUID=6362c232-c289-4af4-af9c-4306cee22589 ro quiet splash
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Hygon HygonGenuine
[    0.000000]   Centaur CentaurHauls
[    0.000000]   zhaoxin   Shanghai  
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:    8
[    0.000000] x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format.

...

[ 3953.342132] PM: suspend entry (s2idle)
[ 3953.345140] Filesystems sync: 0.003 seconds
[ 3955.375058] Bluetooth: hci0: Timed out waiting for suspend events
[ 3955.375069] Bluetooth: hci0: Suspend timeout bit: 9
[ 3955.375095] Bluetooth: hci0: Suspend notifier action (3) failed: -110
[ 3955.375102] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 3955.377737] OOM killer disabled.
[ 3955.377738] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 3955.378880] printk: Suspending console(s) (use no_console_suspend to debug)
[ 3955.563201] ACPI: EC: interrupt blocked
[ 3955.632562] ACPI: EC: interrupt unblocked
[ 3955.675027] pci 0000:00:00.2: can't derive routing for PCI INT A
[ 3955.675034] pci 0000:00:00.2: PCI INT A: no GSI
[ 3955.676654] [drm] PCIE GART of 1024M enabled.
[ 3955.676657] [drm] PTB located at 0x000000F400900000
[ 3955.676667] amdgpu 0000:05:00.0: amdgpu: SMU is resuming...
[ 3955.678135] amdgpu 0000:05:00.0: amdgpu: dpm has been disabled
[ 3955.679302] amdgpu 0000:05:00.0: amdgpu: SMU is resumed successfully!
[ 3955.679896] [drm] DMUB hardware initialized: version=0x0101000A
[ 3955.683118] nvme nvme0: 16/0/0 default/read/poll queues
[ 3955.770943] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[ 3955.771402] [drm] JPEG decode initialized successfully.
[ 3955.771415] amdgpu 0000:05:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[ 3955.771420] amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 3955.771422] amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 3955.771423] amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 3955.771425] amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 3955.771426] amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 3955.771427] amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 3955.771429] amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 3955.771430] amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 3955.771432] amdgpu 0000:05:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[ 3955.771434] amdgpu 0000:05:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
[ 3955.771435] amdgpu 0000:05:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
[ 3955.771437] amdgpu 0000:05:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
[ 3955.771438] amdgpu 0000:05:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
[ 3955.771439] amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
[ 3956.013587] usb 1-3: reset full-speed USB device number 2 using xhci_hcd
[ 3956.179017] OOM killer enabled.
[ 3956.179020] Restarting tasks ... done.
[ 3956.182175] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822
[ 3956.184146] Bluetooth: hci0: RTL: rom_version status=0 version=3
[ 3956.184151] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin
[ 3956.184166] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin
[ 3956.184177] Bluetooth: hci0: RTL: cfg_sz 6, total sz 31422
[ 3956.184296] PM: suspend exit

Re: laptop does not go to suspend anymore with kernel version > 5.16.10

[Thorsten Leemhuis]

On 09.03.22 17:46, Reinhold Mannsberger wrote:
> Dear Thorsten!
> 
> Thank you for your quick response!
> 
> Now that you gave me the advice to check dmesg I found out that the
> messages are the same with kernel version 5.16.10 and 5.16.12. But - as
> I described - with kernel version 5.16.10 I had to press the power
> button to resume from suspend. So I my conclusion that my laptop does
> not go to suspend ist apparently wrong.

Good. :-D

> In any case you find excerpts
> from dmesg with both kernel versions attached.
> 
> Now there is one thing I really would like to understand. Concluding
> from the time stamps in dmesg it seems that my laptop goes to suspend
> only for a moment right before I re-open the lid. Of course I did not
> close my laptop lid only for 3 seconds - as it could be concluded from
> the time stamps for "PM: suspend entry (s2idle)" and "PM: suspend exit"
> - but for a longer period of time. Can you please enlighten me about that?

I have no idea, I'm just tracking regressions and sadly don't known much
about this. To me it looks a bit like s2idle is not working properly,
but I might be totally wrong with that. Maybe google might tell you; or
some measurements where you check how quickly the batter drains in
sleep. Oof you ask the PM developers -- but as this is not a regression
neither the regressions list nor the stable list care, so I guess you do
it in a separate mail.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.



> Am Mittwoch, dem 09.03.2022 um 07:51 +0100 schrieb Thorsten Leemhuis:
>> Hi!
>>
>> On 08.03.22 19:21, Reinhold Mannsberger wrote:
>>>
>>> I am using Linux Mint Xfce 20.3 with kernel version 5.16. I had to use
>>> kernel 5.16 because with the standard kernel version of Linux mit 20.3
>>> (which is 5.13) my laptop did not correctly resume, when I closed the
>>> lid.
>>>
>>> With kernel 5.16 my laptop perfectly went to to suspend when I closed
>>> the lid and it perfectly resumed, when I opened the lid again. This
>>> means: I had to press the power button once
>>
>> That sounds odd to me, as most modern Laptops wake up automatically when
>> you open the lid. It's unlikely, but maybe that just that started to
>> work now?
>>
>>> when I reopened the lid -
>>> and then the laptop resumed (to the login screen). This was true until
>>> kernel version 5.16.10. With kernel version > 5.16.10 my laptop does
>>> not go into suspend anymore. This means: When I open the lid I am back
>>> at the login screen immediately (I don't have to press the power button
>>> anymore).
>>
>> You want to check dmesg if the system really didn't go to sleep; it will
>> likely also provide a hint of what went wrong. Just upload the output
>> (generated after a fresh start and where you suspend and resume once the
>> system booted) somewhere and send us a link or sent it as an attachment
>> in a reply. If that doesn't provide any hints of what might be wrong,
>> you might need to find the change that introduced the problem using a
>> bisection.
>>
>> HTH, Ciao, Thorsten
>>
>>> System information for my laptop:
>>> ----------------------------------------------------------------------
>>> System:    Kernel: 5.16.10-051610-generic x86_64 bits: 64 compiler: N/A
>>> Desktop: Xfce 4.16.0
>>>            tk: Gtk 3.24.20 wm: xfwm4 dm: LightDM Distro: Linux Mint
>>> 20.3 Una
>>>            base: Ubuntu 20.04 focal
>>> Machine:   Type: Laptop System: HP product: HP ProBook 455 G8 Notebook
>>> PC v: N/A serial: <filter>
>>>            Chassis: type: 10 serial: <filter>
>>>            Mobo: HP model: 8864 v: KBC Version 41.1E.00 serial:
>>> <filter> UEFI: HP
>>>            v: T78 Ver. 01.07.00 date: 10/08/2021
>>> Battery:   ID-1: BAT0 charge: 43.8 Wh condition: 44.5/45.0 Wh (99%)
>>> volts: 13.0/11.4
>>>            model: Hewlett-Packard Primary serial: <filter> status:
>>> Unknown
>>> CPU:       Topology: 8-Core model: AMD Ryzen 7 5800U with Radeon
>>> Graphics bits: 64 type: MT MCP
>>>            arch: Zen 3 L2 cache: 4096 KiB
>>>            flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
>>> ssse3 svm bogomips: 60685
>>>            Speed: 3497 MHz min/max: 1600/1900 MHz Core speeds (MHz): 1:
>>> 3474 2: 3464 3: 3473
>>>            4: 3471 5: 4362 6: 4332 7: 3478 8: 3455 9: 3459 10: 3452 11:
>>> 3462 12: 3468 13: 3468
>>>            14: 3468 15: 3467 16: 3472
>>> Graphics:  Device-1: AMD vendor: Hewlett-Packard driver: amdgpu v:
>>> kernel bus ID: 05:00.0
>>>            chip ID: 1002:1638
>>>            Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati
>>> unloaded: fbdev,modesetting,vesa
>>>            resolution: 1920x1080~60Hz
>>>            OpenGL: renderer: AMD RENOIR (DRM 3.44.0 5.16.10-051610-
>>> generic LLVM 12.0.0)
>>>            v: 4.6 Mesa 21.2.6 direct render: Yes
>>> ----------------------------------------------------------------------
>>>
>>>
>>> Best regards,
>>>
>>> Reinhold Mannsberger
>>>
>>>
>>>

Re: laptop does not go to suspend anymore with kernel version > 5.16.10

[Thorsten Leemhuis]

On 09.03.22 18:18, Thorsten Leemhuis wrote:
> On 09.03.22 17:46, Reinhold Mannsberger wrote:
>> Dear Thorsten!
>>
>> Thank you for your quick response!
>>
>> Now that you gave me the advice to check dmesg I found out that the
>> messages are the same with kernel version 5.16.10 and 5.16.12. But - as
>> I described - with kernel version 5.16.10 I had to press the power
>> button to resume from suspend. So I my conclusion that my laptop does
>> not go to suspend ist apparently wrong.
> Good. :-D

Sorry, I might have drawn the wrong conclusions from the data you
provided, as it seems there is a problem that started with 5.16.10. See
this thread for details:

https://lore.kernel.org/all/31b9d1cd-6a67-218b-4ada-12f72e6f00dc@redhat.com/

>> In any case you find excerpts
>> from dmesg with both kernel versions attached.
>>
>> Now there is one thing I really would like to understand. Concluding
>> from the time stamps in dmesg it seems that my laptop goes to suspend
>> only for a moment right before I re-open the lid. Of course I did not
>> close my laptop lid only for 3 seconds - as it could be concluded from
>> the time stamps for "PM: suspend entry (s2idle)" and "PM: suspend exit"
>> - but for a longer period of time. Can you please enlighten me about that?
> 
> I have no idea, I'm just tracking regressions and sadly don't known much
> about this. To me it looks a bit like s2idle is not working properly,
> but I might be totally wrong with that. Maybe google might tell you; or
> some measurements where you check how quickly the batter drains in
> sleep. Oof you ask the PM developers -- but as this is not a regression
> neither the regressions list nor the stable list care, so I guess you do
> it in a separate mail.
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> 
> P.S.: As the Linux kernel's regression tracker I'm getting a lot of
> reports on my table. I can only look briefly into most of them and lack
> knowledge about most of the areas they concern. I thus unfortunately
> will sometimes get things wrong or miss something important. I hope
> that's not the case here; if you think it is, don't hesitate to tell me
> in a public reply, it's in everyone's interest to set the public record
> straight.
> 
> 
> 
>> Am Mittwoch, dem 09.03.2022 um 07:51 +0100 schrieb Thorsten Leemhuis:
>>> Hi!
>>>
>>> On 08.03.22 19:21, Reinhold Mannsberger wrote:
>>>>
>>>> I am using Linux Mint Xfce 20.3 with kernel version 5.16. I had to use
>>>> kernel 5.16 because with the standard kernel version of Linux mit 20.3
>>>> (which is 5.13) my laptop did not correctly resume, when I closed the
>>>> lid.
>>>>
>>>> With kernel 5.16 my laptop perfectly went to to suspend when I closed
>>>> the lid and it perfectly resumed, when I opened the lid again. This
>>>> means: I had to press the power button once
>>>
>>> That sounds odd to me, as most modern Laptops wake up automatically when
>>> you open the lid. It's unlikely, but maybe that just that started to
>>> work now?
>>>
>>>> when I reopened the lid -
>>>> and then the laptop resumed (to the login screen). This was true until
>>>> kernel version 5.16.10. With kernel version > 5.16.10 my laptop does
>>>> not go into suspend anymore. This means: When I open the lid I am back
>>>> at the login screen immediately (I don't have to press the power button
>>>> anymore).
>>>
>>> You want to check dmesg if the system really didn't go to sleep; it will
>>> likely also provide a hint of what went wrong. Just upload the output
>>> (generated after a fresh start and where you suspend and resume once the
>>> system booted) somewhere and send us a link or sent it as an attachment
>>> in a reply. If that doesn't provide any hints of what might be wrong,
>>> you might need to find the change that introduced the problem using a
>>> bisection.
>>>
>>> HTH, Ciao, Thorsten
>>>
>>>> System information for my laptop:
>>>> ----------------------------------------------------------------------
>>>> System:    Kernel: 5.16.10-051610-generic x86_64 bits: 64 compiler: N/A
>>>> Desktop: Xfce 4.16.0
>>>>            tk: Gtk 3.24.20 wm: xfwm4 dm: LightDM Distro: Linux Mint
>>>> 20.3 Una
>>>>            base: Ubuntu 20.04 focal
>>>> Machine:   Type: Laptop System: HP product: HP ProBook 455 G8 Notebook
>>>> PC v: N/A serial: <filter>
>>>>            Chassis: type: 10 serial: <filter>
>>>>            Mobo: HP model: 8864 v: KBC Version 41.1E.00 serial:
>>>> <filter> UEFI: HP
>>>>            v: T78 Ver. 01.07.00 date: 10/08/2021
>>>> Battery:   ID-1: BAT0 charge: 43.8 Wh condition: 44.5/45.0 Wh (99%)
>>>> volts: 13.0/11.4
>>>>            model: Hewlett-Packard Primary serial: <filter> status:
>>>> Unknown
>>>> CPU:       Topology: 8-Core model: AMD Ryzen 7 5800U with Radeon
>>>> Graphics bits: 64 type: MT MCP
>>>>            arch: Zen 3 L2 cache: 4096 KiB
>>>>            flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
>>>> ssse3 svm bogomips: 60685
>>>>            Speed: 3497 MHz min/max: 1600/1900 MHz Core speeds (MHz): 1:
>>>> 3474 2: 3464 3: 3473
>>>>            4: 3471 5: 4362 6: 4332 7: 3478 8: 3455 9: 3459 10: 3452 11:
>>>> 3462 12: 3468 13: 3468
>>>>            14: 3468 15: 3467 16: 3472
>>>> Graphics:  Device-1: AMD vendor: Hewlett-Packard driver: amdgpu v:
>>>> kernel bus ID: 05:00.0
>>>>            chip ID: 1002:1638
>>>>            Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati
>>>> unloaded: fbdev,modesetting,vesa
>>>>            resolution: 1920x1080~60Hz
>>>>            OpenGL: renderer: AMD RENOIR (DRM 3.44.0 5.16.10-051610-
>>>> generic LLVM 12.0.0)
>>>>            v: 4.6 Mesa 21.2.6 direct render: Yes
>>>> ----------------------------------------------------------------------
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> Reinhold Mannsberger
>>>>
>>>>
>>>>
> 
>