Bug #2061091 “Freezing user space processes failed after 20.008 ...” : Bugs : linux-signed-hwe-6.5 package : Ubuntu

Revision history for this message

Richard van der Hoff (richvdh) wrote on 2024-04-12:

#1

Dependencies.txt Edit (3.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (115 bytes, text/plain; charset="utf-8")

Revision history for this message

Richard van der Hoff (richvdh) wrote on 2024-04-12:

#2

I found a very similar report at https://discussion.fedoraproject.org/t/freezing-user-space-processes-failed-after-20-000-seconds-2-tasks-refusing-to-freeze-wq-busy-0/92672, but no resolution there.

Brett Grandbois (brettgrand) on 2024-04-15

Changed in linux-signed-hwe-6.5 (Ubuntu):
assignee:	nobody → Anthony Wong (anthonywong)

Anthony Wong (anthonywong) on 2024-04-15

Changed in linux-signed-hwe-6.5 (Ubuntu):
assignee:	Anthony Wong (anthonywong) → GuoqingJiang (guoqingjiang)

Revision history for this message

GuoqingJiang (guoqingjiang) wrote on 2024-04-16:

#3

Could you share which audio driver is used in the affected system by "cat /proc/asound/modules"? And pls attach the full kern.log to check if something is suspicious here.

Revision history for this message

Richard van der Hoff (richvdh) wrote on 2024-04-16:

#4

rav@xps9320:~$ cat /proc/asound/modules
0 snd_soc_sof_sdw
1 snd_usb_audio

Revision history for this message

Richard van der Hoff (richvdh) wrote on 2024-04-16:

#5

kern.log Edit (248.2 KiB, application/octet-stream)

Here's the kern.log since the last-but-one reboot.

Revision history for this message

GuoqingJiang (guoqingjiang) wrote on 2024-04-17:

#6

Download full text (3.7 KiB)

There is another calltrace in kern.log which might be another issue (probably need a separated bug report).

Apr 15 21:45:23 xps9320 kernel: [43079.109011] ================================================================================
Apr 15 21:45:23 xps9320 kernel: [43079.112281] UBSAN: shift-out-of-bounds in /build/linux-hwe-6.5-jkqeMi/linux-hwe-6.5-6.5.0/drivers/gpu/drm/display/drm_dp_mst_topology.c:4416:36
Apr 15 21:45:23 xps9320 kernel: [43079.115601] shift exponent -1 is negative
Apr 15 21:45:23 xps9320 kernel: [43079.119073] CPU: 0 PID: 34404 Comm: kworker/0:3 Tainted: G OE 6.5.0-27-generic #28~22.04.1-Ubuntu
Apr 15 21:45:23 xps9320 kernel: [43079.122523] Hardware name: Dell Inc. XPS 9320/0CW9KM, BIOS 2.8.0 11/13/2023
Apr 15 21:45:23 xps9320 kernel: [43079.126024] Workqueue: events output_poll_execute [drm_kms_helper]
Apr 15 21:45:23 xps9320 kernel: [43079.129530] Call Trace:
Apr 15 21:45:23 xps9320 kernel: [43079.132985] <TASK>
Apr 15 21:45:23 xps9320 kernel: [43079.136412] dump_stack_lvl+0x48/0x70
Apr 15 21:45:23 xps9320 kernel: [43079.139805] dump_stack+0x10/0x20
Apr 15 21:45:23 xps9320 kernel: [43079.143170] __ubsan_handle_shift_out_of_bounds+0x1ac/0x360
Apr 15 21:45:23 xps9320 kernel: [43079.146525] drm_dp_atomic_release_time_slots.cold+0x17/0x3d [drm_display_helper]
Apr 15 21:45:23 xps9320 kernel: [43079.149904] intel_dp_mst_atomic_check+0xaa/0x180 [i915]
Apr 15 21:45:23 xps9320 kernel: [43079.153378] ? update_connector_routing+0x2fc/0x3f0 [drm_kms_helper]
Apr 15 21:45:23 xps9320 kernel: [43079.156738] drm_atomic_helper_check_modeset+0x300/0x610 [drm_kms_helper]
Apr 15 21:45:23 xps9320 kernel: [43079.160084] intel_atomic_check+0xfe/0xb80 [i915]
Apr 15 21:45:23 xps9320 kernel: [43079.163518] ? drm_plane_check_pixel_format+0x53/0xe0 [drm]
Apr 15 21:45:23 xps9320 kernel: [43079.166858] drm_atomic_check_only+0x1ac/0x400 [drm]
Apr 15 21:45:23 xps9320 kernel: [43079.170172] ? update_output_state+0x184/0x1a0 [drm]
Apr 15 21:45:23 xps9320 kernel: [43079.173478] drm_atomic_commit+0x58/0xd0 [drm]
Apr 15 21:45:23 xps9320 kernel: [43079.176765] ? __pfx___drm_printfn_info+0x10/0x10 [drm]
Apr 15 21:45:23 xps9320 kernel: [43079.180049] drm_client_modeset_commit_atomic+0x203/0x240 [drm]
Apr 15 21:45:23 xps9320 kernel: [43079.183332] drm_client_modeset_commit_locked+0x5b/0x170 [drm]
Apr 15 21:45:23 xps9320 kernel: [43079.186586] ? mutex_lock+0x12/0x50
Apr 15 21:45:23 xps9320 kernel: [43079.189776] drm_client_modeset_commit+0x26/0x50 [drm]
Apr 15 21:45:23 xps9320 kernel: [43079.192980] __drm_fb_helper_restore_fbdev_mode_unlocked+0xc2/0x100 [drm_kms_helper]
Apr 15 21:45:23 xps9320 kernel: [43079.196179] drm_fb_helper_hotplug_event+0x10b/0x120 [drm_kms_helper]
Apr 15 21:45:23 xps9320 kernel: [43079.199336] intel_fbdev_output_poll_changed+0x6b/0xb0 [i915]
Apr 15 21:45:23 xps9320 kernel: [43079.202568] output_poll_execute+0x237/0x280 [drm_kms_helper]
Apr 15 21:45:23 xps9320 kernel: [43079.205686] ? __schedule+0x2d3/0x750
Apr 15 21:45:23 xps9320 kernel: [43079.208777] process_one_work+0x23d/0x450
Apr 15 21:45:23 xps9320 kernel: [43079.211856] worker_thread+0x50/0x3f0
Apr 15 21:45:23 xps9320 kernel: [43079.21492...

Looks suspend/resume can be completed sometimes.

Apr 15 12:49:26 xps9320 kernel: [10214.971688] Freezing user space processes completed (elapsed 0.002 seconds)
Apr 15 21:45:23 xps9320 kernel: [30355.137512] Freezing user space processes completed (elapsed 0.015 seconds)
Apr 15 23:02:59 xps9320 kernel: [47737.172847] Freezing user space processes failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:03:19 xps9320 kernel: [47757.538206] Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:03:49 xps9320 kernel: [47787.948230] Freezing user space processes failed after 20.010 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:04:10 xps9320 kernel: [47808.293913] Freezing user space processes failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:04:40 xps9320 kernel: [47838.963650] Freezing user space processes failed after 20.011 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:05:01 xps9320 kernel: [47859.321047] Freezing user space processes failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:05:31 xps9320 kernel: [47889.930764] Freezing user space processes failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:05:52 xps9320 kernel: [47910.270362] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:06:22 xps9320 kernel: [47940.942995] Freezing user space processes failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:06:43 xps9320 kernel: [47961.284299] Freezing user space processes failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:07:13 xps9320 kernel: [47991.938673] Freezing user space processes failed after 20.003 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:07:34 xps9320 kernel: [48012.283148] Freezing user space processes failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:07:54 xps9320 kernel: [48032.682674] Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:08:15 xps9320 kernel: [48053.066382] Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:08:37 xps9320 kernel: [48075.379470] Freezing user space processes failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:08:57 xps9320 kernel: [48095.707188] Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:09:18 xps9320 kernel: [48116.090956] Freezing user space processes failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:09:38 xps9320 kernel: [48136.438119] Freezing user space processes failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:09:59 xps9320 kernel: [48157.256494] Freezing user space processes failed after 20.002 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:10:19 xps9320 kernel: [48177.593855] Freezing user space processes failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:10:41 xps9320 kernel: [48199.473829] Freezing user space processes failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:11:01 xps9320 kernel: [48219.806060] Freezing user space processes failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:11:22 xps9320 kernel: [48240.188072] Freezing user space processes failed after 20.011 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:11:42 xps9320 kernel: [48260.947835] Freezing user space processes failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 16 12:52:21 xps9320 kernel: [13407.856663] Freezing user space processes completed (elapsed 0.002 seconds)

Could you rebuild kernel with CONFIG_PROVE_LOCKING option to discover locking related deadlocks? Then upload the log after reproduce the issue by shut down laptop with the new kernel. Also please attach the output of lsusb given it could be usb relevant.

And it also would be helpful to try with latest noble kernel or recent upstream kernel, thanks.

Revision history for this message

Richard van der Hoff (richvdh) wrote on 2024-04-17:

#9

> And this call trace looks is related to current issue, I guess snd_power_ref_and_wait was waiting for snd_card_disconnect which wakes up power_sleep at the end of the code, but snd_card_disconnect -> snd_device_disconnect_all -> snd_pcm_dev_disconnect was blocked for some reason.

Yes, interesting. Good spot.

> Looks suspend/resume can be completed sometimes.

Yes. I think what causes the problem is when I disconnect from my USB dock. After that, I can't suspend until I reboot. Once I reboot, it can suspend again until I once more disconnect the dock.

> Could you rebuild kernel with CONFIG_PROVE_LOCKING option to discover locking related deadlocks? Then upload the log after reproduce the issue by shut down laptop with the new kernel. Also please attach the output of lsusb given it could be usb relevant.
>
> And it also would be helpful to try with latest noble kernel or recent upstream kernel, thanks.

Sure. I'll try an upstream kernel with CONFIG_PROVE_LOCKING.

Revision history for this message

Richard van der Hoff (richvdh) wrote on 2024-04-25:

#10

Oddly, I don't seem to be able to reproduce this problem on an upstream 6.8 kernel. I'll try with a rebuild of 6.5.0-27-generic instead.

Revision history for this message

Richard van der Hoff (richvdh) wrote on 2024-04-29:

#11

Download full text (10.3 KiB)

Ok, I reproduced this on a rebuild of 6.5.0-34 with CONFIG_PROVE_LOCKING. Here are some relevant-looking bits of the logs. It looks like the wireplumber process and the usb_disconnect process have deadlocked?

[Thinking about this further, possibly the action that triggers it is to disconnect the dock while the system is suspended, then resume the system.]

Apr 29 21:24:36 xps9320 kernel: [280990.641315] INFO: task wireplumber:3263 blocked for more than 241 seconds.
Apr 29 21:24:36 xps9320 kernel: [280990.641334] Tainted: G OE 6.5.13+ #18
Apr 29 21:24:36 xps9320 kernel: [280990.641341] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 29 21:24:36 xps9320 kernel: [280990.641346] task:wireplumber state:D stack:0 pid:3263 ppid:3253 flags:0x00000002
Apr 29 21:24:36 xps9320 kernel: [280990.641360] Call Trace:
Apr 29 21:24:36 xps9320 kernel: [280990.641367] <TASK>
Apr 29 21:24:36 xps9320 kernel: [280990.641382] __schedule+0x4cc/0x1ad0
Apr 29 21:24:36 xps9320 kernel: [280990.641401] ? trace_hardirqs_on+0x65/0xc0
Apr 29 21:24:36 xps9320 kernel: [280990.641414] ? _raw_spin_unlock_irqrestore+0x31/0x70
Apr 29 21:24:36 xps9320 kernel: [280990.641424] ? __wake_up_common_lock+0x8d/0xd0
Apr 29 21:24:36 xps9320 kernel: [280990.641442] schedule+0x68/0x110
Apr 29 21:24:36 xps9320 kernel: [280990.641456] snd_power_ref_and_wait+0xbd/0x120 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.641486] ? __pfx_autoremove_wake_function+0x10/0x10
Apr 29 21:24:36 xps9320 kernel: [280990.641501] snd_ctl_elem_info+0x4f/0x1b0 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.641532] snd_ctl_elem_info_user+0x4e/0xb0 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.641581] snd_ctl_ioctl+0x1ec/0x850 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.641608] ? __fget_files+0xde/0x1d0
Apr 29 21:24:36 xps9320 kernel: [280990.641625] __x64_sys_ioctl+0x9d/0xe0
Apr 29 21:24:36 xps9320 kernel: [280990.641637] x64_sys_call+0x1fe9/0x2570
Apr 29 21:24:36 xps9320 kernel: [280990.641646] do_syscall_64+0x56/0x90
Apr 29 21:24:36 xps9320 kernel: [280990.641657] ? do_syscall_64+0x63/0x90
Apr 29 21:24:36 xps9320 kernel: [280990.641665] ? do_syscall_64+0x63/0x90
Apr 29 21:24:36 xps9320 kernel: [280990.641675] entry_SYSCALL_64_after_hwframe+0x73/0xdd
Apr 29 21:24:36 xps9320 kernel: [280990.641683] RIP: 0033:0x70991f71a94f
Apr 29 21:24:36 xps9320 kernel: [280990.641692] RSP: 002b:00007ffc84003090 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Apr 29 21:24:36 xps9320 kernel: [280990.641701] RAX: ffffffffffffffda RBX: 00007ffc84003100 RCX: 000070991f71a94f
Apr 29 21:24:36 xps9320 kernel: [280990.641707] RDX: 00007ffc84003100 RSI: 00000000c1105511 RDI: 0000000000000022
Apr 29 21:24:36 xps9320 kernel: [280990.641713] RBP: 00007ffc840032e0 R08: 00006231bc666330 R09: 0000000000000004
Apr 29 21:24:36 xps9320 kernel: [280990.641718] R10: fffffffffffff314 R11: 0000000000000246 R12: 00006231bc90dc50
Apr 29 21:24:36 xps9320 kernel: [280990.641723] R13: 00006231bc7c9140 R14: 00007ffc84003280 R15: 00007ffc84003220
Apr 29 21:24:36 xps9320 kernel: [280990.641745] </TASK>
Apr 29 21:24:36 xps9320 kernel: [280990.642222] INFO: task kworker/2:3:67822 blocke...

