s2idle on kdell xps 9730 does go to sleep but laptop is warm

s2idle on kdell xps 9730 does go to sleep but laptop is warm

[Marc MERLIN]

and burn a lot of battery during full kernel sleep
Reply-To: 
X-Sysadmin: BOFH
X-URL: http://marc.merlins.org/

 With kernel 6.6.9 when I put the laptop to sleep, syslog shows that the
 laptop was sleeping for 9h, fans were stopped, but when I gabbed my
 laptop it was warm and burned 80% of the battery overnight.

And yet, linux was not running, my logs show the kernel went into ACPI
sleep and back out

Logs show the system slept for 9h and went to sleep with s2idle.

Is it the wrong sleep outside of suspend to disk and full shutdown?

Are there devices that should have been powered off but didn't
(evidently yes since battery loss was 80% and laptop was warm)

logs below

2025-05-14T00:01:20 merlin root: >>>>>>>>>> suspend  #1 1747206080

2025-05-14T00:01:21 merlin dbus-daemon[2846]: [system] Activating via systemd: service name='org.wicd.daemon' unit='dbus-org.wicd.daemon.service' requested by ':1.1130' (uid=0 pid=3357435 comm="/usr/bin/python3 /usr/share/wicd/daemon/suspend.py")
2025-05-14T00:01:21 merlin dbus-daemon[2846]: [system] Activation via systemd failed for unit 'dbus-org.wicd.daemon.service': Unit dbus-org.wicd.daemon.service not found.
2025-05-14T00:01:21 merlin kernel: [1388664.621668] PM: suspend entry (s2idle)
2025-05-14T00:01:21 merlin kernel: [1388664.625122] Filesystems sync: 0.003 seconds
2025-05-14T09:20:43 merlin kernel: [1388664.635518] Freezing user space processes
2025-05-14T09:20:43 merlin kernel: [1388664.638313] Freezing user space processes completed (elapsed 0.002 seconds)
2025-05-14T09:20:43 merlin kernel: [1388664.638320] OOM killer disabled.
2025-05-14T09:20:43 merlin kernel: [1388664.638322] Freezing remaining freezable tasks
2025-05-14T09:20:43 merlin kernel: [1388664.640285] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
2025-05-14T09:20:43 merlin kernel: [1388664.640290] printk: Suspending console(s) (use no_console_suspend to debug)
(...)
2025-05-14T09:20:43 merlin kernel: [1422225.195325] OOM killer enabled.
2025-05-14T09:20:43 merlin kernel: [1422225.195328] Restarting tasks ... done.
2025-05-14T09:20:43 merlin kernel: [1422225.204356] vgaarb: client 0x00000000f7b9cd5c called 'target'
2025-05-14T09:20:43 merlin kernel: [1422225.204376] vgaarb: PCI:0000:00:02.0 ==> 0000:00:02.0 pdev 00000000dec5b5e7
2025-05-14T09:20:43 merlin kernel: [1422225.204383] vgaarb: vgadev 00000000dca48b8a
2025-05-14T09:20:43 merlin kernel: [1422225.321870] PM: suspend exit

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
 
Home page: http://marc.merlins.org/                       | PGP 7F55D5F27AAF9D08

Re: s2idle on kdell xps 9730 does go to sleep but laptop is warm

[Marc MERLIN]

This is still a problem. Is there more info I can provide? For now it's
bad enough that I can't have the battery be in S3 sleep for 24H without
the batteries running out :-/

