Auto-standby after wake up

Questions about hardware, drivers and peripherals
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
cieggi
Level 1
Level 1
Posts: 21
Joined: Sun Apr 11, 2021 2:00 am

Auto-standby after wake up

Post by cieggi »

Hello,
I'm running Mint on a MSI Cubi N 8 GL (fanless mini PC with Intel N5000). It works fine, but I have strange issue with the sandby. I don't have an "how reproduce this issue" process, because I've not yet figured out when and why this occurs.

I put the Cubi in sleep mode (standby)
When I press the power button to wake up, it actually starts but after few seconds it goes again in standby. I press the power button again and it goes again in standby after few seconds, and so on..
Sometimes I can keep it "awake" by pressing some keyboard keys, but it doesn't works all the times. If I can't keep it powered on I have to long-press the power button and reboot.

Can you help me to understand how can I solve this problem, or at least why this happens?
Thanks!
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Top
User avatar
SMG
Level 25
Level 25
Posts: 31776
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Auto-standby after wake up

Post by SMG »

Welcome to the forum, cieggi.

Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz
Click </> from the mini toolbar above the textbox where you type your reply and then place your cursor between the code markers and paste the results of the command between the code markers [code]Results[/code]. This will let us know how Mint sees your hardware.
cieggi wrote: ⤴Sun Apr 11, 2021 2:11 amI put the Cubi in sleep mode (standby)
How are you doing this?
cieggi wrote: ⤴Sun Apr 11, 2021 2:11 amWhen I press the power button to wake up, it actually starts but after few seconds it goes again in standby.
If there is nothing in your info (requested above) which indicates an issue, we would probably start checking logs to see what is happening.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
cieggi
Level 1
Level 1
Posts: 21
Joined: Sun Apr 11, 2021 2:00 am

Re: Auto-standby after wake up

Post by cieggi »

Hello,
below the requested info.
I put the system in standby pressing the power button, which is set to "sleep" the system.
What logs can I try to check? Do you have any tip?

Code: Select all

System:
  Kernel: 5.4.0-71-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: Micro-Star product: Cubi N 8GL (MS-B171) v: 1.1 
  serial: <filter> 
  Mobo: Micro-Star model: MS-B1711 v: 1.1 serial: <filter> 
  UEFI: American Megatrends v: 8.60 date: 08/26/2020 
Battery:
  Device-1: hidpp_battery_0 model: Logitech M570 serial: <filter> 
  charge: 40% rechargeable: yes status: Discharging 
CPU:
  Topology: Quad Core model: Intel Pentium Silver N5000 bits: 64 type: MCP 
  arch: Goldmont Plus rev: 1 L2 cache: 4096 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8755 
  Speed: 2587 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 2564 2: 2480 
  3: 2604 4: 2536 
Graphics:
  Device-1: Intel UHD Graphics 605 vendor: Micro-Star MSI driver: i915 
  v: kernel bus ID: 00:02.0 chip ID: 8086:3184 
  Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel UHD Graphics 605 (GLK 3) v: 4.6 Mesa 20.2.6 
  direct render: Yes 
Audio:
  Device-1: Intel vendor: Micro-Star MSI driver: snd_hda_intel v: kernel 
  bus ID: 00:0e.0 chip ID: 8086:3198 
  Sound Server: ALSA v: k5.4.0-71-generic 
Network:
  Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi 
  v: kernel port: f040 bus ID: 05:00.0 chip ID: 8086:24fb 
  IF: wlo1 state: down mac: <filter> 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Micro-Star MSI driver: r8169 v: kernel port: e000 bus ID: 06:00.0 
  chip ID: 10ec:8168 
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IF-ID-1: docker0 state: down mac: <filter> 
Drives:
  Local Storage: total: 456.46 GiB used: 59.48 GiB (13.0%) 
  ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP510 size: 223.57 GiB 
  speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: ECFM22.5 scheme: GPT 
  ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR 