Ok, I reproduced this on a rebuild of 6.5.0-34 with CONFIG_PROVE_LOCKING. Here are some relevant-looking bits of the logs. It looks like the wireplumber process and the usb_disconnect process have deadlocked?

[Thinking about this further, possibly the action that triggers it is to disconnect the dock while the system is suspended, then resume the system.]

Apr 29 21:24:36 xps9320 kernel: [280990.641315] INFO: task wireplumber:3263 blocked for more than 241 seconds.
Apr 29 21:24:36 xps9320 kernel: [280990.641334]       Tainted: G           OE      6.5.13+ #18
Apr 29 21:24:36 xps9320 kernel: [280990.641341] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 29 21:24:36 xps9320 kernel: [280990.641346] task:wireplumber     state:D stack:0     pid:3263  ppid:3253   flags:0x00000002
Apr 29 21:24:36 xps9320 kernel: [280990.641360] Call Trace:
Apr 29 21:24:36 xps9320 kernel: [280990.641367]  <TASK>
Apr 29 21:24:36 xps9320 kernel: [280990.641382]  __schedule+0x4cc/0x1ad0
Apr 29 21:24:36 xps9320 kernel: [280990.641401]  ? trace_hardirqs_on+0x65/0xc0
Apr 29 21:24:36 xps9320 kernel: [280990.641414]  ? _raw_spin_unlock_irqrestore+0x31/0x70
Apr 29 21:24:36 xps9320 kernel: [280990.641424]  ? __wake_up_common_lock+0x8d/0xd0
Apr 29 21:24:36 xps9320 kernel: [280990.641442]  schedule+0x68/0x110
Apr 29 21:24:36 xps9320 kernel: [280990.641456]  snd_power_ref_and_wait+0xbd/0x120 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.641486]  ? __pfx_autoremove_wake_function+0x10/0x10
Apr 29 21:24:36 xps9320 kernel: [280990.641501]  snd_ctl_elem_info+0x4f/0x1b0 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.641532]  snd_ctl_elem_info_user+0x4e/0xb0 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.641581]  snd_ctl_ioctl+0x1ec/0x850 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.641608]  ? __fget_files+0xde/0x1d0
Apr 29 21:24:36 xps9320 kernel: [280990.641625]  __x64_sys_ioctl+0x9d/0xe0
Apr 29 21:24:36 xps9320 kernel: [280990.641637]  x64_sys_call+0x1fe9/0x2570
Apr 29 21:24:36 xps9320 kernel: [280990.641646]  do_syscall_64+0x56/0x90
Apr 29 21:24:36 xps9320 kernel: [280990.641657]  ? do_syscall_64+0x63/0x90
Apr 29 21:24:36 xps9320 kernel: [280990.641665]  ? do_syscall_64+0x63/0x90
Apr 29 21:24:36 xps9320 kernel: [280990.641675]  entry_SYSCALL_64_after_hwframe+0x73/0xdd
Apr 29 21:24:36 xps9320 kernel: [280990.641683] RIP: 0033:0x70991f71a94f
Apr 29 21:24:36 xps9320 kernel: [280990.641692] RSP: 002b:00007ffc84003090 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Apr 29 21:24:36 xps9320 kernel: [280990.641701] RAX: ffffffffffffffda RBX: 00007ffc84003100 RCX: 000070991f71a94f
Apr 29 21:24:36 xps9320 kernel: [280990.641707] RDX: 00007ffc84003100 RSI: 00000000c1105511 RDI: 0000000000000022
Apr 29 21:24:36 xps9320 kernel: [280990.641713] RBP: 00007ffc840032e0 R08: 00006231bc666330 R09: 0000000000000004
Apr 29 21:24:36 xps9320 kernel: [280990.641718] R10: fffffffffffff314 R11: 0000000000000246 R12: 00006231bc90dc50
Apr 29 21:24:36 xps9320 kernel: [280990.641723] R13: 00006231bc7c9140 R14: 00007ffc84003280 R15: 00007ffc84003220
Apr 29 21:24:36 xps9320 kernel: [280990.641745]  </TASK>
Apr 29 21:24:36 xps9320 kernel: [280990.642222] INFO: task kworker/2:3:67822 blocked for more than 241 seconds.
Apr 29 21:24:36 xps9320 kernel: [280990.642229]       Tainted: G           OE      6.5.13+ #18
Apr 29 21:24:36 xps9320 kernel: [280990.642234] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 29 21:24:36 xps9320 kernel: [280990.642239] task:kworker/2:3     state:D stack:0     pid:67822 ppid:2      flags:0x00004000
Apr 29 21:24:36 xps9320 kernel: [280990.642250] Workqueue: usb_hub_wq hub_event
Apr 29 21:24:36 xps9320 kernel: [280990.642262] Call Trace:
Apr 29 21:24:36 xps9320 kernel: [280990.642266]  <TASK>
Apr 29 21:24:36 xps9320 kernel: [280990.642274]  __schedule+0x4cc/0x1ad0
Apr 29 21:24:36 xps9320 kernel: [280990.642285]  ? mark_held_locks+0x4d/0x90
Apr 29 21:24:36 xps9320 kernel: [280990.642303]  schedule+0x68/0x110
Apr 29 21:24:36 xps9320 kernel: [280990.642312]  schedule_preempt_disabled+0x15/0x30
Apr 29 21:24:36 xps9320 kernel: [280990.642321]  rwsem_down_write_slowpath+0x2bc/0x820
Apr 29 21:24:36 xps9320 kernel: [280990.642342]  down_write+0xde/0xe0
Apr 29 21:24:36 xps9320 kernel: [280990.642353]  snd_pcm_dev_disconnect+0x1cb/0x280 [snd_pcm]
Apr 29 21:24:36 xps9320 kernel: [280990.642386]  snd_device_disconnect_all+0x47/0xa0 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.642411]  snd_card_disconnect.part.0+0x10d/0x270 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.642439]  snd_card_disconnect+0x13/0x30 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.642462]  usb_audio_disconnect+0x116/0x290 [snd_usb_audio]
Apr 29 21:24:36 xps9320 kernel: [280990.642504]  usb_unbind_interface+0x90/0x280
Apr 29 21:24:36 xps9320 kernel: [280990.642518]  device_remove+0x69/0x80
Apr 29 21:24:36 xps9320 kernel: [280990.642528]  device_release_driver_internal+0x20d/0x280
Apr 29 21:24:36 xps9320 kernel: [280990.642539]  device_release_driver+0x12/0x20
Apr 29 21:24:36 xps9320 kernel: [280990.642545]  bus_remove_device+0xdc/0x150
Apr 29 21:24:36 xps9320 kernel: [280990.642556]  device_del+0x160/0x3d0
Apr 29 21:24:36 xps9320 kernel: [280990.642572]  usb_disable_device+0xe1/0x280
Apr 29 21:24:36 xps9320 kernel: [280990.642586]  usb_disconnect+0xe6/0x2f0
Apr 29 21:24:36 xps9320 kernel: [280990.642600]  usb_disconnect+0xcb/0x2f0
Apr 29 21:24:36 xps9320 kernel: [280990.642614]  usb_disconnect+0xcb/0x2f0
Apr 29 21:24:36 xps9320 kernel: [280990.642628]  hub_event+0xe2d/0x1ce0
Apr 29 21:24:36 xps9320 kernel: [280990.642654]  process_one_work+0x2bf/0x5a0
Apr 29 21:24:36 xps9320 kernel: [280990.642663]  ? process_one_work+0x260/0x5a0
Apr 29 21:24:36 xps9320 kernel: [280990.642678]  worker_thread+0x52/0x3f0
Apr 29 21:24:36 xps9320 kernel: [280990.642689]  ? __pfx_worker_thread+0x10/0x10
Apr 29 21:24:36 xps9320 kernel: [280990.642697]  kthread+0xf7/0x130
Apr 29 21:24:36 xps9320 kernel: [280990.642704]  ? __pfx_kthread+0x10/0x10
Apr 29 21:24:36 xps9320 kernel: [280990.642713]  ret_from_fork+0x43/0x70
Apr 29 21:24:36 xps9320 kernel: [280990.642721]  ? __pfx_kthread+0x10/0x10
Apr 29 21:24:36 xps9320 kernel: [280990.642729]  ret_from_fork_asm+0x1b/0x30
Apr 29 21:24:36 xps9320 kernel: [280990.642748]  </TASK>
Apr 29 21:24:36 xps9320 kernel: [280990.642773] 
Apr 29 21:24:36 xps9320 kernel: [280990.642773] Showing all locks held in the system:
Apr 29 21:24:36 xps9320 kernel: [280990.642783] 1 lock held by rcu_tasks_kthre/12:
Apr 29 21:24:36 xps9320 kernel: [280990.642789]  #0: ffffffff9ffa4770 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0x490
Apr 29 21:24:36 xps9320 kernel: [280990.642811] 1 lock held by rcu_tasks_rude_/13:
Apr 29 21:24:36 xps9320 kernel: [280990.642816]  #0: ffffffff9ffa44f0 (rcu_tasks_rude.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0x490
Apr 29 21:24:36 xps9320 kernel: [280990.642834] 1 lock held by rcu_tasks_trace/14:
Apr 29 21:24:36 xps9320 kernel: [280990.642839]  #0: ffffffff9ffa4230 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0x490
Apr 29 21:24:36 xps9320 kernel: [280990.642865] 1 lock held by khungtaskd/114:
Apr 29 21:24:36 xps9320 kernel: [280990.642870]  #0: ffffffff9ffa5260 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x37/0x220
Apr 29 21:24:36 xps9320 kernel: [280990.642902] 1 lock held by in:imklog/1824:
Apr 29 21:24:36 xps9320 kernel: [280990.642907]  #0: ffff91128a130cc8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x4f/0x80
Apr 29 21:24:36 xps9320 kernel: [280990.642966] 1 lock held by wireplumber/3263:
Apr 29 21:24:36 xps9320 kernel: [280990.642971]  #0: ffff911281646698 (&card->controls_rwsem){++++}-{3:3}, at: snd_ctl_elem_info+0x30/0x1b0 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.643185] 4 locks held by pipe-connection/11701:
Apr 29 21:24:36 xps9320 kernel: [280990.643191]  #0: ffff9116767eb4c8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x4f/0x80
Apr 29 21:24:36 xps9320 kernel: [280990.643206]  #1: ffff911282d1c0a0 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0x6a/0x500
Apr 29 21:24:36 xps9320 kernel: [280990.643220]  #2: ffff9112b8e82a88 (&of->mutex){+.+.}-{3:3}, at: kernfs_seq_start+0x2f/0x120
Apr 29 21:24:36 xps9320 kernel: [280990.643237]  #3: ffff9112d06ed190 (&dev->mutex){....}-{3:3}, at: bConfigurationValue_show+0x27/0x80
Apr 29 21:24:36 xps9320 kernel: [280990.643405] 11 locks held by kworker/2:3/67822:
Apr 29 21:24:36 xps9320 kernel: [280990.643410]  #0: ffff9112833fb538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x260/0x5a0
Apr 29 21:24:36 xps9320 kernel: [280990.643426]  #1: ffffb1b164ad3e40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x260/0x5a0
Apr 29 21:24:36 xps9320 kernel: [280990.643441]  #2: ffff9112d0a5a990 (&dev->mutex){....}-{3:3}, at: hub_event+0x7b/0x1ce0
Apr 29 21:24:36 xps9320 kernel: [280990.643454]  #3: ffff9112d0ab0990 (&dev->mutex){....}-{3:3}, at: usb_disconnect+0x7e/0x2f0
Apr 29 21:24:36 xps9320 kernel: [280990.643470]  #4: ffff911283742990 (&dev->mutex){....}-{3:3}, at: usb_disconnect+0x7e/0x2f0
Apr 29 21:24:36 xps9320 kernel: [280990.643485]  #5: ffff9112d06ed190 (&dev->mutex){....}-{3:3}, at: usb_disconnect+0x7e/0x2f0
Apr 29 21:24:36 xps9320 kernel: [280990.643501]  #6: ffff9112d06ec160 (&dev->mutex){....}-{3:3}, at: device_release_driver_internal+0x55/0x280
Apr 29 21:24:36 xps9320 kernel: [280990.643515]  #7: ffffffffc18026a8 (register_mutex#3){+.+.}-{3:3}, at: usb_audio_disconnect+0x47/0x290 [snd_usb_audio]
Apr 29 21:24:36 xps9320 kernel: [280990.643553]  #8: ffffffffc1709f28 (register_mutex#4){+.+.}-{3:3}, at: snd_pcm_dev_disconnect+0x37/0x280 [snd_pcm]
Apr 29 21:24:36 xps9320 kernel: [280990.643587]  #9: ffff91128b14ca60 (&pcm->open_mutex){+.+.}-{3:3}, at: snd_pcm_dev_disconnect+0x41/0x280 [snd_pcm]
Apr 29 21:24:36 xps9320 kernel: [280990.643617]  #10: ffff911281646698 (&card->controls_rwsem){++++}-{3:3}, at: snd_pcm_dev_disconnect+0x1cb/0x280 [snd_pcm]
Apr 29 21:24:36 xps9320 kernel: [280990.643656] 2 locks held by less/69421:
Apr 29 21:24:36 xps9320 kernel: [280990.643661]  #0: ffff9114065c2898 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x25/0x40
Apr 29 21:24:36 xps9320 kernel: [280990.643677]  #1: ffffb1b1494832f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x59f/0x6c0
Apr 29 21:24:36 xps9320 kernel: [280990.643702] 
Apr 29 21:24:36 xps9320 kernel: [280990.643707] =============================================
Apr 29 21:24:36 xps9320 kernel: [280990.643707]