On Thu, May 15, 2025 at 12:45:23AM -0700, Marc MERLIN wrote:
> and burn a lot of battery during full kernel sleep
> Reply-To: 
> X-Sysadmin: BOFH
> X-URL: http://marc.merlins.org/
> 
>  With kernel 6.6.9 when I put the laptop to sleep, syslog shows that the
>  laptop was sleeping for 9h, fans were stopped, but when I gabbed my
>  laptop it was warm and burned 80% of the battery overnight.
> 
> And yet, linux was not running, my logs show the kernel went into ACPI
> sleep and back out
> 
> Logs show the system slept for 9h and went to sleep with s2idle.
> 
> Is it the wrong sleep outside of suspend to disk and full shutdown?
> 
> Are there devices that should have been powered off but didn't
> (evidently yes since battery loss was 80% and laptop was warm)
> 
> logs below
> 
> 2025-05-14T00:01:20 merlin root: >>>>>>>>>> suspend  #1 1747206080
> 
> 2025-05-14T00:01:21 merlin dbus-daemon[2846]: [system] Activating via systemd: service name='org.wicd.daemon' unit='dbus-org.wicd.daemon.service' requested by ':1.1130' (uid=0 pid=3357435 comm="/usr/bin/python3 /usr/share/wicd/daemon/suspend.py")
> 2025-05-14T00:01:21 merlin dbus-daemon[2846]: [system] Activation via systemd failed for unit 'dbus-org.wicd.daemon.service': Unit dbus-org.wicd.daemon.service not found.
> 2025-05-14T00:01:21 merlin kernel: [1388664.621668] PM: suspend entry (s2idle)
> 2025-05-14T00:01:21 merlin kernel: [1388664.625122] Filesystems sync: 0.003 seconds
> 2025-05-14T09:20:43 merlin kernel: [1388664.635518] Freezing user space processes
> 2025-05-14T09:20:43 merlin kernel: [1388664.638313] Freezing user space processes completed (elapsed 0.002 seconds)
> 2025-05-14T09:20:43 merlin kernel: [1388664.638320] OOM killer disabled.
> 2025-05-14T09:20:43 merlin kernel: [1388664.638322] Freezing remaining freezable tasks
> 2025-05-14T09:20:43 merlin kernel: [1388664.640285] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
> 2025-05-14T09:20:43 merlin kernel: [1388664.640290] printk: Suspending console(s) (use no_console_suspend to debug)
> (...)
> 2025-05-14T09:20:43 merlin kernel: [1422225.195325] OOM killer enabled.
> 2025-05-14T09:20:43 merlin kernel: [1422225.195328] Restarting tasks ... done.
> 2025-05-14T09:20:43 merlin kernel: [1422225.204356] vgaarb: client 0x00000000f7b9cd5c called 'target'
> 2025-05-14T09:20:43 merlin kernel: [1422225.204376] vgaarb: PCI:0000:00:02.0 ==> 0000:00:02.0 pdev 00000000dec5b5e7
> 2025-05-14T09:20:43 merlin kernel: [1422225.204383] vgaarb: vgadev 00000000dca48b8a
> 2025-05-14T09:20:43 merlin kernel: [1422225.321870] PM: suspend exit
> 
> Thanks,
> Marc
> -- 
> "A mouse is a device used to point at the xterm you want to type in" - A.S.R.
>  
> Home page: http://marc.merlins.org/                       | PGP 7F55D5F27AAF9D08
> 

-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
 
Home page: http://marc.merlins.org/                       | PGP 7F55D5F27AAF9D08

Re: s2idle on kdell xps 9730 does go to sleep but laptop is warm

