Bug 2219711 - alsactl wireplumber Freezing user space processes failed
Summary: alsactl wireplumber Freezing user space processes failed
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: wireplumber
Version: 38
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-04 22:46 UTC by Marcel Ziswiler
Modified: 2024-05-28 13:19 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-28 13:19:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
journalctl -b -1 --no-hostname (7.25 MB, text/plain)
2023-07-04 22:49 UTC, Marcel Ziswiler
no flags Details

Description Marcel Ziswiler 2023-07-04 22:46:08 UTC
Jul 04 19:33:54 fedora systemd[1]: Reached target sleep.target - Sleep.
Jul 04 19:33:54 fedora systemd[1]: Starting systemd-suspend.service - System Suspend...
Jul 04 19:33:54 fedora systemd-sleep[43552]: Entering sleep state 'suspend'...
Jul 04 19:33:54 fedora kernel: PM: suspend entry (s2idle)
Jul 04 19:33:55 fedora kernel: Filesystems sync: 0.091 seconds
Jul 04 19:34:15 fedora kernel: Freezing user space processes
Jul 04 19:34:15 fedora kernel: Freezing user space processes failed after 20.005 seconds (2 tasks refusing to freeze, wq_busy=0):
Jul 04 19:34:15 fedora kernel: task:alsactl         state:D stack:0     pid:1224  ppid:1      flags:0x00000006
Jul 04 19:34:15 fedora kernel: Call Trace:
Jul 04 19:34:15 fedora kernel:  <TASK>
Jul 04 19:34:15 fedora kernel:  __schedule+0x449/0x14a0
Jul 04 19:34:15 fedora kernel:  schedule+0x5e/0xd0
Jul 04 19:34:15 fedora kernel:  snd_power_ref_and_wait+0xde/0x130 [snd]
Jul 04 19:34:15 fedora kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Jul 04 19:34:15 fedora kernel:  snd_ctl_elem_info+0x48/0x190 [snd]
Jul 04 19:34:15 fedora kernel:  snd_ctl_elem_info_user+0x54/0xb0 [snd]
Jul 04 19:34:15 fedora kernel:  snd_ctl_ioctl+0x2bf/0x800 [snd]
Jul 04 19:34:15 fedora kernel:  __x64_sys_ioctl+0x94/0xd0
Jul 04 19:34:15 fedora kernel:  do_syscall_64+0x60/0x90
Jul 04 19:34:15 fedora kernel:  ? __x64_sys_ioctl+0x94/0xd0
Jul 04 19:34:15 fedora kernel:  ? syscall_exit_to_user_mode+0x1b/0x40
Jul 04 19:34:15 fedora kernel:  ? do_syscall_64+0x6c/0x90
Jul 04 19:34:15 fedora kernel:  ? do_syscall_64+0x6c/0x90
Jul 04 19:34:15 fedora kernel:  ? syscall_exit_to_user_mode+0x1b/0x40
Jul 04 19:34:15 fedora kernel:  ? do_syscall_64+0x6c/0x90
Jul 04 19:34:15 fedora kernel:  ? do_syscall_64+0x6c/0x90
Jul 04 19:34:15 fedora kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Jul 04 19:34:15 fedora kernel: RIP: 0033:0x7fbe0bbd9edd
Jul 04 19:34:15 fedora kernel: RSP: 002b:00007ffc99b28240 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jul 04 19:34:15 fedora kernel: RAX: ffffffffffffffda RBX: 00007ffc99b28ba0 RCX: 00007fbe0bbd9edd
Jul 04 19:34:15 fedora kernel: RDX: 00007ffc99b282b0 RSI: 00000000c1105511 RDI: 0000000000000009
Jul 04 19:34:15 fedora kernel: RBP: 00007ffc99b28290 R08: 0000000000000210 R09: 0000000000000001
Jul 04 19:34:15 fedora kernel: R10: 0000000000000002 R11: 0000000000000246 R12: 000055ed74cc44d0
Jul 04 19:34:15 fedora kernel: R13: 00007ffc99b282b0 R14: 000055ed74cc9020 R15: 0000000000000110
Jul 04 19:34:15 fedora kernel:  </TASK>
Jul 04 19:34:15 fedora kernel: task:wireplumber     state:D stack:0     pid:2255  ppid:2078   flags:0x00000006
Jul 04 19:34:15 fedora kernel: Call Trace:
Jul 04 19:34:15 fedora kernel:  <TASK>
Jul 04 19:34:15 fedora kernel:  __schedule+0x449/0x14a0
Jul 04 19:34:15 fedora kernel:  ? inotify_handle_inode_event+0x150/0x230
Jul 04 19:34:15 fedora kernel:  schedule+0x5e/0xd0
Jul 04 19:34:15 fedora kernel:  schedule_preempt_disabled+0x15/0x30
Jul 04 19:34:15 fedora kernel:  rwsem_down_write_slowpath+0x1f3/0x640
Jul 04 19:34:15 fedora kernel:  down_write+0x5b/0x60
Jul 04 19:34:15 fedora kernel:  snd_ctl_release+0x8a/0x130 [snd]
Jul 04 19:34:15 fedora kernel:  __fput+0x91/0x250
Jul 04 19:34:15 fedora kernel:  task_work_run+0x5d/0x90
Jul 04 19:34:15 fedora kernel:  exit_to_user_mode_prepare+0x1e6/0x1f0
Jul 04 19:34:15 fedora kernel:  syscall_exit_to_user_mode+0x1b/0x40
Jul 04 19:34:15 fedora kernel:  do_syscall_64+0x6c/0x90
Jul 04 19:34:15 fedora kernel:  ? __irq_exit_rcu+0x4b/0xf0
Jul 04 19:34:15 fedora kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Jul 04 19:34:15 fedora kernel: RIP: 0033:0x7f586f4d786c
Jul 04 19:34:15 fedora kernel: RSP: 002b:00007ffd6caa37f0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
Jul 04 19:34:15 fedora kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f586f4d786c
Jul 04 19:34:15 fedora kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000000002b
Jul 04 19:34:15 fedora kernel: RBP: 00007ffd6caa3800 R08: 000055eea04af750 R09: 0000000000000000
Jul 04 19:34:15 fedora kernel: R10: 00000000000003b1 R11: 0000000000000293 R12: 000055eea061d9a0
Jul 04 19:34:15 fedora kernel: R13: 000055eea061d4c0 R14: 000055eea061d450 R15: 000055eea03ceaa0
Jul 04 19:34:15 fedora kernel:  </TASK>

Reproducible: Sometimes

Steps to Reproduce:
1.Boot
2.Suspend
3.Resume
4.Suspend again
Actual Results:  
alsactl wireplumber Freezing user space processes failed

Expected Results:  
Suspend just worksTM

Might have to do with suspending/resuming multiple times sometimes docked sometimes undocked. Regular Lenovo docking station with sideways sliding double USB-C/Ethernet connector. BTW: Lenovo ThinkPad T14 Gen 1 AMD, model 20UES1Y600.

Comment 1 Marcel Ziswiler 2023-07-04 22:49:33 UTC
Created attachment 1974051 [details]
journalctl -b -1 --no-hostname

Comment 2 Aoife Moloney 2024-05-28 13:19:35 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.