Revision history for this message

GuoqingJiang (guoqingjiang) wrote on 2024-04-30:

#12

Thanks for the update, could you bisect which commit fixes the issue since upstream 6.8 works?

https://git-scm.com/docs/git-bisect

Revision history for this message

Richard van der Hoff (richvdh) wrote on 2024-05-01:

#13

kern.log Edit (584.4 KiB, text/html)

Seems I was mistaken. This happens on 6.8 as well.

Revision history for this message

Richard van der Hoff (richvdh) wrote on 2024-05-07:

#14

I reported this upstream at https://bugzilla.kernel.org/show_bug.cgi?id=218816. Perhaps someone there can help.

Revision history for this message

GuoqingJiang (guoqingjiang) wrote on 2024-05-21:

#15

Thanks for the update, commit 87988a534d8e ("ALSA: Fix deadlocks with kctl removals at disconnection") has been merged into upstream, and it will be included by stable update

Revision history for this message

GuoqingJiang (guoqingjiang) wrote on 2024-06-07:

#16

SRU Justification

BugLink: https://bugs.launchpad.net/bugs/2061091

[Impact]
User reports that laptop gets stuck on the console screen when trying to
shut down or suspend laptop.

[Fix]
Focal: backport form bb9b0e46b84 due to different context.
Jammy and Mantic: cherry-pick from bb9b0e46b84.
Noble: stable v6.8.12 includes the fix by 88ce3fe255d5.

