Peripherals do not wake up after idle; cannot resume

Report Bugs, Issues and non- package Requests
Message
Author
Ptericles
Posts: 5
Joined: Tue Aug 25, 2020 6:44 pm

Peripherals do not wake up after idle; cannot resume

#1 Post by Ptericles »

amd64
Nothing was running except background services such as SMB
I think the system goes to the lock screen after an idle timeout, but I tried to disable sleep modes.
System sleep mode: Hibernate When inactive for Never
Blank screen after 10 minutes
Put to sleep after Never
Switch off after Never
Reduce brightness after Never
Num lock on
I added
#ahs hardware stack repo
deb http://la.mxrepo.com/mx/repo/ bookworm ahs
to /etc/apt/sources.list.d/mx.list and enabled it in the MX Repo Manager

I added usbcore.autosuspend=-1 to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash resume=UUID=337a3003-7a3d-4e07-90d6-c5d255760aa9 resume_offset=88145920 usbcore.autosuspend=-1"
in /etc/default/grub

I still need to test a PS/2 keyboard, but when I first plugged in the PS/2 keyboard, the num lock light didn't change, but I haven't tested after a restart.

Peripherals do not wake up after idle, so I can't press the "Any" key ;) to wake the computer back up.

Code: Select all

System:
  Kernel: 6.1.0-18-amd64 [6.1.76-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-amd64 root=UUID=<filter> ro
    mem_sleep_default=s2idle quiet splash resume=UUID=<filter> resume_offset=88145920
    usbcore.autosuspend=-1
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.2_x64 Libretto October 15  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: Gigabyte model: AX370-Gaming K7 serial: <superuser required> BIOS: American
    Megatrends LLC. v: F51h date: 07/27/2022
CPU:
  Info: model: AMD Ryzen 7 1700 bits: 64 type: MT MCP arch: Zen level: v3 note: check
    built: 2017-19 process: GF 14nm family: 0x17 (23) model-id: 1 stepping: 1 microcode: 0x8001138
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 768 KiB
    desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 1476 high: 1550 min/max: 1550/3000 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1377 2: 1376 3: 1550 4: 1411 5: 1377 6: 1550
    7: 1550 8: 1550 9: 1550 10: 1550 11: 1378 12: 1550 13: 1378 14: 1377 15: 1550 16: 1550
    bogomips: 95996
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT vulnerable
  Type: spec_rstack_overflow mitigation: safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: disabled, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GM200 [GeForce GTX 980 Ti] vendor: Micro-Star MSI driver: nouveau v: kernel
    non-free: 530.xx+ status: current (as of 2023-03) arch: Maxwell code: GMxxx process: TSMC 28nm
    built: 2014-19 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
    active: DP-3,DVI-I-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 07:00.0 chip-ID: 10de:17c8
    class-ID: 0300 temp: 59.0 C
  Device-2: Logitech QuickCam Pro 5000 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-7:2
    chip-ID: 046d:08ce class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2970x1680 s-dpi: 96 s-size: 786x445mm (30.94x17.52") s-diag: 903mm (35.56")
  Monitor-1: DP-3 pos: top-right model: HP LA2205 serial: <filter> built: 2010 res: 1050x1680
    hz: 60 dpi: 90 gamma: 1.2 size: 296x473mm (11.65x18.62") diag: 558mm (22") ratio: 16:10 modes:
    max: 1680x1050 min: 720x400
  Monitor-2: DVI-I-1 pos: bottom-l model: Dell E2214H serial: <filter> built: 2015 res: 1920x1080
    hz: 60 dpi: 102 gamma: 1.2 size: 477x268mm (18.78x10.55") diag: 547mm (21.5") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 4.3 Mesa 23.1.2-1~mx23ahs renderer: NV120 direct-render: Yes
Audio:
  Device-1: NVIDIA GM200 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel
    bus-ID: 1-7:2 v: kernel chip-ID: 046d:08ce pcie: gen: 1 class-ID: 0102 serial: <filter>
    speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 07:00.1 chip-ID: 10de:0fb0
    class-ID: 0403
  Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 09:00.3 chip-ID: 1022:1457 class-ID: 0403
  Device-3: Logitech QuickCam Pro 5000 type: USB driver: snd-usb-audio,uvcvideo
  Device-4: ShanWan Gioteck EX-05 Headset type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus-ID: 3-1:2 chip-ID: 25f0:e511 class-ID: 0300
  API: ALSA v: k6.1.0-18-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 04:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: eth1 state: down mac: <filter>
  Device-2: Qualcomm Atheros Killer E2500 Gigabit Ethernet vendor: Gigabyte driver: alx v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 05:00.0 chip-ID: 1969:e0b1
    class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-3: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus-ID: 1-8:3
    chip-ID: 148f:7601 class-ID: 0000 serial: <filter>
  IF: wlan0 state: down mac: <filter>
Drives:
  Local Storage: total: 4.56 TiB used: 59.07 GiB (1.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 840 PRO Series size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 5B0Q
    scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 840 Series size: 465.76 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 7B0Q scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: HGST (Hitachi) model: HDN726040ALE614 size: 3.64 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: W7JH scheme: GPT
Partition:
  ID-1: / raw-size: 465.76 GiB size: 457.38 GiB (98.20%) used: 59.07 GiB (12.9%) fs: ext4
    dev: /dev/sdb1 maj-min: 8:17
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 19.51 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 38.5 C mobo: N/A gpu: nouveau temp: 59.0 C
  Fan Speeds (RPM): N/A gpu: nouveau fan: 0
Repos:
  Packages: 2091 pm: dpkg pkgs: 2082 libs: 1053 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 9
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb https://mxrepo.com/mx/repo/ bookworm ahs
Info:
  Processes: 328 Uptime: 17m wakeups: 13136 Memory: 15.51 GiB used: 3.09 GiB (19.9%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

Charlie Brown

Re: Peripherals do not wake up after idle; cannot resume

#2 Post by Charlie Brown »

Especially if it looks like a freezing (just the pointer is movable on a black screen etc..) remove the problematic xfce4-screensaver (long time known issue).. (No matter it was already disabled etc... )

Ptericles
Posts: 5
Joined: Tue Aug 25, 2020 6:44 pm

Re: Peripherals do not wake up after idle; cannot resume

#3 Post by Ptericles »

Thanks for your reply Charlie Brown.
I uninstalled xfce4-screensaver.
The good news is the keyboard is responding to numlock on and off, but that's all I can do. MX Linux still won't wake up.

User avatar
CharlesV
Global Moderator
Posts: 7377
Joined: Sun Jul 07, 2019 5:11 pm

Re: Peripherals do not wake up after idle; cannot resume

#4 Post by CharlesV »

Try moving the mouse, and then type in your password and hit enter

I saw something like this a while back, where the computer was asking for the password on waking up, but no dialog was visible. Once I type in the password, everything was back.
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

Charlie Brown

Re: Peripherals do not wake up after idle; cannot resume

#5 Post by Charlie Brown »

What if you suspend with this?

Code: Select all

sudo pm-suspend
Also, what if you install the most recent (just "while you're at it") Liquorix kernel from "MX Package Installer" (the initial tab, takes 2 clicks only) and reboot and try with that?

Ptericles
Posts: 5
Joined: Tue Aug 25, 2020 6:44 pm

Re: Peripherals do not wake up after idle; cannot resume

#6 Post by Ptericles »

I tried the Liquorix 64 bit (ahs updates package) and the Liquorix 6.9.11-1 64 bit package.

The result was /var/kern.log.1 filling up the drive to 197.8 GB. It seems to be back to 354.7 KB now, but syslog.2.gz and kern.log.2.gz are 11.6 GB.

It seems like your system encountered a Non-Maskable Interrupt (NMI) which triggered a kernel panic. The call trace you provided shows the sequence of function calls leading up to the issue. NMIs are often used to handle critical hardware errors.

The specific error message `rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks` indicates that the Read-Copy-Update (RCU) subsystem detected a stall, which can happen if a CPU is not responding as expected¹.

To troubleshoot this issue, you might want to:
1. Check for hardware issues: Ensure that all hardware components are properly seated and functioning.
2. Update your BIOS and firmware: Sometimes, updating the BIOS and firmware can resolve such issues.
3. Review recent changes: If you recently made any changes to your system (e.g., new hardware, software updates), consider reverting them to see if the issue persists.
4. Consult logs: Look at other system logs around the time of the error for additional clues.

If the problem continues, you might need to delve deeper into kernel debugging or seek help from the Linux community or your hardware manufacturer.

Is there anything specific you'd like to focus on or any other details you can provide about the issue?

¹: [NMI Trace Events — The Linux Kernel documentation](https://www.kernel.org/doc/html/latest/ ... s-nmi.html)

Source: Conversation with Copilot, 8/1/2024
(1) NMI Trace Events — The Linux Kernel documentation. https://www.kernel.org/doc/html/latest/ ... s-nmi.html.
(2) Call trace when loading a module in Linux - Stack Overflow. https://stackoverflow.com/questions/621 ... e-in-linux.
(3) Analyzing Linux kernel crash dumps with crash - The one tutorial that .... https://www.dedoimedo.com/computers/crash-analyze.html.


2024-06-14T22:49:02.255614-07:00 Ryzen7mx kernel: Call Trace:
2024-06-14T22:49:02.255619-07:00 Ryzen7mx kernel: <NMI>
2024-06-14T22:49:02.255646-07:00 Ryzen7mx kernel: ? nmi_cpu_backtrace+0x95/0x110
2024-06-14T22:49:02.255649-07:00 Ryzen7mx kernel: ? nmi_cpu_backtrace_handler+0xd/0x20
2024-06-14T22:49:02.255655-07:00 Ryzen7mx kernel: ? nmi_handle+0x5d/0x150
2024-06-14T22:49:02.255660-07:00 Ryzen7mx kernel: ? default_do_nmi+0x42/0x1e0
2024-06-14T22:49:02.255663-07:00 Ryzen7mx kernel: ? exc_nmi+0x1a5/0x260
2024-06-14T22:49:02.255666-07:00 Ryzen7mx kernel: ? end_repeat_nmi+0xf/0x60
2024-06-14T22:49:02.255671-07:00 Ryzen7mx kernel: ? smp_call_function_many_cond+0x122/0x4e0
2024-06-14T22:49:02.255676-07:00 Ryzen7mx kernel: ? smp_call_function_many_cond+0x122/0x4e0
2024-06-14T22:49:02.255680-07:00 Ryzen7mx kernel: ? smp_call_function_many_cond+0x122/0x4e0
2024-06-14T22:49:02.255684-07:00 Ryzen7mx kernel: </NMI>
2024-06-14T22:49:02.255689-07:00 Ryzen7mx kernel: <TASK>
2024-06-14T22:49:02.255697-07:00 Ryzen7mx kernel: ? __pfx_do_sync_core+0x10/0x10
2024-06-14T22:49:02.255700-07:00 Ryzen7mx kernel: on_each_cpu_cond_mask+0x20/0x40
2024-06-14T22:49:02.255703-07:00 Ryzen7mx kernel: text_poke_bp_batch+0xb0/0x2d0
2024-06-14T22:49:02.255708-07:00 Ryzen7mx kernel: ? ip_finish_output+0x55/0x600
2024-06-14T22:49:02.255711-07:00 Ryzen7mx kernel: ? arch_jump_label_transform_queue+0x53/0x80
2024-06-14T22:49:02.255717-07:00 Ryzen7mx kernel: text_poke_finish+0x1b/0x30
2024-06-14T22:49:02.255720-07:00 Ryzen7mx kernel: arch_jump_label_transform_apply+0x16/0x30
2024-06-14T22:49:02.255723-07:00 Ryzen7mx kernel: jump_label_update+0x9c/0x100
2024-06-14T22:49:02.255727-07:00 Ryzen7mx kernel: static_key_enable+0x61/0x90
2024-06-14T22:49:02.255729-07:00 Ryzen7mx kernel: process_one_work+0x16b/0x320
2024-06-14T22:49:02.255737-07:00 Ryzen7mx kernel: worker_thread+0x359/0x4d0
2024-06-14T22:49:02.255740-07:00 Ryzen7mx kernel: ? __pfx_worker_thread+0x10/0x10
2024-06-14T22:49:02.255744-07:00 Ryzen7mx kernel: kthread+0xe4/0x110
2024-06-14T22:49:02.255746-07:00 Ryzen7mx kernel: ? __pfx_kthread+0x10/0x10
2024-06-14T22:49:02.255761-07:00 Ryzen7mx kernel: ret_from_fork+0x30/0x50
2024-06-14T22:49:02.255766-07:00 Ryzen7mx kernel: ? __pfx_kthread+0x10/0x10
2024-06-14T22:49:02.255770-07:00 Ryzen7mx kernel: ret_from_fork_asm+0x1b/0x30
2024-06-14T22:49:02.255775-07:00 Ryzen7mx kernel: </TASK>
2024-06-14T22:49:02.330566-07:00 Ryzen7mx kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks:
{ 4-.... } 4710 jiffies s: 733 root: 0x1/.
2024-06-14T22:49:02.330578-07:00 Ryzen7mx kernel: rcu: blocking rcu_node structures (internal RCU debug): l=1:0-15
:0x10/.
2024-06-14T22:49:02.330581-07:00 Ryzen7mx kernel: Sending NMI from CPU 7 to CPUs 4:
2024-06-14T22:49:02.330583-07:00 Ryzen7mx kernel: NMI backtrace for cpu 4
2024-06-14T22:49:02.330586-07:00 Ryzen7mx kernel: CPU: 4 PID: 182611 Comm: kworker/4:0 Not tainted 6.8.12-1-liquor
ix-amd64 #1 liquorix 6.8-18~mx23ahs
2024-06-14T22:49:02.330588-07:00 Ryzen7mx kernel: Hardware name: Gigabyte Technology Co., Ltd. AX370-Gaming K7/AX3
70-Gaming K7, BIOS F51h 07/27/2022
2024-06-14T22:49:02.330591-07:00 Ryzen7mx kernel: Workqueue: events netstamp_clear
2024-06-14T22:49:02.330624-07:00 Ryzen7mx kernel: RIP: 0010:smp_call_function_many_cond+0x122/0x4e0
2024-06-14T22:49:02.330627-07:00 Ryzen7mx kernel: Code: d0 48 89 df e8 2f 10 4f 00 3b 05 99 2f e4 01 73 26 48 63 d
0 49 8b 75 00 48 03 34 d5 60 3c 72 82 8b 56 08 83 e2 01 74 0a f3 90 <8b> 4e 08 83 e1 01 75 f6 83 c0 01 eb c1 48 83
c4 50 5b 5d 41 5c 41
2024-06-14T22:49:02.330630-07:00 Ryzen7mx kernel: RSP: 0018:ffffc90019113d58 EFLAGS: 00000202
2024-06-14T22:49:02.330634-07:00 Ryzen7mx kernel: RAX: 0000000000000000 RBX: ffff88842e9340c8 RCX: 000000000000000
1
2024-06-14T22:49:02.330636-07:00 Ryzen7mx kernel: RDX: 0000000000000001 RSI: ffff88842e83a2a0 RDI: ffff88842e9340c
8
2024-06-14T22:49:02.330641-07:00 Ryzen7mx kernel: RBP: ffff88842e9340c0 R08: 0000000000000000 R09: ffffffff82

Post Reply

Return to “Bugs and Non-Package Requests Forum”