[Theodore Ts'o]

On Sat, May 31, 2025 at 02:26:32PM -0700, Marc MERLIN wrote:
> This is still a problem. Is there more info I can provide? For now it's
> bad enough that I can't have the battery be in S3 sleep for 24H without
> the batteries running out :-/

I believe what is going on is that on more modern systems, it relies
on the OS's drivers to power done various peripherals (e.g., graphics,
SSD's, etc.) and this is no longer being done by the low-level
firmware.  With Linux the CPU is put to sleep, but there's a lot more
on a modern mainboard than just the CPU....

My solution, two tears ago, was to give up on my Dell XPS 13, and I
switched to a M2 MacBook Air, and I run (arm64) Linux in a Parallels
VM.

Sigh....

							- Ted

Re: s2idle on kdell xps 9730 does go to sleep but laptop is warm

[Marc MERLIN]

On Sat, May 31, 2025 at 07:16:26PM -0400, Theodore Ts'o wrote:
> On Sat, May 31, 2025 at 02:26:32PM -0700, Marc MERLIN wrote:
> > This is still a problem. Is there more info I can provide? For now it's
> > bad enough that I can't have the battery be in S3 sleep for 24H without
> > the batteries running out :-/
> 
> I believe what is going on is that on more modern systems, it relies
> on the OS's drivers to power done various peripherals (e.g., graphics,
> SSD's, etc.) and this is no longer being done by the low-level
> firmware.  With Linux the CPU is put to sleep, but there's a lot more
> on a modern mainboard than just the CPU....

Hi Ted, nice to hear from you.  Yes, I agree that what you wrote totally
matches my experience and the reason why the laptop was so warm, even in
sleep mode.

So, given that this is not a new problem, are there any new options in
linux drivers and/or kernel options to have linux do this (shut down
each subsystem)?

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
 
Home page: http://marc.merlins.org/                       | PGP 7F55D5F27AAF9D08

Re: s2idle on kdell xps 9730 does go to sleep but laptop is warm

[Rafael J. Wysocki]

On Thu, May 15, 2025 at 9:45 AM Marc MERLIN <marc@merlins.org> wrote:
>
> and burn a lot of battery during full kernel sleep
> Reply-To:
> X-Sysadmin: BOFH
> X-URL: http://marc.merlins.org/
>
>  With kernel 6.6.9 when I put the laptop to sleep, syslog shows that the
>  laptop was sleeping for 9h, fans were stopped, but when I gabbed my
>  laptop it was warm and burned 80% of the battery overnight.

First off, I'd try a newer kernel.  Say 6.15.0 (unless you boot with
"nosmt" in the kernel command line).

> And yet, linux was not running, my logs show the kernel went into ACPI
> sleep and back out

It wouldn't be "ACPI sleep" if it was suspend-to-idle.

> Logs show the system slept for 9h and went to sleep with s2idle.
>
> Is it the wrong sleep outside of suspend to disk and full shutdown?

No, it shouldn't be.

> Are there devices that should have been powered off but didn't
> (evidently yes since battery loss was 80% and laptop was warm)

There seems to be driver support missing for some devices.

> logs below
>
> 2025-05-14T00:01:20 merlin root: >>>>>>>>>> suspend  #1 1747206080
>
> 2025-05-14T00:01:21 merlin dbus-daemon[2846]: [system] Activating via systemd: service name='org.wicd.daemon' unit='dbus-org.wicd.daemon.service' requested by ':1.1130' (uid=0 pid=3357435 comm="/usr/bin/python3 /usr/share/wicd/daemon/suspend.py")
> 2025-05-14T00:01:21 merlin dbus-daemon[2846]: [system] Activation via systemd failed for unit 'dbus-org.wicd.daemon.service': Unit dbus-org.wicd.daemon.service not found.
> 2025-05-14T00:01:21 merlin kernel: [1388664.621668] PM: suspend entry (s2idle)
> 2025-05-14T00:01:21 merlin kernel: [1388664.625122] Filesystems sync: 0.003 seconds
> 2025-05-14T09:20:43 merlin kernel: [1388664.635518] Freezing user space processes
> 2025-05-14T09:20:43 merlin kernel: [1388664.638313] Freezing user space processes completed (elapsed 0.002 seconds)
> 2025-05-14T09:20:43 merlin kernel: [1388664.638320] OOM killer disabled.
> 2025-05-14T09:20:43 merlin kernel: [1388664.638322] Freezing remaining freezable tasks
> 2025-05-14T09:20:43 merlin kernel: [1388664.640285] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
> 2025-05-14T09:20:43 merlin kernel: [1388664.640290] printk: Suspending console(s) (use no_console_suspend to debug)
> (...)
> 2025-05-14T09:20:43 merlin kernel: [1422225.195325] OOM killer enabled.
> 2025-05-14T09:20:43 merlin kernel: [1422225.195328] Restarting tasks ... done.
> 2025-05-14T09:20:43 merlin kernel: [1422225.204356] vgaarb: client 0x00000000f7b9cd5c called 'target'
> 2025-05-14T09:20:43 merlin kernel: [1422225.204376] vgaarb: PCI:0000:00:02.0 ==> 0000:00:02.0 pdev 00000000dec5b5e7
> 2025-05-14T09:20:43 merlin kernel: [1422225.204383] vgaarb: vgadev 00000000dca48b8a
> 2025-05-14T09:20:43 merlin kernel: [1422225.321870] PM: suspend exit

