[Asus X541NC] wakes up from sleep mode after 1 second (unless ACPI RP03 is disabled)

Bug #1943469 reported by João Sousa
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-hwe-5.11 (Ubuntu)
New
Undecided
Unassigned

Bug Description

computer "wakes up" from sleep mode after 1 second no matter if i wait the given time for it to sleep, or if i put it to sleep with terminal.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 13 18:56:14 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [1043:16a0]
   Subsystem: ASUSTeK Computer Inc. GK107M [GeForce 810M] [1043:137e]
InstallationDate: Installed on 2021-07-30 (44 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
 Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam
 Bus 001 Device 002: ID 0bda:b721 Realtek Semiconductor Corp. Bluetooth Radio
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X541NC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=264f931b-e96b-44e9-a13d-bf5c3236a567 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X541NC.307
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X541NC
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541NC.307:bd06/19/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX541NC:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX541NC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X541NC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
João Sousa (balqash) wrote :
affects: ubuntu → xorg (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks for the bug report. The first thing to try is to unplug your peripherals (before sleeping) to see if it is any of them waking the machine up.

affects: xorg (Ubuntu) → linux-hwe-5.11 (Ubuntu)
Changed in linux-hwe-5.11 (Ubuntu):
status: New → Incomplete
Revision history for this message
João Sousa (balqash) wrote :

joao 1000 joao 1945 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses block

this is the only thing i have, but it should be disabled automatically when entering sleep mode, right?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I'm not sure if that is relevant. I was recommending you unplug any keyboards and mice etc but it looks like you might not have any such things plugged in...

Do you have any Bluetooth devices configured? If so then please try disabling Bluetooth on the laptop before entering sleep mode.

Revision history for this message
João Sousa (balqash) wrote :

well, i have nothing plugged into computer. this is just a laptop with nothing connected here, no mouse, no mic, nothing, and i even have the bluetooth off all the time. this happens since i changed recently from 18.04 to 20.04, from that very moment computer never went to sleep mode. when it comes the time to do ti, as i set it, it goes to sleep for one second or sell and wakes up immediately. and besides, i can not find anywhere in the configurations how to set what computer does when closing the lid.

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: [Asus X541NC] wakes up from sleep mode after 1 second

I have seen suggestions that some machines get monitor "hotplug" events when they go to sleep and that might cause them to immediately wake up again. If that was the cause then selecting:

  Ubuntu on Wayland

from the login screen (bottom right corner just before you enter your password) might avoid the issue. Actually trying 'Ubuntu on Wayland' might avoid the issue even if the root cause is something different.

summary: - sleep mode
+ [Asus X541NC] wakes up from sleep mode after 1 second
Revision history for this message
João Sousa (balqash) wrote :

well, i have nothing plugged into computer. this is just a laptop with nothing connected here, no mouse, no mic, nothing, and i even have the bluetooth off all the time. this happens since i changed recently from 18.04 to 20.04, from that very moment computer never went to sleep mode. when it comes the time to do it, as i set it, it goes to sleep for one second or less and wakes up immediately. and besides, i can not find anywhere in the configurations how to set what computer does when closing the lid.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I know there is no monitor connected but "hotplug" events might still occur internally for the laptop's screen as it is turned on or off. Please try the instructions in comment #6.

Revision history for this message
João Sousa (balqash) wrote :

I have just tried it (on wayland) I doesn't work. The same happens.

I saw on the internet that other people are facing the same issue, so that's why i decided to report it, it looks to me that is is a bug.

It never happend to me when using 16 nor 18.04, and this is so annoying that i am considering going back to 18.04.

Revision history for this message
João Sousa (balqash) wrote :

*it doesn't work

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK, next please:

1. Reproduce the bug again.

2. As soon as it's woken itself up, open a Terminal and run:

   journalctl -b0 > woke.txt

3. Attach the resulting text file here.

Revision history for this message
João Sousa (balqash) wrote :

thank you for your help!
here it is attached the information you requested.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Looks like it's the network waking the machine up, so try disabling any wake-on-network-activity option(s) in your BIOS.

rugs. 17 11:48:13 joao-X541NC systemd[1]: Finished Suspend.
rugs. 17 11:48:13 joao-X541NC systemd[1]: Stopped target Sleep.
rugs. 17 11:48:13 joao-X541NC systemd[1]: Reached target Suspend.
rugs. 17 11:48:13 joao-X541NC systemd[1]: Stopped target Suspend.
rugs. 17 11:48:13 joao-X541NC systemd-logind[966]: Operation 'sleep' finished.
rugs. 17 11:48:13 joao-X541NC NetworkManager[937]: <info> [1631868493.2691] manager: sleep: wake requested (sleeping: yes enabled: yes)
rugs. 17 11:48:13 joao-X541NC NetworkManager[937]: <info> [1631868493.2693] device (enp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
rugs. 17 11:48:13 joao-X541NC kernel: RTL8208 Fast Ethernet r8169-100:00: attached PHY driver (mii_bus:phy_addr=r8169-100:00, irq=POLL)

Revision history for this message
João Sousa (balqash) wrote :

Ok thanks, I will try to do it and let you know here.

Revision history for this message
João Sousa (balqash) wrote :

It doesn't work. Are you sure it is internal and an issue that can be solve in computer BIOS? Actually I couldn't find there where to disable any network wake request. The only one available was the "wake on lid open" that I indeed disabled just now, but the situation doesn't change.

And besides, computer was sleeping with windows before alongside with ubuntu 18.04, but since i formated computer and installed 20.04, there is no way i can "put computer to sleep". There were no changes in BIOS, just this flaw.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It appears you can configure what hardware components can wake the machine up with /proc/acpi/wakeup

Can you attach a copy of that file here?

Changed in linux-hwe-5.11 (Ubuntu):
status: Incomplete → New
Revision history for this message
João Sousa (balqash) wrote :

Yes, sure. Here it is...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. That seems to show only internal components (PCIe) and the USB 3.0 controller can wake the machine up. Please try disabling each of them separately:

  sudo sh -c 'echo XHC > /proc/acpi/wakeup'
  sudo sh -c 'echo RP01 > /proc/acpi/wakeup'
  sudo sh -c 'echo RP03 > /proc/acpi/wakeup'
  sudo sh -c 'echo RP04 > /proc/acpi/wakeup'

If none of those work then the next step would be to see if the nouveau driver is causing the issue. I would recommend trying the official Nvidia driver instead, which you can enable by the 'Additional Drivers' app or:

  sudo apt install nvidia-driver-430

Changed in linux-hwe-5.11 (Ubuntu):
status: New → Incomplete
Revision history for this message
João Sousa (balqash) wrote :

Well, i tried installing nvidia but nothing changed. I am going now to try to disable those controllers. But aren't they going to mess other things in computer? Can you please tell me how to enable them if something goes not right?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

To re-enable them is the same command, it only toggles the setting. Also it may not be remembered between reboots so just rebooting likely will reset them too.

Revision history for this message
João Sousa (balqash) wrote :

finally it worked after:

sudo sh -c 'echo RP03 > /proc/acpi/wakeup'

but computer is not sleeping after i restarted it... and besides, doing this i am disabling something, right?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

RP03 is the "PCI Express Port A #1" but that doesn't tell us much else. And no you're not disabling anything other than the ability of one device to wake the machine up. So long as you have some other way of waking the machine up it should be safe.

I'm not sure what the recommended way of disabling RP03 by default would be...

Revision history for this message
João Sousa (balqash) wrote :

thank you for your help. at least i know now how to enable sleep, although the problem still persists. i will try to find a way to make this permanent, so i don't have to run it on terminal each time i turn on computer...

summary: - [Asus X541NC] wakes up from sleep mode after 1 second
+ [Asus X541NC] wakes up from sleep mode after 1 second (unless ACPI RP03
+ is disabled)
Changed in linux-hwe-5.11 (Ubuntu):
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.