Dell Inspiron 17 7706, Mint 20 wakes up automatically from suspend

[asdfuioda]

Have been reading a lot of threads on these forums and elsewhere. Trying to get this new computer to work flawlessly. Have 2 pesky issues. Suspend doesn't work, and microphone doesn't work (but audio and webcam does). Leaving the latter for another thread...

I have a Dell Inspiron 17, 7706, running Mint 20. Laptop wakes up about 30 seconds after going into suspend. Screen turns on and fan starts when this happens, just as normal. I am running the Nvidia 460 drivers. I have tried disabling bluetooth (no difference), or WLAN (no difference). I am running the latest stable kernel, 5.11.8 (5.11.8-051108-generic). I ran out of ideas to try, so posting here! Was unable to figure out how to see which device woke it up. Maybe it is simply failing to go into suspend properly. Not sure how to see this.

I have disabled every wakeup device except for the power button. I did this using variations on

Code: Select all

echo XHCI | sudo tee /proc/acpi/wakeup

, swap XHCI for each device one wants to disable.

Code: Select all

emil@test ~ $ cat /proc/acpi/wakeup
Device	S-state	  Status   Sysfs node
PEG0	  S4	*disabled
PEGP	  S4	*disabled
PEG1	  S4	*disabled
PEGP	  S4	*disabled
PEG2	  S4	*disabled
PEGP	  S4	*disabled
XHCI	  S0	*disabled  pci:0000:00:14.0
XDCI	  S4	*disabled
HDAS	  S4	*disabled  pci:0000:00:1f.3
RP01	  S4	*disabled
PXSX	  S4	*disabled
RP02	  S4	*disabled
PXSX	  S4	*disabled
RP03	  S4	*disabled
PXSX	  S4	*disabled
RP04	  S4	*disabled
PXSX	  S4	*disabled
RP05	  S4	*disabled  pci:0000:00:1c.0
PXSX	  S4	*disabled  pci:0000:2b:00.0
RP06	  S4	*disabled
PXSX	  S4	*disabled
RP07	  S4	*disabled
PXSX	  S4	*disabled
RP08	  S4	*disabled
PXSX	  S4	*disabled
RP09	  S4	*disabled  pci:0000:00:1d.0
PXSX	  S4	*disabled  pci:0000:2c:00.0
RP10	  S4	*disabled
PXSX	  S4	*disabled
RP11	  S4	*disabled
PXSX	  S4	*disabled
RP12	  S4	*disabled
PXSX	  S4	*disabled
RP13	  S4	*disabled
PXSX	  S4	*disabled
RP14	  S4	*disabled
PXSX	  S4	*disabled
RP15	  S4	*disabled
PXSX	  S4	*disabled
RP16	  S4	*disabled
PXSX	  S4	*disabled
RP17	  S4	*disabled
PXSX	  S4	*disabled
RP18	  S4	*disabled
PXSX	  S4	*disabled
RP19	  S4	*disabled
PXSX	  S4	*disabled
RP20	  S4	*disabled
PXSX	  S4	*disabled
RP21	  S4	*disabled
PXSX	  S4	*disabled
RP22	  S4	*disabled
PXSX	  S4	*disabled
RP23	  S4	*disabled
PXSX	  S4	*disabled
RP24	  S4	*disabled
PXSX	  S4	*disabled
CNVW	  S4	*disabled  pci:0000:00:14.3
TXHC	  S4	*disabled  pci:0000:00:0d.0
TDM0	  S4	*disabled  pci:0000:00:0d.2
TDM1	  S4	*disabled
TRP0	  S4	*disabled  pci:0000:00:07.0
PXSX	  S4	*disabled
TRP1	  S4	*disabled
PXSX	  S4	*disabled
TRP2	  S4	*disabled
PXSX	  S4	*disabled
TRP3	  S4	*disabled
PXSX	  S4	*disabled
AWAC	  S4	*disabled  platform:ACPI000E:00
LID0	  S3	*disabled  platform:PNP0C0D:00
PBTN	  S3	*enabled   platform:PNP0C0C:00

Devices:

Code: Select all

emil@test ~ $ cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=4000 0 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=1100f02902000 8380307cf910f001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input5
U: Uniq=
H: Handlers=mouse3 event9 
B: PROP=1
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3

I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input13
U: Uniq=
H: Handlers=kbd event10 
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0