Well, it obviously is not a complete log.

What processor is there in your system?

Re: s2idle on kdell xps 9730 does go to sleep but laptop is warm

[Marc MERLIN]

On Mon, Jun 02, 2025 at 04:23:42PM +0200, Rafael J. Wysocki wrote:
> >  With kernel 6.6.9 when I put the laptop to sleep, syslog shows that the
> >  laptop was sleeping for 9h, fans were stopped, but when I gabbed my
> >  laptop it was warm and burned 80% of the battery overnight.
> 
> First off, I'd try a newer kernel.  Say 6.15.0 (unless you boot with
> "nosmt" in the kernel command line).
 
Fair point, I somehow failed to upgrade the kernel on that machine.
I have a 6.14.5 kernel I just installed.

I also upgraded all firmware:
dpkggrep firmware | awk '{ print $1 }' | xargs apt-get install -t unstable  -y

> > And yet, linux was not running, my logs show the kernel went into ACPI
> > sleep and back out
> 
> It wouldn't be "ACPI sleep" if it was suspend-to-idle.

My thinkpad has:
sauron:~# cat /sys/power/mem_sleep
s2idle [deep]

The Dell XPS only has:
merlin:/usr/src# cat /sys/power/mem_sleep
[s2idle]

> What processor is there in your system?

model name      : 13th Gen Intel(R) Core(TM) i7-13700H

> Well, it obviously is not a complete log.

Ok, I tested again with the new kernel. The laptop didn't feel warm when
in sleep, but I lost 20% battery in 4H, which means the battery would
not last 24H in sleep

For logs, which one did you want?  I have pretty full logs here:
https://marc.merlins.org/tmp/merlin-sleep-6.14.5_dmesg.txt
https://marc.merlins.org/tmp/merlin-sleep-6.14.5_acpi.txt

One thing I changed recently is that unloading wireless altogether,
causes issues at times, so now I have
rfkill block wlan
instead of
killall wpa_supplicant &>/dev/null
pkill -f "dhclient.*wlan0"
ifconfig -a | grep -q wlan0 && ifconfig wlan0 down
rmmod iwlmvm
rmmod iwlwifi iwlagn iwlcore
rmmod ieee80211
rmmod ieee80211_crypt_wep 2>/dev/null
rmmod ieee80211_crypt_tkip 2>/dev/null
rmmod ieee80211_crypt 2>/dev/null
rmmod mac80211 2>/dev/null
rmmod cfg80211 2>/dev/null