[Test case]
No specific test case from our side since this bug was reported by customer.

[Regression Potential]
It could affect PM relevant actions.

Takashi Iwai (1):
ALSA: Fix deadlocks with kctl removals at disconnection

sound/core/init.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)

Changed in linux-signed-hwe-6.5 (Ubuntu):
milestone:	none → jammy-updates
Changed in linux-signed-hwe-6.5 (Ubuntu Focal):
assignee:	nobody → GuoqingJiang (guoqingjiang)
Changed in linux-signed-hwe-6.5 (Ubuntu Jammy):
assignee:	nobody → GuoqingJiang (guoqingjiang)
Changed in linux-signed-hwe-6.5 (Ubuntu Mantic):
assignee:	nobody → GuoqingJiang (guoqingjiang)
Changed in linux-signed-hwe-6.5 (Ubuntu Focal):
milestone:	none → focal-updates
Changed in linux-signed-hwe-6.5 (Ubuntu Jammy):
milestone:	none → jammy-updates
Changed in linux-signed-hwe-6.5 (Ubuntu Mantic):
milestone:	none → mantic-updates

Roxana Nicolescu (roxanan) on 2024-06-17

Changed in linux-signed-hwe-6.5 (Ubuntu Focal):
status:	New → Fix Committed
Changed in linux-signed-hwe-6.5 (Ubuntu Jammy):
status:	New → Fix Committed
Changed in linux-signed-hwe-6.5 (Ubuntu Mantic):
status:	New → Fix Committed

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-07-10:

#17

This bug is awaiting verification that the linux/5.4.0-192.212 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux' to 'verification-done-focal-linux'. If the problem still exists, change the tag 'verification-needed-focal-linux' to 'verification-failed-focal-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-v2 verification-needed-focal-linux

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-07-15:

#18

This bug is awaiting verification that the linux/5.15.0-118.128 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy-linux' to 'verification-failed-jammy-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux

Revision history for this message

Brian Murray (brian-murray) wrote on 2024-07-25:

#19

Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release.

Changed in linux-signed-hwe-6.5 (Ubuntu Mantic):
status:	Fix Committed → Won't Fix

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-07:

#20

This bug is awaiting verification that the linux-nvidia-tegra/5.15.0-1027.27 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-07:

#21

This bug is awaiting verification that the linux-nvidia-tegra-igx/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 verification-needed-jammy-linux-nvidia-tegra-igx

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#22

This bug is awaiting verification that the linux-azure/5.15.0-1070.79 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy-linux-azure'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#23

This bug is awaiting verification that the linux-ibm/5.15.0-1060.63 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-ibm' to 'verification-done-jammy-linux-ibm'. If the problem still exists, change the tag 'verification-needed-jammy-linux-ibm' to 'verification-failed-jammy-linux-ibm'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-ibm-v2 verification-needed-jammy-linux-ibm

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#24