I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:3e/LNXVIDEO:01/input/input14
U: Uniq=
H: Handlers=kbd event11 
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Intel HID events"
P: Phys=
S: Sysfs=/devices/platform/INTC1051:00/input/input15
U: Uniq=
H: Handlers=rfkill kbd event12 
B: PROP=0
B: EV=13
B: KEY=81000300000000 5000004000 1e294000000020 0
B: MSC=10

I: Bus=0003 Vendor=0bda Product=565a Version=8176
N: Name="Integrated_Webcam_HD: Integrate"
P: Phys=usb-0000:00:14.0-6/button
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.0/input/input16
U: Uniq=
H: Handlers=kbd event4 
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Dell WMI hotkeys"
P: Phys=
S: Sysfs=/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input17
U: Uniq=
H: Handlers=rfkill kbd event5 
B: PROP=0
B: EV=13
B: KEY=800000000000 0 0 101500b00000c00 1200300000 e000000000000 0
B: MSC=10

I: Bus=0018 Vendor=04f3 Product=2a11 Version=0100
N: Name="CUST0000:00 04F3:2A11"
P: Phys=i2c-CUST0000:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0000:00/0018:04F3:2A11.0001/input/input18
U: Uniq=
H: Handlers=mouse0 event6 
B: PROP=2
B: EV=1b
B: KEY=400 0 0 0 0 0
B: ABS=3273800000000003
B: MSC=20

I: Bus=0018 Vendor=04f3 Product=2a11 Version=0100
N: Name="CUST0000:00 04F3:2A11 UNKNOWN"
P: Phys=i2c-CUST0000:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0000:00/0018:04F3:2A11.0001/input/input19
U: Uniq=
H: Handlers=event13 
B: PROP=0
B: EV=9
B: ABS=10000000000

I: Bus=0018 Vendor=04f3 Product=2a11 Version=0100
N: Name="CUST0000:00 04F3:2A11 UNKNOWN"
P: Phys=i2c-CUST0000:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-CUST0000:00/0018:04F3:2A11.0001/input/input20
U: Uniq=
H: Handlers=event14 
B: PROP=0
B: EV=100001

I: Bus=0018 Vendor=04f3 Product=314b Version=0100
N: Name="DLL0945:00 04F3:314B Mouse"
P: Phys=i2c-DLL0945:00
S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0945:00/0018:04F3:314B.0002/input/input22
U: Uniq=
H: Handlers=mouse1 event7 
B: PROP=0
B: EV=17
B: KEY=30000 0 0 0 0
B: REL=3
B: MSC=10

I: Bus=0018 Vendor=04f3 Product=314b Version=0100
N: Name="DLL0945:00 04F3:314B Touchpad"
P: Phys=i2c-DLL0945:00
S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0945:00/0018:04F3:314B.0002/input/input23
U: Uniq=
H: Handlers=mouse2 event8 
B: PROP=5
B: EV=1b
B: KEY=e520 10000 0 0 0 0
B: ABS=2e0800000000003
B: MSC=20

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Headphone Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input25
U: Uniq=
H: Handlers=event15 
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input26
U: Uniq=
H: Handlers=event16 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input27
U: Uniq=
H: Handlers=event17 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input28
U: Uniq=
H: Handlers=event18 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input29
U: Uniq=
H: Handlers=event19 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=10"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input30
U: Uniq=
H: Handlers=event20 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=11"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input31
U: Uniq=
H: Handlers=event21 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=12"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input32
U: Uniq=
H: Handlers=event22 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=13"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input33
U: Uniq=
H: Handlers=event23 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=14"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input34
U: Uniq=
H: Handlers=event24 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=15"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input35
U: Uniq=
H: Handlers=event25 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=16"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input36
U: Uniq=
H: Handlers=event26 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Intel HID switches"
P: Phys=
S: Sysfs=/devices/platform/INTC1051:00/input/input37
U: Uniq=
H: Handlers=event27 
B: PROP=0
B: EV=21
B: SW=2

inxi output:

Code: Select all

emil@test ~ $ inxi -Fxz
System:
  Kernel: 5.11.8-051108-generic x86_64 bits: 64 compiler: N/A 
  Desktop: Cinnamon 4.8.6 Distro: Linux Mint 20.1 Ulyssa 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Convertible System: Dell product: Inspiron 7706 2n1 v: N/A 
  serial: <filter> 
  Mobo: Dell model: 0P47D9 v: A00 serial: <filter> UEFI: Dell v: 1.1.8 
  date: 12/17/2020 