This bit of dmesg just before sleep may be relevant:
[  226.365652] thunderbolt 0000:00:0d.2: save config 0x34: 0x00000080
[  226.365654] thunderbolt 0000:00:0d.3: save config 0x2c: 0x0bda1028
[  226.365655] thunderbolt 0000:00:0d.2: save config 0x38: 0x00000000
[  226.365656] thunderbolt 0000:00:0d.3: save config 0x30: 0x00000000
[  226.365657] thunderbolt 0000:00:0d.2: save config 0x3c: 0x000001ff
[  226.365659] thunderbolt 0000:00:0d.3: save config 0x34: 0x00000080
[  226.365661] thunderbolt 0000:00:0d.3: save config 0x38: 0x00000000
[  226.365663] thunderbolt 0000:00:0d.3: save config 0x3c: 0x000001ff
[  226.366245] thunderbolt 0000:00:0d.2: PME# enabled
[  226.366424] thunderbolt 0000:00:0d.3: PME# enabled
[  226.370305] pcieport 10000:e0:06.2: PCI PM: Suspend power state: D3hot
[  226.370328] pcieport 10000:e0:06.0: PCI PM: Suspend power state: D3hot
[  226.370539] vmd 0000:00:0e.0: save config 0x00: 0xa77f8086
[  226.370551] vmd 0000:00:0e.0: save config 0x04: 0x00100406
[  226.370555] vmd 0000:00:0e.0: save config 0x08: 0x01040000
[  226.370560] vmd 0000:00:0e.0: save config 0x0c: 0x00800000
[  226.370565] vmd 0000:00:0e.0: save config 0x10: 0x02000004
[  226.370575] vmd 0000:00:0e.0: save config 0x14: 0x00000062
[  226.370581] vmd 0000:00:0e.0: save config 0x18: 0x72000000
[  226.370587] vmd 0000:00:0e.0: save config 0x1c: 0x00000000
[  226.370592] vmd 0000:00:0e.0: save config 0x20: 0x07900004
[  226.370596] vmd 0000:00:0e.0: save config 0x24: 0x00000062
[  226.370600] vmd 0000:00:0e.0: save config 0x28: 0x00000000
[  226.370603] vmd 0000:00:0e.0: save config 0x2c: 0x0bda1028
[  226.370607] vmd 0000:00:0e.0: save config 0x30: 0x00000000
[  226.370611] vmd 0000:00:0e.0: save config 0x34: 0x00000080
[  226.370615] vmd 0000:00:0e.0: save config 0x38: 0x00000000
[  226.370620] vmd 0000:00:0e.0: save config 0x3c: 0x00000000
[  226.375481] intel-lpss 0000:00:15.1: ACPI _REG disconnect evaluation failed (5)
[  226.375487] mei_me 0000:00:16.0: PCI PM: Suspend power state: D3hot
[  226.375908] intel-lpss 0000:00:15.0: ACPI _REG disconnect evaluation failed (5)
[  226.376162] proc_thermal_pci 0000:00:04.0: PCI PM: Suspend power state: D3hot
[  226.377183] intel-lpss 0000:00:15.1: power state changed by ACPI to D3hot
[  226.377277] intel-lpss 0000:00:15.1: PCI PM: Suspend power state: D3hot
[  226.377771] intel-lpss 0000:00:15.0: power state changed by ACPI to D3hot
[  226.378257] rtsx_pci 0000:06:00.0: PCI PM: Suspend power state: D3hot
[  226.378422] intel-lpss 0000:00:15.0: PCI PM: Suspend power state: D3hot
[  226.378448] pcieport 0000:00:1c.0: save config 0x00: 0x51bb8086
[  226.378607] pcieport 0000:00:1c.0: save config 0x04: 0x00100407
[  226.378656] pcieport 0000:00:1c.0: save config 0x08: 0x06040001
[  226.378707] pcieport 0000:00:1c.0: save config 0x0c: 0x00810000
[  226.378758] pcieport 0000:00:1c.0: save config 0x10: 0x00000000
[  226.378782] pcieport 0000:00:1c.0: save config 0x14: 0x00000000
[  226.378806] pcieport 0000:00:1c.0: save config 0x18: 0x00060600
[  226.378830] pcieport 0000:00:1c.0: save config 0x1c: 0x000000f0
[  226.378853] pcieport 0000:00:1c.0: save config 0x20: 0x75007500
[  226.378877] pcieport 0000:00:1c.0: save config 0x24: 0x0001fff1
[  226.378899] pcieport 0000:00:1c.0: save config 0x28: 0x00000000
[  226.378905] pcieport 0000:00:1c.0: save config 0x2c: 0x00000000
[  226.378935] pcieport 0000:00:1c.0: save config 0x30: 0x00000000
[  226.378958] pcieport 0000:00:1c.0: save config 0x34: 0x00000040
[  226.378982] pcieport 0000:00:1c.0: save config 0x38: 0x00000000
[  226.379006] pcieport 0000:00:1c.0: save config 0x3c: 0x000204ff
[  226.379534] pcieport 0000:00:1c.0: PME# enabled
[  226.379589] thunderbolt 0000:00:0d.2: ACPI _REG disconnect evaluation failed (5)
[  226.380218] xhci_hcd 0000:00:0d.0: ACPI _REG disconnect evaluation failed (5)
[  226.381101] thunderbolt 0000:00:0d.3: ACPI _REG disconnect evaluation failed (5)
[  226.382316] iwlwifi 0000:00:14.3: power state changed by ACPI to D3hot
[  226.382528] iwlwifi 0000:00:14.3: PCI PM: Suspend power state: D3hot
[  226.383140] vmd 0000:00:0e.0: ACPI _REG disconnect evaluation failed (5)
[  226.384467] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3hot
[  226.384574] xhci_hcd 0000:00:14.0: PCI PM: Suspend power state: D3hot
[  226.384813] vmd 0000:00:0e.0: power state changed by ACPI to D3hot
[  226.384825] vmd 0000:00:0e.0: PCI PM: Suspend power state: D3hot
[  226.385180] xhci_hcd 0000:00:0d.0: power state changed by ACPI to D3cold
[  226.385191] xhci_hcd 0000:00:0d.0: PCI PM: Suspend power state: D3cold
[  226.391528] pcieport 0000:00:1c.0: ACPI _REG disconnect evaluation failed (5)
[  226.392369] pcieport 0000:00:1c.0: power state changed by ACPI to D3hot
[  226.392484] pcieport 0000:00:1c.0: PCI PM: Suspend power state: D3hot
[  226.395162] thunderbolt 0000:00:0d.2: power state changed by ACPI to D3cold
[  226.395172] thunderbolt 0000:00:0d.2: PCI PM: Suspend power state: D3cold
[  226.396283] thunderbolt 0000:00:0d.3: power state changed by ACPI to D3cold
[  226.396291] thunderbolt 0000:00:0d.3: PCI PM: Suspend power state: D3cold
[14916.770339] ACPI: EC: interrupt unblocked