This bug is awaiting verification that the linux-raspi/5.15.0-1060.63 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-linux-raspi'. If the problem still exists, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#25

This bug is awaiting verification that the linux-oracle/5.15.0-1065.71 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oracle' to 'verification-done-jammy-linux-oracle'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oracle' to 'verification-failed-jammy-linux-oracle'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-oracle-v2 verification-needed-jammy-linux-oracle

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#26

This bug is awaiting verification that the linux-aws-5.15/5.15.0-1067.73~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-5.15

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#27

This bug is awaiting verification that the linux-hwe-5.15/5.15.0-118.128~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-hwe-5.15' to 'verification-done-focal-linux-hwe-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-hwe-5.15' to 'verification-failed-focal-linux-hwe-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-hwe-5.15-v2 verification-needed-focal-linux-hwe-5.15

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#28

This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-gcp-tcpx' to 'verification-done-focal-linux-gcp-tcpx'. If the problem still exists, change the tag 'verification-needed-focal-linux-gcp-tcpx' to 'verification-failed-focal-linux-gcp-tcpx'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-gcp-tcpx-v2 verification-needed-focal-linux-gcp-tcpx

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#29

This bug is awaiting verification that the linux-gkeop-5.15/5.15.0-1050.57~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-gkeop-5.15' to 'verification-done-focal-linux-gkeop-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-gkeop-5.15' to 'verification-failed-focal-linux-gkeop-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-gkeop-5.15-v2 verification-needed-focal-linux-gkeop-5.15

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#30