Battery:
  ID-1: BAT0 charge: 46.2 Wh condition: 68.0/68.0 Wh (100%) 
  model: LGC-LGC4.47 DELL 10X1J0B status: Charging 
CPU:
  Topology: Quad Core model: 11th Gen Intel Core i7-1165G7 bits: 64 
  type: MT MCP arch: Tiger Lake rev: 1 L2 cache: 12.0 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 44851 
  Speed: 1200 MHz min/max: 400/4700 MHz Core speeds (MHz): 1: 1200 2: 1192 
  3: 1292 4: 1232 5: 1185 6: 1201 7: 1172 8: 1187 
Graphics:
  Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 
  Device-2: NVIDIA GP107M [GeForce MX350] driver: nvidia v: 460.39 
  bus ID: 2b:00.0 
  Display: x11 server: X.Org 1.20.9 driver: modesetting,nvidia 
  unloaded: fbdev,nouveau,vesa resolution: 2560x1600~60Hz 
  OpenGL: renderer: GeForce MX350/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39 
  direct render: Yes 
Audio:
  Device-1: Intel vendor: Dell driver: snd_hda_intel v: kernel 
  bus ID: 00:1f.3 
  Sound Server: ALSA v: k5.11.8-051108-generic 
Network:
  Device-1: Intel driver: iwlwifi v: kernel port: 4000 bus ID: 00:14.3 
  IF: wlp0s20f3 state: up mac: <filter> 
Drives:
  Local Storage: total: 3.73 TiB used: 1.32 TiB (35.3%) 
  ID-1: /dev/nvme0n1 vendor: Seagate model: XPG SPECTRIX S40G size: 3.73 TiB 
Partition:
  ID-1: / size: 3.66 TiB used: 364.94 GiB (9.7%) fs: ext4 dev: /dev/dm-1 
  ID-2: /boot size: 704.5 MiB used: 513.3 MiB (72.9%) fs: ext4 
  dev: /dev/nvme0n1p2 
  ID-3: swap-1 size: 976.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-2 
Sensors:
  System Temperatures: cpu: 55.0 C mobo: N/A gpu: nvidia temp: 57 C 
  Fan Speeds (RPM): cpu: 3213 
Info:
  Processes: 296 Uptime: 43m Memory: 62.54 GiB used: 5.05 GiB (8.1%) 
  Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 
  inxi: 3.0.38 

[deepakdeshp]

In update manager view kernels install latest kernel of 5.8 series, reboot choosing this in grub and test.

[SMG]

Laptop wakes up about 30 seconds after going into suspend. ... Was unable to figure out how to see which device woke it up.

After it wakes, run dmesg | tail -n 50 which will give the last 50 log messages. Depending upon how much is happening, you may have get more lines (100 or 150) to see what is happening.

These types of issues are often ACPI related, so I would second the recommendation to use the Ubuntu-supported 5.8 kernel rather than the one you are using.

I would also recommend you update to the latest available BIOS as that most directly impacts ACPI handling. This link Inspiron 7706 2-in-1 Drivers indicates version 1.2.0 came out a few weeks ago.

Machine:
Type: Convertible System: Dell product: Inspiron 7706 2n1 v: N/A
serial: <filter>
Mobo: Dell model: 0P47D9 v: A00 serial: <filter> UEFI: Dell v: 1.1.8
date: 12/17/2020

[asdfuioda]

I tried downgrading to the latest 5.8 kernel, which is 5.8.18. Then doing a test suspension for 46 minutes:

[


So in the 46 minutes, it drained some 7% power. That seems too high to me. This would drain a full battery in about 6.6 hours. ((60/7) * 46)/60.

Terminal output:

Code: Select all

[ 3276.482009] wlp0s20f3: deauthenticating from 84:d8:1b:25:e3:2d by local choice (Reason: 3=DEAUTH_LEAVING)
[ 3276.557544] PM: suspend entry (s2idle)
[ 3276.560450] Filesystems sync: 0.002 seconds
[ 3277.206537] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 3277.208741] OOM killer disabled.
[ 3277.208741] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 3277.209883] printk: Suspending console(s) (use no_console_suspend to debug)
[ 3278.078213] ACPI: EC: interrupt blocked
[ 6013.594173] ACPI: EC: interrupt unblocked
[ 6014.373921] nvme nvme0: 7/0/0 default/read/poll queues
[ 6014.766834] OOM killer enabled.
[ 6014.766835] Restarting tasks ... 
[ 6014.771643] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[ 6014.772371] done.
[ 6014.783911] thermal thermal_zone6: failed to read out thermal zone (-61)
[ 6014.840694] PM: suspend exit
[ 6018.704429] wlp0s20f3: authenticate with 84:d8:1b:25:e3:2d
[ 6018.705935] wlp0s20f3: send auth to 84:d8:1b:25:e3:2d (try 1/3)
[ 6018.731159] wlp0s20f3: authenticated
[ 6018.732017] wlp0s20f3: associate with 84:d8:1b:25:e3:2d (try 1/3)
[ 6018.836094] wlp0s20f3: associate with 84:d8:1b:25:e3:2d (try 2/3)
[ 6018.877214] wlp0s20f3: RX AssocResp from 84:d8:1b:25:e3:2d (capab=0x1411 status=0 aid=1)
[ 6018.879943] wlp0s20f3: associated
[ 6018.929116] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready

On the positive side. This kernel downgrade fixed the microphone!

[SMG]

I tried downgrading to the latest 5.8 kernel, which is 5.8.18.

I have no idea where you are getting kernels, but the advice to use the 5.8 kernel meant to use one from the Ubuntu repository. The latest available 5.8 kernel which is available through Update Manager is 5.8.0-48.

You can get that kernel by opening Update Manager. Select View > Linux Kernels and click Continue. Make sure 5.8 is selected on the left panel and then click the top-most option on the right panel. An "Install" button will appear. Install the kernel and then reboot for it to become active.

We can help you troubleshoot Ubuntu kernels because that is what we use, but we can not help you troubleshooting issues with other kernels.

Did you update your BIOS/UEFI? That may help with whatever ACPI issue that seems to be preventing your computer from fully going to sleep.

[asdfuioda]

Next, I did the BIOS update. I did this using the USB drive approach as was recommended by Dell. I updated from 1.18 to 1.30.

https://www.dell.com/support/home/en-us ... n-1-laptop

I did a new suspension test, for about 1 hour. Results:




So it drained 10% power in 65 minutes, which is consistent with prior experiment. The rate is 9.23%/hour in this experiment vs. 9.13/hour before.

I update kernels with UKUU paid version:



I never heard of specific Ubuntu kernels before. I will try the approach you say and report back with another suspension test.

[SMG]

I never heard of specific Ubuntu kernels before. I will try the approach you say and report back with another suspension test.

The Ubuntu kernels are what come on the Mint ISO's. Mint does not use mainline kernels.

[asdfuioda]

Another suspension test on the Ubuntu Kernel, as requested. System information confirms this:



Battery before and after:




Suspended for 61 minutes, drained 10% power, so a rate of 9.84/hour, about the same as before.

dmseg:

Code: Select all

