System sometimes irreversibly freezes when I try to suspend

kaz49 · 2025-01-15 03:44:55

Hello.

For the past couple months, I've had this problem where whenever I put my laptop to sleep, there's like a 1% chance that the system freezes completely (even sysrq+REISUB doesn't work) and I am forced to hold down the power button to reboot. The screen goes black except for the mouse pointer, which stays on screen and doesn't respond to the touchpad.
It's persisted across multiple kernel versions and I've lost a decent bit of unsaved work to this glitch, so I thought I'd ask for help.

I did a bit of digging in journalctl, and I think I might have found something...? Whenever my laptop successfully sleeps, I see the messages

kaz49-dynabook systemd-sleep[384482]: Successfully froze unit 'user.slice'.
kaz49-dynabook systemd-sleep[384482]: Performing sleep operation 'suspend'...
kaz49-dynabook kernel: PM: suspend entry (s2idle)
kaz49-dynabook kernel: Filesystems sync: 0.045 seconds
kaz49-dynabook kernel: Freezing user space processes
kaz49-dynabook kernel: Freezing user space processes completed (elapsed 0.029 seconds)
kaz49-dynabook kernel: OOM killer disabled.

But when the sleep fails, I see

kaz49-dynabook systemd-sleep[1111480]: Failed to freeze unit 'user.slice': Connection timed out
kaz49-dynabook systemd-sleep[1111480]: Performing sleep operation 'suspend'...
kaz49-dynabook kernel: PM: suspend entry (s2idle)
kaz49-dynabook kernel: Filesystems sync: 0.014 seconds
kaz49-dynabook kernel: Freezing user space processes
kaz49-dynabook kernel: Freezing user space processes failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
kaz49-dynabook kernel: task:plasmashell     state:D stack:0     pid:1092  tgid:1092  ppid:794    flags:0x00004006

and and "OOM killer enabled." after a long stacktrace-looking thing.
Something to do with Plasma misbehaving, perhaps? I can't be sure though, I'm not an expert.

I have full journal logs on my disk, but I wasn't sure if posting them would be a security risk. If I should post the full journal, please do tell me to do that
Thank you in advance for your help!

seth · 2025-01-15 14:45:16

Plasma is waiting for some IO - the journal isn't supposed to contain any sensitive data (sometimes public IPv6 addresses show up), but that's not gaonna be the journal from an incident where

the system freezes completely (even sysrq+REISUB doesn't work) and I am forced to hold down the power button to reboot

because that will preclude the journal from being written to disk.

Looking at the journal to see whether there's anything generally suspcious is the best we can do out of that condition :\

kaz49 · 2025-01-17 02:20:51

I tried looking for more suspicious things in the log myself, but I'm afraid most of it is indecipherable to me.

I've posted the logs online, I'd really appreciate it if you could take a look
Log starting from when I pressed the sleep button (I hope) pastebin.com/wNMW6fjX (22KB)
Full log drive.google.com/file/d/1skkLCOMI5_DKzp … sp=sharing (Warning: 22MB)

Last edited by kaz49 (2025-01-17 02:21:25)

seth · 2025-01-17 10:32:50

Jan 15 11:40:33 kaz49-dynabook systemd-sleep[1111480]: Failed to freeze unit 'user.slice': Connection timed out
Jan 15 11:40:33 kaz49-dynabook systemd-sleep[1111480]: Performing sleep operation 'suspend'...
Jan 15 11:40:33 kaz49-dynabook kernel: PM: suspend entry (s2idle)
Jan 15 11:40:33 kaz49-dynabook kernel: Filesystems sync: 0.014 seconds
Jan 15 11:40:54 kaz49-dynabook kernel: Freezing user space processes
Jan 15 11:40:54 kaz49-dynabook kernel: Freezing user space processes failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
Jan 15 11:40:54 kaz49-dynabook kernel: task:plasmashell     state:D stack:0     pid:1092  tgid:1092  ppid:794    flags:0x00004006
Jan 15 11:40:54 kaz49-dynabook kernel: Call Trace:
Jan 15 11:40:54 kaz49-dynabook kernel:  <TASK>
Jan 15 11:40:54 kaz49-dynabook kernel:  __schedule+0x3b0/0x12b0
Jan 15 11:40:54 kaz49-dynabook kernel:  ? kmem_cache_alloc_noprof+0x111/0x2f0
Jan 15 11:40:54 kaz49-dynabook kernel:  schedule+0x27/0xf0
Jan 15 11:40:54 kaz49-dynabook kernel:  request_wait_answer+0xd0/0x2b0
Jan 15 11:40:54 kaz49-dynabook kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Jan 15 11:40:54 kaz49-dynabook kernel:  __fuse_simple_request+0xd7/0x290
Jan 15 11:40:54 kaz49-dynabook kernel:  fuse_send_open+0xb9/0x110
Jan 15 11:40:54 kaz49-dynabook kernel:  fuse_file_open+0x117/0x1a0
Jan 15 11:40:54 kaz49-dynabook kernel:  fuse_open+0x8a/0x320
Jan 15 11:40:54 kaz49-dynabook kernel:  ? __pfx_fuse_open+0x10/0x10
Jan 15 11:40:54 kaz49-dynabook kernel:  do_dentry_open+0x14c/0x4a0
Jan 15 11:40:54 kaz49-dynabook kernel:  vfs_open+0x2e/0xe0

https://wiki.archlinux.org/title/Power_ … _waking_up
But plasmashell hangs in the fuse driver, do you mount some ntfs drive?

The journal for the affected boot is gonna suffice (and not be 22MB)
Eg for the previous (-1) boot:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

kaz49 · 2025-01-18 10:14:45

The Arch Wiki page says:

When such an issue occurs, trying to login (start another session) would fail with
pam_systemd(process:session): Failed to create session: Job 9876 for unit 'session-6.scope' failed with 'frozen'

but I don't have that anywhere in my log. That might be simply because the system freezes before I can ever attempt a login though... do you think I should attempt the fix on that page and see how it goes?

I do have a NTFS partition on my main drive, but I don't have it mounted by default. I have Dolphin mount it for me whenever I need to access it, and it's usually not mounted when the freeze happens.

(base) [~]$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1     259:0    0 476.9G  0 disk 
├─nvme0n1p1 259:1    0   260M  0 part 
├─nvme0n1p2 259:2    0    16M  0 part 
├─nvme0n1p3 259:3    0   150G  0 part 
├─nvme0n1p4 259:4    0   990M  0 part 
├─nvme0n1p5 259:5    0  10.6G  0 part 
├─nvme0n1p6 259:6    0    66G  0 part /
├─nvme0n1p7 259:7    0 225.1G  0 part /home
└─nvme0n1p8 259:8    0    24G  0 part [SWAP]
(base) [~]$ sudo fdisk -l
Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: C-E80T512G2-P003D2E19T                  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B9881232-F088-4FE4-B372-9DC153791C4B

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1      2048     534527    532480   260M EFI System
/dev/nvme0n1p2    534528     567295     32768    16M Microsoft reserved
/dev/nvme0n1p3    567296  315140095 314572800   150G Microsoft basic data
/dev/nvme0n1p4 976041984  978069503   2027520   990M Windows recovery environment
/dev/nvme0n1p5 978069504 1000214527  22145024  10.6G Windows recovery environment
/dev/nvme0n1p6 315140096  453552127 138412032    66G Linux filesystem
/dev/nvme0n1p7 503883776  976041983 472158208 225.1G Linux filesystem
/dev/nvme0n1p8 453552128  503883775  50331648    24G Linux swap

Partition table entries are not in disk order.

The link I gave you before is the full journal for the boot that the freeze occurred in. It's 22MB long because the system sleeps normally most of the time, so I'd been using my laptop on that boot for a couple days.
Here's the URL I got from the command in your post (it's the same thing, but this 0x0 website is neat! ) 0x0.st/8Hix.txt

Last edited by kaz49 (2025-01-18 10:22:24)

seth · 2025-01-18 15:05:44

[Me] think [you] should attempt the fix on that page and see how it goes

Then what's the fuse call for?
Sidabar: 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Another popular way to stumble S2idle/S3 is APST, https://wiki.archlinux.org/title/Solid_ … leshooting (loosely fits the fuse involvement)

Arch Linux

#1 2025-01-15 03:44:55

System sometimes irreversibly freezes when I try to suspend

#2 2025-01-15 14:45:16

Re: System sometimes irreversibly freezes when I try to suspend

#3 2025-01-17 02:20:51

Re: System sometimes irreversibly freezes when I try to suspend

#4 2025-01-17 10:32:50

Re: System sometimes irreversibly freezes when I try to suspend

#5 2025-01-18 10:14:45

Re: System sometimes irreversibly freezes when I try to suspend

#6 2025-01-18 15:05:44

Re: System sometimes irreversibly freezes when I try to suspend

Board footer