-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
 
Home page: http://marc.merlins.org/                       | PGP 7F55D5F27AAF9D08

Re: s2idle on kdell xps 9730 does go to sleep but laptop is warm

[Marc MERLIN]

Were the logs I gave useful in any way, or just confirm that it's just
some new-ish laptop (2 years old now) that sadly does things in ways
that don't work well with linux?

https://marc.merlins.org/tmp/merlin-sleep-6.14.5_dmesg.txt
https://marc.merlins.org/tmp/merlin-sleep-6.14.5_acpi.txt


On Mon, Jun 02, 2025 at 01:56:13PM -0700, Marc MERLIN wrote:
> On Mon, Jun 02, 2025 at 04:23:42PM +0200, Rafael J. Wysocki wrote:
> > >  With kernel 6.6.9 when I put the laptop to sleep, syslog shows that the
> > >  laptop was sleeping for 9h, fans were stopped, but when I gabbed my
> > >  laptop it was warm and burned 80% of the battery overnight.
> > 
> > First off, I'd try a newer kernel.  Say 6.15.0 (unless you boot with
> > "nosmt" in the kernel command line).
>  
> Fair point, I somehow failed to upgrade the kernel on that machine.
> I have a 6.14.5 kernel I just installed.
> 
> I also upgraded all firmware:
> dpkggrep firmware | awk '{ print $1 }' | xargs apt-get install -t unstable  -y
> 
> > > And yet, linux was not running, my logs show the kernel went into ACPI
> > > sleep and back out
> > 
> > It wouldn't be "ACPI sleep" if it was suspend-to-idle.
> 
> My thinkpad has:
> sauron:~# cat /sys/power/mem_sleep
> s2idle [deep]
> 
> The Dell XPS only has:
> merlin:/usr/src# cat /sys/power/mem_sleep
> [s2idle]
> 
> > What processor is there in your system?
> 
> model name      : 13th Gen Intel(R) Core(TM) i7-13700H
> 
> > Well, it obviously is not a complete log.
> 
> Ok, I tested again with the new kernel. The laptop didn't feel warm when
> in sleep, but I lost 20% battery in 4H, which means the battery would
> not last 24H in sleep
> 
> For logs, which one did you want?  I have pretty full logs here:
> https://marc.merlins.org/tmp/merlin-sleep-6.14.5_dmesg.txt
> https://marc.merlins.org/tmp/merlin-sleep-6.14.5_acpi.txt
> 
> One thing I changed recently is that unloading wireless altogether,
> causes issues at times, so now I have
> rfkill block wlan
> instead of
> killall wpa_supplicant &>/dev/null
> pkill -f "dhclient.*wlan0"
> ifconfig -a | grep -q wlan0 && ifconfig wlan0 down
> rmmod iwlmvm
> rmmod iwlwifi iwlagn iwlcore
> rmmod ieee80211
> rmmod ieee80211_crypt_wep 2>/dev/null
> rmmod ieee80211_crypt_tkip 2>/dev/null
> rmmod ieee80211_crypt 2>/dev/null
> rmmod mac80211 2>/dev/null
> rmmod cfg80211 2>/dev/null
> 
> This bit of dmesg just before sleep may be relevant:
> [  226.365652] thunderbolt 0000:00:0d.2: save config 0x34: 0x00000080
> [  226.365654] thunderbolt 0000:00:0d.3: save config 0x2c: 0x0bda1028
> [  226.365655] thunderbolt 0000:00:0d.2: save config 0x38: 0x00000000
> [  226.365656] thunderbolt 0000:00:0d.3: save config 0x30: 0x00000000
> [  226.365657] thunderbolt 0000:00:0d.2: save config 0x3c: 0x000001ff
> [  226.365659] thunderbolt 0000:00:0d.3: save config 0x34: 0x00000080
> [  226.365661] thunderbolt 0000:00:0d.3: save config 0x38: 0x00000000
> [  226.365663] thunderbolt 0000:00:0d.3: save config 0x3c: 0x000001ff
> [  226.366245] thunderbolt 0000:00:0d.2: PME# enabled
> [  226.366424] thunderbolt 0000:00:0d.3: PME# enabled
> [  226.370305] pcieport 10000:e0:06.2: PCI PM: Suspend power state: D3hot
> [  226.370328] pcieport 10000:e0:06.0: PCI PM: Suspend power state: D3hot
> [  226.370539] vmd 0000:00:0e.0: save config 0x00: 0xa77f8086
> [  226.370551] vmd 0000:00:0e.0: save config 0x04: 0x00100406
> [  226.370555] vmd 0000:00:0e.0: save config 0x08: 0x01040000
> [  226.370560] vmd 0000:00:0e.0: save config 0x0c: 0x00800000
> [  226.370565] vmd 0000:00:0e.0: save config 0x10: 0x02000004
> [  226.370575] vmd 0000:00:0e.0: save config 0x14: 0x00000062
> [  226.370581] vmd 0000:00:0e.0: save config 0x18: 0x72000000
> [  226.370587] vmd 0000:00:0e.0: save config 0x1c: 0x00000000
> [  226.370592] vmd 0000:00:0e.0: save config 0x20: 0x07900004
> [  226.370596] vmd 0000:00:0e.0: save config 0x24: 0x00000062
> [  226.370600] vmd 0000:00:0e.0: save config 0x28: 0x00000000
> [  226.370603] vmd 0000:00:0e.0: save config 0x2c: 0x0bda1028
> [  226.370607] vmd 0000:00:0e.0: save config 0x30: 0x00000000
> [  226.370611] vmd 0000:00:0e.0: save config 0x34: 0x00000080
> [  226.370615] vmd 0000:00:0e.0: save config 0x38: 0x00000000
> [  226.370620] vmd 0000:00:0e.0: save config 0x3c: 0x00000000
> [  226.375481] intel-lpss 0000:00:15.1: ACPI _REG disconnect evaluation failed (5)
> [  226.375487] mei_me 0000:00:16.0: PCI PM: Suspend power state: D3hot
> [  226.375908] intel-lpss 0000:00:15.0: ACPI _REG disconnect evaluation failed (5)
> [  226.376162] proc_thermal_pci 0000:00:04.0: PCI PM: Suspend power state: D3hot
> [  226.377183] intel-lpss 0000:00:15.1: power state changed by ACPI to D3hot
> [  226.377277] intel-lpss 0000:00:15.1: PCI PM: Suspend power state: D3hot
> [  226.377771] intel-lpss 0000:00:15.0: power state changed by ACPI to D3hot
> [  226.378257] rtsx_pci 0000:06:00.0: PCI PM: Suspend power state: D3hot
> [  226.378422] intel-lpss 0000:00:15.0: PCI PM: Suspend power state: D3hot
> [  226.378448] pcieport 0000:00:1c.0: save config 0x00: 0x51bb8086
> [  226.378607] pcieport 0000:00:1c.0: save config 0x04: 0x00100407
> [  226.378656] pcieport 0000:00:1c.0: save config 0x08: 0x06040001
> [  226.378707] pcieport 0000:00:1c.0: save config 0x0c: 0x00810000
> [  226.378758] pcieport 0000:00:1c.0: save config 0x10: 0x00000000
> [  226.378782] pcieport 0000:00:1c.0: save config 0x14: 0x00000000
> [  226.378806] pcieport 0000:00:1c.0: save config 0x18: 0x00060600
> [  226.378830] pcieport 0000:00:1c.0: save config 0x1c: 0x000000f0
> [  226.378853] pcieport 0000:00:1c.0: save config 0x20: 0x75007500
> [  226.378877] pcieport 0000:00:1c.0: save config 0x24: 0x0001fff1
> [  226.378899] pcieport 0000:00:1c.0: save config 0x28: 0x00000000
> [  226.378905] pcieport 0000:00:1c.0: save config 0x2c: 0x00000000
> [  226.378935] pcieport 0000:00:1c.0: save config 0x30: 0x00000000
> [  226.378958] pcieport 0000:00:1c.0: save config 0x34: 0x00000040
> [  226.378982] pcieport 0000:00:1c.0: save config 0x38: 0x00000000
> [  226.379006] pcieport 0000:00:1c.0: save config 0x3c: 0x000204ff
> [  226.379534] pcieport 0000:00:1c.0: PME# enabled
> [  226.379589] thunderbolt 0000:00:0d.2: ACPI _REG disconnect evaluation failed (5)
> [  226.380218] xhci_hcd 0000:00:0d.0: ACPI _REG disconnect evaluation failed (5)
> [  226.381101] thunderbolt 0000:00:0d.3: ACPI _REG disconnect evaluation failed (5)
> [  226.382316] iwlwifi 0000:00:14.3: power state changed by ACPI to D3hot
> [  226.382528] iwlwifi 0000:00:14.3: PCI PM: Suspend power state: D3hot
> [  226.383140] vmd 0000:00:0e.0: ACPI _REG disconnect evaluation failed (5)
> [  226.384467] xhci_hcd 0000:00:14.0: power state changed by ACPI to D3hot
> [  226.384574] xhci_hcd 0000:00:14.0: PCI PM: Suspend power state: D3hot
> [  226.384813] vmd 0000:00:0e.0: power state changed by ACPI to D3hot
> [  226.384825] vmd 0000:00:0e.0: PCI PM: Suspend power state: D3hot
> [  226.385180] xhci_hcd 0000:00:0d.0: power state changed by ACPI to D3cold
> [  226.385191] xhci_hcd 0000:00:0d.0: PCI PM: Suspend power state: D3cold
> [  226.391528] pcieport 0000:00:1c.0: ACPI _REG disconnect evaluation failed (5)
> [  226.392369] pcieport 0000:00:1c.0: power state changed by ACPI to D3hot
> [  226.392484] pcieport 0000:00:1c.0: PCI PM: Suspend power state: D3hot
> [  226.395162] thunderbolt 0000:00:0d.2: power state changed by ACPI to D3cold
> [  226.395172] thunderbolt 0000:00:0d.2: PCI PM: Suspend power state: D3cold
> [  226.396283] thunderbolt 0000:00:0d.3: power state changed by ACPI to D3cold
> [  226.396291] thunderbolt 0000:00:0d.3: PCI PM: Suspend power state: D3cold
> [14916.770339] ACPI: EC: interrupt unblocked
> 
> -- 
> "A mouse is a device used to point at the xterm you want to type in" - A.S.R.
>  
> Home page: http://marc.merlins.org/                       | PGP 7F55D5F27AAF9D08

-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
 
Home page: http://marc.merlins.org/                       | PGP 7F55D5F27AAF9D08