This bug is awaiting verification that the linux-bluefield/5.4.0-1090.97 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-done-focal-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-failed-focal-linux-bluefield'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-bluefield-v2 verification-needed-focal-linux-bluefield

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#31

This bug is awaiting verification that the linux-azure/5.4.0-1135.142 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-azure' to 'verification-done-focal-linux-azure'. If the problem still exists, change the tag 'verification-needed-focal-linux-azure' to 'verification-failed-focal-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-azure-v2 verification-needed-focal-linux-azure

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#32

This bug is awaiting verification that the linux-raspi-5.4/5.4.0-1114.126~18.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic-linux-raspi-5.4' to 'verification-done-bionic-linux-raspi-5.4'. If the problem still exists, change the tag 'verification-needed-bionic-linux-raspi-5.4' to 'verification-failed-bionic-linux-raspi-5.4'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-bionic-linux-raspi-5.4-v2 verification-needed-bionic-linux-raspi-5.4

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#33

This bug is awaiting verification that the linux-gcp-5.4/5.4.0-1134.143~18.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic-linux-gcp-5.4' to 'verification-done-bionic-linux-gcp-5.4'. If the problem still exists, change the tag 'verification-needed-bionic-linux-gcp-5.4' to 'verification-failed-bionic-linux-gcp-5.4'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-bionic-linux-gcp-5.4-v2 verification-needed-bionic-linux-gcp-5.4

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#34