Partition:
  ID-1: / size: 231.00 GiB used: 59.40 GiB (25.7%) fs: btrfs dev: /dev/sda1 
  ID-2: /home size: 231.00 GiB used: 59.40 GiB (25.7%) fs: btrfs 
  dev: /dev/sda1 
  ID-3: swap-1 size: 1.88 GiB used: 51.9 MiB (2.7%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 54.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 
  1: deb [arch=amd64] https://download.docker.com/linux/ubuntu focal stable
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
  1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/jami-main.list 
  1: deb https://dl.jami.net/nightly/ubuntu_20.04 jami main
  Active apt repos in: /etc/apt/sources.list.d/nextcloud-devs-client-focal.list 
  1: deb http://ppa.launchpad.net/nextcloud-devs/client/ubuntu focal main
  No active apt repos in: /etc/apt/sources.list.d/nilarimogard-webupd8-focal.list 
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com ulyssa main upstream import backport
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/sebastian-stenzel-cryptomator-focal.list 
  1: deb http://ppa.launchpad.net/sebastian-stenzel/cryptomator/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
  1: deb https://linux.teamviewer.com/deb stable main
Info:
  Processes: 287 Uptime: 1d 5h 03m Memory: 7.58 GiB used: 2.71 GiB (35.7%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38
Top
User avatar
SMG
Level 25
Level 25
Posts: 31776
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Auto-standby after wake up

Post by SMG »

cieggi wrote: ⤴Sun Apr 18, 2021 2:39 pmWhat logs can I try to check? Do you have any tip?
If you are able to keep the computer awake after pressing the button, you can run dmesg -T | tail -200 in a terminal to see the last 200 lines of the journal. I do not know the specifics of your computer, so you may not need that many lines to see what is waking/sleeping the system. You can change the last number to get a different amount of output.

If you have to re-power the computer, the following command will list the journal output of the prior boot cycle (for which you killed the power) in reverse order (so the reason it would not wake up should be near the top) and print it to termbin. You can post the url returned in your next post if you would like others to help you analyze the data.
journalctl -rb -1 | nc termbin.com 9999
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
cieggi
Level 1
Level 1
Posts: 21
Joined: Sun Apr 11, 2021 2:00 am

Re: Auto-standby after wake up

Post by cieggi »

Thank you. Now I'm starting to monitor the standby and when this happens again I'll check the logs
Top
cieggi
Level 1
Level 1
Posts: 21
Joined: Sun Apr 11, 2021 2:00 am

Re: Auto-standby after wake up

Post by cieggi »

SMG wrote: ⤴Sun Apr 18, 2021 2:54 pm
cieggi wrote: ⤴Sun Apr 18, 2021 2:39 pmWhat logs can I try to check? Do you have any tip?
If you are able to keep the computer awake after pressing the button, you can run dmesg -T | tail -200 in a terminal to see the last 200 lines of the journal. I do not know the specifics of your computer, so you may not need that many lines to see what is waking/sleeping the system. You can change the last number to get a different amount of output.

If you have to re-power the computer, the following command will list the journal output of the prior boot cycle (for which you killed the power) in reverse order (so the reason it would not wake up should be near the top) and print it to termbin. You can post the url returned in your next post if you would like others to help you analyze the data.
journalctl -rb -1 | nc termbin.com 9999
Hello,
the issue happened again. I was able to keep the system awake but the command dmesg -T | tail -200 only returns messages from the previous session:

Code: Select all

[ven apr 23 06:18:38 2021] sd 0:0:0:0: [sda] Stopping disk
[ven apr 23 06:18:38 2021] ACPI: Preparing to enter system sleep state S3
[ven apr 23 06:18:38 2021] PM: Saving platform NVS memory
[ven apr 23 06:18:38 2021] Disabling non-boot CPUs ...
[ven apr 23 06:18:38 2021] smpboot: CPU 1 is now offline
[ven apr 23 06:18:38 2021] smpboot: CPU 2 is now offline
[ven apr 23 06:18:38 2021] smpboot: CPU 3 is now offline
[ven apr 23 06:18:38 2021] ACPI: Low-level resume complete
[ven apr 23 06:18:38 2021] PM: Restoring platform NVS memory
[ven apr 23 06:18:38 2021] Enabling non-boot CPUs ...
[ven apr 23 06:18:38 2021] x86: Booting SMP configuration:
[ven apr 23 06:18:38 2021] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ven apr 23 06:18:38 2021] CPU1 is up
[ven apr 23 06:18:38 2021] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ven apr 23 06:18:38 2021] CPU2 is up
[ven apr 23 06:18:38 2021] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ven apr 23 06:18:38 2021] CPU3 is up
[ven apr 23 06:18:38 2021] ACPI: Waking up from system sleep state S3
[ven apr 23 06:18:38 2021] acpi LNXPOWER:13: Turning ON
[ven apr 23 06:18:38 2021] acpi LNXPOWER:18: Turning ON
[ven apr 23 06:18:38 2021] sd 0:0:0:0: [sda] Starting disk
[ven apr 23 06:18:38 2021] nvme nvme0: Shutdown timeout set to 10 seconds
[ven apr 23 06:18:38 2021] nvme nvme0: 4/0/0 default/read/poll queues
[ven apr 23 06:18:38 2021] acpi LNXPOWER:1a: Turning OFF
[ven apr 23 06:18:38 2021] acpi LNXPOWER:19: Turning OFF
[ven apr 23 06:18:38 2021] acpi LNXPOWER:17: Turning OFF
[ven apr 23 06:18:38 2021] acpi LNXPOWER:16: Turning OFF
[ven apr 23 06:18:38 2021] acpi LNXPOWER:14: Turning OFF
[ven apr 23 06:18:38 2021] acpi LNXPOWER:12: Turning OFF
[ven apr 23 06:18:38 2021] acpi LNXPOWER:10: Turning OFF
[ven apr 23 06:18:38 2021] acpi LNXPOWER:0d: Turning OFF
[ven apr 23 06:18:38 2021] OOM killer enabled.
[ven apr 23 06:18:38 2021] Restarting tasks ... done.
[ven apr 23 06:18:38 2021] thermal thermal_zone0: failed to read out thermal zone (-61)
[ven apr 23 06:18:38 2021] video LNXVIDEO:00: Restoring backlight state
[ven apr 23 06:18:38 2021] PM: suspend exit
[ven apr 23 06:18:38 2021] ata2: SATA link down (SStatus 4 SControl 300)
[ven apr 23 06:18:38 2021] Generic FE-GE Realtek PHY r8169-600:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-600:00, irq=IGNORE)
[ven apr 23 06:18:39 2021] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ven apr 23 06:18:39 2021] ata1.00: supports DRM functions and may not be fully accessible
[ven apr 23 06:18:39 2021] ata1.00: supports DRM functions and may not be fully accessible
[ven apr 23 06:18:39 2021] ata1.00: configured for UDMA/133
[ven apr 23 06:18:39 2021] ata1.00: Enabling discard_zeroes_data
[ven apr 23 06:18:39 2021] PM: suspend entry (deep)
[ven apr 23 06:18:39 2021] r8169 0000:06:00.0 enp6s0: Link is Down
[ven apr 23 06:18:39 2021] Filesystems sync: 0.055 seconds
[ven apr 23 06:18:39 2021] Freezing user space processes ... (elapsed 0.005 seconds) done.
[ven apr 23 06:18:39 2021] OOM killer disabled.
[ven apr 23 06:18:39 2021] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ven apr 23 06:18:39 2021] printk: Suspending console(s) (use no_console_suspend to debug)
[ven apr 23 06:18:39 2021] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ven apr 23 06:18:39 2021] sd 0:0:0:0: [sda] Stopping disk
[ven apr 23 06:18:39 2021] ACPI: Preparing to enter system sleep state S3
[ven apr 23 06:18:39 2021] PM: Saving platform NVS memory
[ven apr 23 06:18:39 2021] Disabling non-boot CPUs ...
[ven apr 23 06:18:39 2021] smpboot: CPU 1 is now offline
[ven apr 23 06:18:39 2021] smpboot: CPU 2 is now offline
[ven apr 23 06:18:39 2021] smpboot: CPU 3 is now offline
[ven apr 23 06:18:39 2021] ACPI: Low-level resume complete
[ven apr 23 06:18:39 2021] PM: Restoring platform NVS memory
[ven apr 23 06:18:39 2021] Enabling non-boot CPUs ...
[ven apr 23 06:18:39 2021] x86: Booting SMP configuration:
[ven apr 23 06:18:39 2021] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ven apr 23 06:18:39 2021] CPU1 is up
[ven apr 23 06:18:39 2021] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ven apr 23 06:18:39 2021] CPU2 is up
[ven apr 23 06:18:39 2021] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ven apr 23 06:18:39 2021] CPU3 is up
[ven apr 23 06:18:39 2021] ACPI: Waking up from system sleep state S3
[ven apr 23 06:18:39 2021] acpi LNXPOWER:13: Turning ON
[ven apr 23 06:18:39 2021] acpi LNXPOWER:18: Turning ON
[ven apr 23 06:18:39 2021] sd 0:0:0:0: [sda] Starting disk
[ven apr 23 06:18:39 2021] nvme nvme0: Shutdown timeout set to 10 seconds
[ven apr 23 06:18:39 2021] nvme nvme0: 4/0/0 default/read/poll queues
[ven apr 23 06:18:39 2021] acpi LNXPOWER:1a: Turning OFF
[ven apr 23 06:18:39 2021] acpi LNXPOWER:19: Turning OFF
[ven apr 23 06:18:39 2021] acpi LNXPOWER:17: Turning OFF
[ven apr 23 06:18:39 2021] acpi LNXPOWER:16: Turning OFF
[ven apr 23 06:18:39 2021] acpi LNXPOWER:14: Turning OFF
[ven apr 23 06:18:39 2021] acpi LNXPOWER:12: Turning OFF
[ven apr 23 06:18:39 2021] acpi LNXPOWER:10: Turning OFF
[ven apr 23 06:18:39 2021] acpi LNXPOWER:0d: Turning OFF
[ven apr 23 06:18:39 2021] OOM killer enabled.
[ven apr 23 06:18:39 2021] Restarting tasks ... done.
[ven apr 23 06:18:39 2021] thermal thermal_zone0: failed to read out thermal zone (-61)
[ven apr 23 06:18:39 2021] video LNXVIDEO:00: Restoring backlight state
[ven apr 23 06:18:39 2021] PM: suspend exit
[ven apr 23 06:18:39 2021] Generic FE-GE Realtek PHY r8169-600:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-600:00, irq=IGNORE)
[ven apr 23 06:18:39 2021] ata2: SATA link down (SStatus 4 SControl 300)
[ven apr 23 06:18:40 2021] PM: suspend entry (deep)
[ven apr 23 06:18:40 2021] r8169 0000:06:00.0 enp6s0: Link is Down
[ven apr 23 06:18:40 2021] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ven apr 23 06:18:40 2021] ata1.00: supports DRM functions and may not be fully accessible
[ven apr 23 06:18:40 2021] ata1.00: supports DRM functions and may not be fully accessible
[ven apr 23 06:18:40 2021] ata1.00: configured for UDMA/133
[ven apr 23 06:18:40 2021] ata1.00: Enabling discard_zeroes_data
[ven apr 23 06:18:40 2021] Filesystems sync: 0.163 seconds
[ven apr 23 06:18:40 2021] Freezing user space processes ... (elapsed 0.006 seconds) done.
[ven apr 23 06:18:40 2021] OOM killer disabled.
[ven apr 23 06:18:40 2021] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ven apr 23 06:18:40 2021] printk: Suspending console(s) (use no_console_suspend to debug)
[ven apr 23 06:18:40 2021] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ven apr 23 06:18:40 2021] sd 0:0:0:0: [sda] Stopping disk
[ven apr 23 06:18:40 2021] ACPI: Preparing to enter system sleep state S3
[ven apr 23 06:18:40 2021] PM: Saving platform NVS memory
[ven apr 23 06:18:40 2021] Disabling non-boot CPUs ...
[ven apr 23 06:18:40 2021] smpboot: CPU 1 is now offline
[ven apr 23 06:18:40 2021] smpboot: CPU 2 is now offline
[ven apr 23 06:18:40 2021] smpboot: CPU 3 is now offline
[ven apr 23 06:18:40 2021] ACPI: Low-level resume complete
[ven apr 23 06:18:40 2021] PM: Restoring platform NVS memory
[ven apr 23 06:18:40 2021] Enabling non-boot CPUs ...
[ven apr 23 06:18:40 2021] x86: Booting SMP configuration:
[ven apr 23 06:18:40 2021] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ven apr 23 06:18:40 2021] CPU1 is up
[ven apr 23 06:18:40 2021] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ven apr 23 06:18:40 2021] CPU2 is up
[ven apr 23 06:18:40 2021] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ven apr 23 06:18:40 2021] CPU3 is up
[ven apr 23 06:18:40 2021] ACPI: Waking up from system sleep state S3
[ven apr 23 06:18:40 2021] acpi LNXPOWER:13: Turning ON
[ven apr 23 06:18:40 2021] acpi LNXPOWER:18: Turning ON
[ven apr 23 06:18:40 2021] sd 0:0:0:0: [sda] Starting disk
[ven apr 23 06:18:40 2021] nvme nvme0: Shutdown timeout set to 10 seconds
[ven apr 23 06:18:40 2021] nvme nvme0: 4/0/0 default/read/poll queues
[ven apr 23 06:18:40 2021] acpi LNXPOWER:1a: Turning OFF
[ven apr 23 06:18:40 2021] acpi LNXPOWER:19: Turning OFF
[ven apr 23 06:18:40 2021] acpi LNXPOWER:17: Turning OFF
[ven apr 23 06:18:40 2021] acpi LNXPOWER:16: Turning OFF
[ven apr 23 06:18:40 2021] acpi LNXPOWER:14: Turning OFF
[ven apr 23 06:18:40 2021] acpi LNXPOWER:12: Turning OFF
[ven apr 23 06:18:40 2021] acpi LNXPOWER:10: Turning OFF
[ven apr 23 06:18:40 2021] acpi LNXPOWER:0d: Turning OFF
[ven apr 23 06:18:40 2021] OOM killer enabled.
[ven apr 23 06:18:40 2021] Restarting tasks ... done.
[ven apr 23 06:18:40 2021] thermal thermal_zone0: failed to read out thermal zone (-61)
[ven apr 23 06:18:40 2021] video LNXVIDEO:00: Restoring backlight state
[ven apr 23 06:18:40 2021] PM: suspend exit
[ven apr 23 06:18:41 2021] ata2: SATA link down (SStatus 4 SControl 300)
[ven apr 23 06:18:41 2021] Generic FE-GE Realtek PHY r8169-600:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-600:00, irq=IGNORE)
[ven apr 23 06:18:41 2021] PM: suspend entry (deep)
[ven apr 23 06:18:41 2021] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ven apr 23 06:18:41 2021] ata1.00: supports DRM functions and may not be fully accessible
[ven apr 23 06:18:41 2021] ata1.00: supports DRM functions and may not be fully accessible
[ven apr 23 06:18:41 2021] ata1.00: configured for UDMA/133
[ven apr 23 06:18:41 2021] ata1.00: Enabling discard_zeroes_data
[ven apr 23 06:18:41 2021] r8169 0000:06:00.0 enp6s0: Link is Down
[ven apr 23 06:18:41 2021] Filesystems sync: 0.094 seconds
[ven apr 23 06:18:41 2021] Freezing user space processes ... (elapsed 0.025 seconds) done.
[ven apr 23 06:18:41 2021] OOM killer disabled.
[ven apr 23 06:18:41 2021] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
[ven apr 23 06:18:41 2021] printk: Suspending console(s) (use no_console_suspend to debug)
[ven apr 23 06:18:41 2021] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ven apr 23 06:18:41 2021] sd 0:0:0:0: [sda] Stopping disk
[ven apr 23 06:18:41 2021] ACPI: Preparing to enter system sleep state S3
[ven apr 23 06:18:41 2021] PM: Saving platform NVS memory
[ven apr 23 06:18:41 2021] Disabling non-boot CPUs ...
[ven apr 23 06:18:41 2021] smpboot: CPU 1 is now offline
[ven apr 23 06:18:41 2021] smpboot: CPU 2 is now offline
[ven apr 23 06:18:41 2021] smpboot: CPU 3 is now offline
[ven apr 23 06:18:41 2021] ACPI: Low-level resume complete
[ven apr 23 06:18:41 2021] PM: Restoring platform NVS memory
[ven apr 23 06:18:41 2021] Enabling non-boot CPUs ...
[ven apr 23 06:18:41 2021] x86: Booting SMP configuration:
[ven apr 23 06:18:41 2021] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ven apr 23 06:18:41 2021] CPU1 is up
[ven apr 23 06:18:41 2021] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ven apr 23 06:18:41 2021] CPU2 is up
[ven apr 23 06:18:41 2021] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ven apr 23 06:18:41 2021] CPU3 is up
[ven apr 23 06:18:41 2021] ACPI: Waking up from system sleep state S3
[ven apr 23 06:18:41 2021] acpi LNXPOWER:13: Turning ON
[ven apr 23 06:18:41 2021] acpi LNXPOWER:18: Turning ON
[ven apr 23 06:18:41 2021] sd 0:0:0:0: [sda] Starting disk
[ven apr 23 06:18:41 2021] nvme nvme0: Shutdown timeout set to 10 seconds
[ven apr 23 06:18:41 2021] nvme nvme0: 4/0/0 default/read/poll queues
[ven apr 23 06:18:42 2021] acpi LNXPOWER:1a: Turning OFF
[ven apr 23 06:18:42 2021] acpi LNXPOWER:19: Turning OFF
[ven apr 23 06:18:42 2021] acpi LNXPOWER:17: Turning OFF
[ven apr 23 06:18:42 2021] acpi LNXPOWER:16: Turning OFF
[ven apr 23 06:18:42 2021] acpi LNXPOWER:14: Turning OFF
[ven apr 23 06:18:42 2021] acpi LNXPOWER:12: Turning OFF
[ven apr 23 06:18:42 2021] acpi LNXPOWER:10: Turning OFF
[ven apr 23 06:18:42 2021] acpi LNXPOWER:0d: Turning OFF
[ven apr 23 06:18:42 2021] OOM killer enabled.
[ven apr 23 06:18:42 2021] Restarting tasks ... 
[ven apr 23 06:18:42 2021] ata2: SATA link down (SStatus 4 SControl 300)
[ven apr 23 06:18:42 2021] done.
[ven apr 23 06:18:42 2021] thermal thermal_zone0: failed to read out thermal zone (-61)
[ven apr 23 06:18:42 2021] video LNXVIDEO:00: Restoring backlight state
[ven apr 23 06:18:42 2021] PM: suspend exit
[ven apr 23 06:18:42 2021] Generic FE-GE Realtek PHY r8169-600:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-600:00, irq=IGNORE)
[ven apr 23 06:18:42 2021] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ven apr 23 06:18:42 2021] ata1.00: supports DRM functions and may not be fully accessible
[ven apr 23 06:18:42 2021] ata1.00: supports DRM functions and may not be fully accessible
[ven apr 23 06:18:42 2021] ata1.00: configured for UDMA/133
[ven apr 23 06:18:42 2021] ata1.00: Enabling discard_zeroes_data
[ven apr 23 06:18:42 2021] r8169 0000:06:00.0 enp6s0: Link is Down
[ven apr 23 06:18:45 2021] r8169 0000:06:00.0 enp6s0: Link is Up - 1Gbps/Full - flow control rx/tx
[ven apr 23 06:18:45 2021] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
I woke up the system @ 08:13 more or less. As you can see, there is not messages near this specific time.
Also the journalctl command shows "old" data as the most recent info is from April 22
Top
User avatar
SMG
Level 25
Level 25
Posts: 31776
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Auto-standby after wake up