emil@test ~ $ sudo dmesg | tail -n 50
[sudo] password for emil:             
[   12.434092] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:2b:00.0 on minor 1
[   12.450512] nvidia-uvm: Loaded the UVM driver, major device number 507.
[   13.091316] Bluetooth: hci0: Waiting for firmware download to complete
[   13.091712] Bluetooth: hci0: Firmware loaded in 1533007 usecs
[   13.091747] Bluetooth: hci0: Waiting for device to boot
[   13.106791] Bluetooth: hci0: Device booted in 14703 usecs
[   13.106987] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
[   13.108836] Bluetooth: hci0: Applying Intel DDC parameters completed
[   13.109819] Bluetooth: hci0: Firmware revision 0.0 build 121 week 36 2020
[   15.556031] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   15.556033] Bluetooth: BNEP filters: protocol multicast
[   15.556036] Bluetooth: BNEP socket layer initialized
[   15.563706] NET: Registered protocol family 38
[   15.569213] process '/usr/bin/anydesk' started with executable stack
[   15.650588] hid-sensor-hub 001F:8087:0AC2.0004: hid_field_extract() called with n (192) > 32! (kworker/1:1)
[   16.374983] ACPI Warning: \_SB.PC00.RP05.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20200528/nsarguments-59)
[   19.448821] wlp0s20f3: authenticate with 84:d8:1b:25:e3:2d
[   19.450399] wlp0s20f3: send auth to 84:d8:1b:25:e3:2d (try 1/3)
[   19.475957] wlp0s20f3: authenticated
[   19.480703] wlp0s20f3: associate with 84:d8:1b:25:e3:2d (try 1/3)
[   19.584699] wlp0s20f3: associate with 84:d8:1b:25:e3:2d (try 2/3)
[   19.626045] wlp0s20f3: RX AssocResp from 84:d8:1b:25:e3:2d (capab=0x1411 status=0 aid=1)
[   19.628145] wlp0s20f3: associated
[   19.675081] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready
[   25.358404] Bluetooth: RFCOMM TTY layer initialized
[   25.358409] Bluetooth: RFCOMM socket layer initialized
[   25.358412] Bluetooth: RFCOMM ver 1.11
[   68.217591] wlp0s20f3: deauthenticating from 84:d8:1b:25:e3:2d by local choice (Reason: 3=DEAUTH_LEAVING)
[   68.299358] PM: suspend entry (s2idle)
[   68.306977] Filesystems sync: 0.007 seconds
[   68.894824] Freezing user space processes ... (elapsed 0.002 seconds) done.
[   68.896943] OOM killer disabled.
[   68.896944] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[   68.898136] printk: Suspending console(s) (use no_console_suspend to debug)
[   69.405546] ACPI: EC: interrupt blocked
[ 3712.815138] ACPI: EC: interrupt unblocked
[ 3713.582487] nvme nvme0: 7/0/0 default/read/poll queues
[ 3713.974806] OOM killer enabled.
[ 3713.974807] Restarting tasks ... done.
[ 3713.980978] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[ 3713.992889] thermal thermal_zone6: failed to read out thermal zone (-61)
[ 3714.040047] PM: suspend exit
[ 3717.847459] wlp0s20f3: authenticate with 84:d8:1b:25:e3:2d
[ 3717.848935] wlp0s20f3: send auth to 84:d8:1b:25:e3:2d (try 1/3)
[ 3717.874484] wlp0s20f3: authenticated
[ 3717.876347] wlp0s20f3: associate with 84:d8:1b:25:e3:2d (try 1/3)
[ 3717.980335] wlp0s20f3: associate with 84:d8:1b:25:e3:2d (try 2/3)
[ 3718.021911] wlp0s20f3: RX AssocResp from 84:d8:1b:25:e3:2d (capab=0x1411 status=0 aid=1)
[ 3718.025387] wlp0s20f3: associated
[ 3718.067783] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready

[SMG]

In your initial post you indicated, "Suspend doesn't work", so I am confused about what you are referring to as a "suspension test" that you are doing for 40-60 minutes. Either suspend works or it does not.

Checking how much the battery drains is a check of how much of the system is shut off during suspend. Some computer manufacturers have their BIOS/UEFI set up so that deep sleep states are not possible. That means a suspension will consume more energy than may be expected, but that does not correlate with whether or not the computer is suspended.

emil@test ~ $ sudo dmesg | tail -n 50

sudo is not necessary to get dmesg output.

This indicates suspend is happening. Notice the nearly one hour difference between the interrupt blocked and unblocked.

Code: Select all

[   68.299358] PM: suspend entry (s2idle)
[   68.306977] Filesystems sync: 0.007 seconds
[   68.894824] Freezing user space processes ... (elapsed 0.002 seconds) done.
[   68.896943] OOM killer disabled.
[   68.896944] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[   68.898136] printk: Suspending console(s) (use no_console_suspend to debug)
[   69.405546] ACPI: EC: interrupt blocked
[ 3712.815138] ACPI: EC: interrupt unblocked
[ 3713.582487] nvme nvme0: 7/0/0 default/read/poll queues
[ 3713.974806] OOM killer enabled.
[ 3713.974807] Restarting tasks ... done.
[ 3713.980978] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[ 3714.040047] PM: suspend exit

Looking at your previous dmesg output, I see the same large time gap which means the computer is suspending. I missed that when I checked the information earlier.

Code: Select all

[ 3278.078213] ACPI: EC: interrupt blocked
[ 6013.594173] ACPI: EC: interrupt unblocked

That means the issue in the title of your thread is resolved.

[asdfuioda]

The point of the thread is obviously to get suspend to work properly. I think it wakes up automatically because it uses power, the fans turn on, it gets hot etc. I don't know whether you want to classify that as "suspend doesn't work properly" or "suspend doesn't work, wakes up partially automatically". In either case, it doesn't work as it should. I don't see the point of the semantics conflict. Suspend works fine on Windows 10 (the default OS) for this computer.

As for dmesg, yes, sudo was necessary. I got an error before. I think that was maybe because I had messed up a group setting for my user (I accidentally did this) or maybe it is kernel related (?) because it works now. I didn't save the output unfortunately, so I can't tell you what the exact error message was, but something about lack of permission to run that. I think it was this error.