This bug is awaiting verification that the linux-ibm-5.15/5.15.0-1060.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-ibm-5.15' to 'verification-done-focal-linux-ibm-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-ibm-5.15' to 'verification-failed-focal-linux-ibm-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-ibm-5.15-v2 verification-needed-focal-linux-ibm-5.15

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-08:

#35

This bug is awaiting verification that the linux-azure-5.4/5.4.0-1135.142~18.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic-linux-azure-5.4' to 'verification-done-bionic-linux-azure-5.4'. If the problem still exists, change the tag 'verification-needed-bionic-linux-azure-5.4' to 'verification-failed-bionic-linux-azure-5.4'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-bionic-linux-azure-5.4-v2 verification-needed-bionic-linux-azure-5.4

Revision history for this message

Vinicius Peixoto (vpeixoto) wrote on 2024-08-08:

#36

Adding the "verification-done-focal-linux-aws-5.15" since this bug doesn't affect focal:linux-azure-5.15

tags:	added: verification-done-focal-linux-aws-5.15 removed: kernel-spammed-bionic-linux-azure-5.4-v2 kernel-spammed-focal-linux-ibm-5.15-v2 verification-needed-bionic-linux-azure-5.4 verification-needed-focal-linux-aws-5.15 verification-needed-focal-linux-ibm-5.15
tags:	added: kernel-spammed-bionic-linux-azure-5.4-v2 kernel-spammed-focal-linux-ibm-5.15-v2 verification-needed-bionic-linux-azure-5.4 verification-needed-focal-linux-ibm-5.15

Revision history for this message

Bartlomiej Zolnierkiewicz (bzolnier) wrote on 2024-08-12 (last edit on 2024-08-12):

#37

focal:linux-bluefield kernel has CONFIG_SOUND set to 'n' so this bug doesn't affect it.

tags:

added: verification-done-focal-linux-bluefield
removed: verification-needed-focal-linux-bluefield

Revision history for this message

Noah Wager (nwager) wrote on 2024-08-12:

#38

Doesn't affect tegra kernels

tags:

added: verification-done-jammy-linux-nvidia-tegra verification-done-jammy-linux-nvidia-tegra-igx
removed: verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-08-14:

#39

This bug is awaiting verification that the linux-nvidia-tegra-5.15/5.15.0-1027.27~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-tegra-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2024-09-06:

#40

This bug is awaiting verification that the linux-mtk/5.15.0-1034.39 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-linux-mtk'. If the problem still exists, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk

	Status	Importance	Assigned to	Milestone
linux-signed-hwe-6.5 (Ubuntu)	New	Undecided	GuoqingJiang	Ubuntu jammy-updates
Focal	Fix Committed	Undecided	GuoqingJiang	Ubuntu focal-updates
Jammy	Fix Committed	Undecided	GuoqingJiang	Ubuntu jammy-updates
Mantic	Won't Fix	Undecided	GuoqingJiang	Ubuntu mantic-updates

Ubuntu
linux-signed-hwe-6.5 package

Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntulinux-signed-hwe-6.5 package

Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux-signed-hwe-6.5 package