Post by SMG »

cieggi wrote: ⤴Sat Apr 24, 2021 2:18 amthe issue happened again. I was able to keep the system awake but the command dmesg -T | tail -200 only returns messages from the previous session:
That command returns the last 200 lines the computer has experienced. I am not sure what you mean by "session" as it is all the same boot cycle since you did not shut down the computer. (You only put the computer to sleep, so it's still the same boot cycle session.)
cieggi wrote: ⤴Sat Apr 24, 2021 2:18 amI woke up the system @ 08:13 more or less. As you can see, there is not messages near this specific time.
When did you put the computer to sleep? These messages seem to indicate the computer never successfully went to sleep. It kept trying, but something kept waking it. Or maybe it was the computer trying to wake up, but something kept putting it to sleep? Not sure because of what you have indicated about the time not being what you expected.
cieggi wrote: ⤴Sat Apr 24, 2021 2:18 amAlso the journalctl command shows "old" data as the most recent info is from April 22
That command shows information from the prior boot cycle. If the last time you shut down and restarted the computer was April 22, then that is the date it will show.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
User avatar
SMG
Level 25
Level 25
Posts: 31776
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Auto-standby after wake up

Post by SMG »

Have you checked to see if there is a newer BIOS/UEFI for your computer? Often wake/sleep commands interact with ACPI tables which can be affected by firmware updates.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
cieggi
Level 1
Level 1
Posts: 21
Joined: Sun Apr 11, 2021 2:00 am

Re: Auto-standby after wake up

Post by cieggi »

SMG wrote: ⤴Sat Apr 24, 2021 1:12 pm Have you checked to see if there is a newer BIOS/UEFI for your computer? Often wake/sleep commands interact with ACPI tables which can be affected by firmware updates.
Hello. yes, I've the last bios update (Aug 2020) and asked to their customer service but unfortunately MSI doesn't provide Linux support for this Cubi
Top
cieggi
Level 1
Level 1
Posts: 21
Joined: Sun Apr 11, 2021 2:00 am

Re: Auto-standby after wake up

Post by cieggi »

Just to complete the thread, the problem seems reduced after the last updates. It still happens sometimes, but the system permanently wake up after 1-2 attempts. It doesn't require a forced reboot anymore.

It is a minor issue now, not a big problem in everyday usage
Top
Locked

Return to “Hardware Support”