Maybe this is related: https://www.dell.com/community/Laptops- ... -p/4247978

I will look around in the BIOS to see if I can find anything to try turning off/on.

[SMG]

The point of the thread is obviously to get suspend to work properly. I think it wakes up automatically because it uses power, the fans turn on, it gets hot etc. I don't know whether you want to classify that as "suspend doesn't work properly" or "suspend doesn't work, wakes up partially automatically". In either case, it doesn't work as it should. I don't see the point of the semantics conflict. Suspend works fine on Windows 10 (the default OS) for this computer.

You have provided zero data to indicate suspend "wakes up automatically". What data you have provided indicates the operating system is suspending and it is resuming from suspend mode when you tell it to resume from suspend. That sounds like a definition of suspend working properly.

I have seen dmesg info where suspend does not work properly, where it never makes it to the deep state and in less than a minute or so the person has their desktop back on their screen. That is what happens when suspend does not work. That is not how you have described your situation and not what your data shows.

If you want a resolution, you have to find the root cause. In order to find the root cause, you have to define the problem correctly. That is not "semantics". That is basic troubleshooting 101.

If your issue is how much power your computer is using during the suspend cycle, then that is a power consumption issue. That is something which is handled on the base level by the hardware of your computer. Then the next level are the settings your computer's manufacturer has set in the BIOS/UEFI for the various sleep states. There are multiple sleep states on a computer. Sleep does not mean the same thing for every hardware component on your computer. Then there is the operating system telling the hardware which state was requested and which one to use.

It sounds like your concern is your computer is consuming more power than you want it to consume while it is in sleep state. That does not sound like the issue in the Dell community thread you linked which appears to be the computer is not waking up from suspend. You have indicated your computer is waking up from suspend.

I do not know the specifics of your hardware. I do not know what design criteria was used to define each sleep state level. That means I do not know what are safe settings for your hardware's longevity so I have no recommendations for what sleep level should be used when Mint suspends your computer.

I think part of the issue is manufacturer's have changed the settings in recent years on those sleep states to be more in line with Windows' fast boot requirements. In order to bring a system back to life quickly, some items are left in a partially powered state.

[asdfuioda]

So I figured out a way to tell whether it wakes itself up (as I thought) or whether suspend itself is just broken. Someone suggested leaving music running, and it should thus turn itself back on when it resumes. This doesn't happen, so it's a problem with suspend, not automatically waking.

dmseg has also gone back to not working without sudo:

Code: Select all

emil@test ~ $ dmesg | tail -n 50
dmesg: read kernel buffer failed: Operation not permitted
emil@test ~ $ sudo dmesg | tail -n 50
[sudo] password for emil:             
[  119.212771] wlp0s20f3: associate with 84:d8:1b:25:e3:2d (try 2/3)
[  119.254235] wlp0s20f3: RX AssocResp from 84:d8:1b:25:e3:2d (capab=0x1411 status=0 aid=1)

I guess I was wrong above, and this behavior resets every reboot or something...

Seems related to this https://bugs.launchpad.net/ubuntu/+sour ... ug/1808957

I tried the grub edit method already, did not change anything. File /etc/default/grub, change to:

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"

and then:

Code: Select all

sudo grub-mkconfig -o /boot/grub/grub.cfg

Produces no errors, but changes nothing, nor after reboot.

I can't echo the file they say to edit:

Code: Select all

emil@test ~ $ cat /sys/power/mem_sleep
[s2idle]
emil@test ~ $ echo deep > /sys/power/mem_sleep
bash: /sys/power/mem_sleep: Permission denied
emil@test ~ $ sudo -i
root@test:~# echo deep > /sys/power/mem_sleep
-bash: echo: write error: Invalid argument

Even running nano as root does not make me able to write to that file:



Something preventing it at a deep level?

Next I tried `/etc/systemd/sleep.conf` editing to add/change:

Code: Select all

[Sleep]
SuspendMode=
SuspendState=mem

After reboot, no change to the s2idle file.

Of interest is:

Code: Select all

root@test:/sys/power# cat /sys/power/state
freeze mem disk

Whereas for other people, the `disk` is not there. Does that mean it keeps the power on the disk? It's an NVMe, so maybe this is some NVMe issue.

Some people talk about an NVidia related issue. This machine has an NVidia card (MX350). I tried adding to grub:

Code: Select all

GRUB_CMDLINE_LINUX="nouveau.modeset=0"

Rebuild grub and reboot, no change:

Code: Select all

emil@test ~ $ cat /sys/power/mem_sleep
[s2idle]

One guy suggests trying the 5.3 kernel. I will do that and report back...

[asdfuioda]

5.3.18 and 5.4.0.70.78 (default) kernels leaves the system unable to boot. This was the initial behavior once I installed Mint on this machine. I think it has something to do with the sound driver issues I mentioned.

Next thing to try. This BIOS changing options. Seems like a far fetch, but I guess I have nothing else to try.

https://askubuntu.com/a/1180175/573611

o, my tentative solution that seems to work so far is: toggling certain BIOS settings on and off. I know it sounds downright idiotic, but I swear it seemed to work from what I've tested so far.

Specifically, I either turned settings off and/or selected a different option for a setting, applied it, then set it back and applied it. The settings I toggled back and forth were:

System Configuration > Touchscreen (Toggled Off, then back On)

Power Management > Auto On Time (Switched it to a different option, then back to Disabled)

Power Management > Wake on Dell USB-C Docks (Toggled Off, then On)

[SMG]

So I figured out a way to tell whether it wakes itself up (as I thought) or whether suspend itself is just broken. Someone suggested leaving music running, and it should thus turn itself back on when it resumes. This doesn't happen, so it's a problem with suspend, not automatically waking.

Who here suggested that? I did not see anyone suggest that.

And why are you now talking about suspend not automatically waking? You titled the thread that the suspend was automatically waking and now you expect us to believe the problem is the exact opposite.

Just because the sound driver does not resume, does not mean the computer did not resume. There are separate drivers for each of the hardware pieces in the computer.

dmseg has also gone back to not working without sudo:

I honestly think it is time for you to boot to a live session of Mint with the Linux Mint 20.1 "Ulyssa" - Cinnamon (Edge, 64-bit) ISO. That will give you an unmodified system to test.

You keep making changes on your system which just complicates the troubleshooting process because you are making more problems along the way.

I tried the grub edit method already, did not change anything.

Who advised you to try a grub method which was listed for computer hardware that is different from yours? And for a bug from two years ago that has been resolved and the fixes pushed out to the kernels long ago?

One guy suggests trying the 5.3 kernel. I will do that and report back...

Don't bother reporting back.

The lowest kernel which is supported for LM20 is the 5.4 kernel. The 5.3 kernel is no longer a supported kernel.

[asdfuioda]

So, I did a new suspend test after doing the BIOS thing. No changes. 30 mins suspend produced a power drain of 5%, which is about 10/hour, same as before. This was on kernel 5.8.18-050818-generic.

Who here suggested that? I did not see anyone suggest that.

No one. I didn't say that either. I said someone, it was this answer https://askubuntu.com/a/1044270/573611

It is reasonable to try solutions for similar laptops when there are no more online resources for this one.

Will try with the live disk, but this problem was there since the initial use of this machine. The system cannot boot with the default 5.4 kernel, it needs a newer one to boot. The live disk will boot though. The workaround here is to enter recovery mode on first boot from disk and click resume boot. That circumvents some problem (I guess the sound driver since it produces some errors on screen about these otherwise) and allows one to get into the system to update the kernel.

[SMG]

Will try with the live disk, but this problem was there since the initial use of this machine. The system cannot boot with the default 5.4 kernel, it needs a newer one to boot.

The ISO to which I linked has the 5.8.0 kernel on it. It is a currently supported Ubuntu kernel.

The workaround here is to enter recovery mode on first boot from disk and click resume boot. That circumvents some problem (I guess the sound driver since it produces some errors on screen about these otherwise) and allows one to get into the system to update the kernel.

Recovery Mode disables a number of drivers including graphics drivers.

[asdfuioda]

Tried the live disk. Same results. Drained 4% in 30 mins. With rounding (84% to 80%), this is in the 8-10%/hour range. The output is also the same from

Code: Select all

cat /sys/power/mem_sleep

and from

Code: Select all

cat /sys/power/state

.

Next idea. I can disable the NVMe in the BIOS, boot from the live disk and retry. This should disable any power use to NVMe. Thus, one can at least see if this makes a large difference.

[SMG]

Here is the Dell information which explains the sleep states The Battery drains quicker than expected on a Dell notebook with Modern Standby mode enabled.

This Dell community thread XPS 15 9560, Battery drain during sleep has a solution which recommends hibernation instead of sleep. It also has a video which explains Modern Standby.

Hibernation is turned off by default in Mint 20, but there are tutorials on this forum for turning it on if you want to go that route.

[asdfuioda]

I will look into that. I read somewhere I think that hibernation will not work with encrypted disks (mine is encrypted), so maybe I am out of luck...

In any case, the live disk no-NVMe experiment worked as expected. In 60 minutes it drained 4% (76% to 72%), so that's much closer to a normal rate, and about 60% less than what I am currently getting.

Now, I am wondering if I am wrong that it works fine on Windows. Unfortunately, I don't think I can get the default Windows 10 back since I overwrote everything when installing Mint.

[asdfuioda]

I used this guide to get hibernation to work. Cross-posting there for ease of reference. Fixed some errors in his guide. This uses a swap file on an encrypted disk.

Make swap file if you don't have one:

Code: Select all

sudo dd if=/dev/zero of=/swapfile bs=$(cat /proc/meminfo | grep MemTotal | grep -oh '[0-9]*') count=1024 conv=notrunc
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile

This code uses your memory size by default. If you don't want, then remove the $(...) part and enter whatever value you want, in bytes.

Note the UUID of the partition containing your swapfile:

Code: Select all

$ sudo findmnt -no SOURCE,UUID -T /swapfile
/dev/nvme0n1p5 20562a02-cfa6-42e0-bb9f-5e936ea763d0

The mkswap command also outputs an UUID, but it differs from the above for some reason. Use the one from above.

Reconfigure the package uswsusp correctly:

Code: Select all

sudo apt -y install uswsusp
sudo dpkg-reconfigure -pmedium uswsusp
# Answer "Yes" to continue without swap space
# Select "/dev/disk/by-uuid/20562a02-cfa6-42e0-bb9f-5e936ea763d0" replace the UUID with the result from the previous [c]findmnt[/c] command
# Encrypt: "No"

Edit the SystemD hibernate service using sudo systemctl edit systemd-hibernate.service and fill it with the following content:

Code: Select all

[Service]
ExecStart=
ExecStartPre=-/bin/run-parts -v -a pre /lib/systemd/system-sleep
ExecStart=/usr/sbin/s2disk
ExecStartPost=-/bin/run-parts -v --reverse -a post /lib/systemd/system-sleep

Note the offset of your swapfile relative to the partition start:

Code: Select all

$ sudo swap-offset /swapfile
resume offset = 34818

Tell grub to resume by editing your /etc/default/grub

NOTE: THE OFFSET IS DIFFERENT FROM SYSTEM TO SYSTEM! YOU NEED TO USE THE VALUE RETURNED ON YOUR SYSTEM!

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="resume=UUID=20562a02-cfa6-42e0-bb9f-5e936ea763d0 resume_offset=34818 quiet splash"

Update grub:

Code: Select all

sudo update-grub

Create /etc/initramfs-tools/conf.d/resume

Code: Select all

resume=UUID=20562a02-cfa6-42e0-bb9e-5e936ea763d0 resume_offset=34816
# Resume from /swapfile

Update initramfs:

Code: Select all

sudo update-initramfs -u -k all

Beware of errors/warnings thrown here. They indicate you did something wrong.

Now you can maybe hibernate your system with:

Code: Select all

sudo systemctl hibernate

If this doesn't work, and gives an error:

Code: Select all

Failed to hibernate system via logind: Not enough swap space for hibernation

Then use:

Code: Select all

sudo s2disk

This works for me.

If you want this file to permanently be used (probably!), you need to edit /etc/fstab to add:

Code: Select all

/swapfile none swap sw 0 0

I tested this. Hibernated for 1 hour, spent 1% battery. Probably not real use, but done during the save to disk phase. It took about 1 minute to hibernate. Boot time was same as booting normal.

Last thing to try to avoid hibernation. I found some references to OEM kernels maybe working with newer Dell hardware.

Related Dell laptop problems: https://www.dell.com/community/XPS/Ubun ... -p/7734008 https://www.dell.com/community/Linux-De ... -p/4610134 https://www.dell.com/community/Linux-De ... -p/7622225 https://www.dell.com/community/XPS/Susp ... -p/7646809

https://askubuntu.com/questions/1290864 ... p-problems
https://wiki.ubuntu.com/Kernel/OEMKernel
https://askubuntu.com/questions/1312788 ... ge-package

Seems the appropriate command to get the newest kernel:

Code: Select all

apt install linux-image-oem-20.04-edge

Will report back...