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

Bug #2061091 reported by Richard van der Hoff
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-signed-hwe-6.5 (Ubuntu)
New
Undecided
GuoqingJiang

Bug Description

Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq.

The following appears in `kern.log`:

```
Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x00000006
Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace:
Apr 12 08:59:54 xps9320 kernel: [173172.521755] <TASK>
Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750
Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110
Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd]
Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10
Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd]
Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd]
Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd]
Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120
Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0
Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90
Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60
Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90
Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90
Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60
Apr 12 08:59:54 xps9320 kernel: [173172.555596] ? do_syscall_64+0x67/0x90
Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0
Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f
Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:00007ffef2072940 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffffffffffffffda RBX: 00007ffef20729b0 RCX: 000070f3adb1a94f
Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 00007ffef20729b0 RSI: 00000000c1105511 RDI: 0000000000000022
Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 00007ffef2072b90 R08: 000065107d2b6070 R09: 0000000000000004
Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: fffffffffffff014 R11: 0000000000000246 R12: 000065107d2ee100
Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 000065107d1fb400 R14: 00007ffef2072b30 R15: 00007ffef2072ad0
Apr 12 08:59:54 xps9320 kernel: [173172.578308] </TASK>
```

Another point of interest is that, when in this situation:
 * `lsusb` hangs after printing out a few lines
 * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards.

So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 12 09:42:52 2024
InstallationDate: Installed on 2022-06-28 (653 days ago)
InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Richard van der Hoff (richvdh) wrote :
Revision history for this message
Richard van der Hoff (richvdh) wrote :
Changed in linux-signed-hwe-6.5 (Ubuntu):
assignee: nobody → Anthony Wong (anthonywong)
Changed in linux-signed-hwe-6.5 (Ubuntu):
assignee: Anthony Wong (anthonywong) → GuoqingJiang (guoqingjiang)
Revision history for this message
GuoqingJiang (guoqingjiang) wrote :

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 :

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 :

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

Revision history for this message
GuoqingJiang (guoqingjiang) wrote :
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...

Read more...

Revision history for this message
GuoqingJiang (guoqingjiang) wrote :
Download full text (3.6 KiB)

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.

Apr 15 21:48:23 xps9320 kernel: [43261.751897] INFO: task kworker/0:6:34416 blocked for more than 120 seconds.
Apr 15 21:48:23 xps9320 kernel: [43261.751900] Tainted: G OE 6.5.0-27-generic #28~22.04.1-Ubuntu
Apr 15 21:48:23 xps9320 kernel: [43261.751901] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 15 21:48:23 xps9320 kernel: [43261.751903] task:kworker/0:6 state:D stack:0 pid:34416 ppid:2 flags:0x00004000
Apr 15 21:48:23 xps9320 kernel: [43261.751907] Workqueue: usb_hub_wq hub_event
Apr 15 21:48:23 xps9320 kernel: [43261.751913] Call Trace:
Apr 15 21:48:23 xps9320 kernel: [43261.751915] <TASK>
Apr 15 21:48:23 xps9320 kernel: [43261.751916] __schedule+0x2cb/0x750
Apr 15 21:48:23 xps9320 kernel: [43261.751921] schedule+0x63/0x110
Apr 15 21:48:23 xps9320 kernel: [43261.751924] schedule_preempt_disabled+0x15/0x30
Apr 15 21:48:23 xps9320 kernel: [43261.751928] rwsem_down_write_slowpath+0x2a2/0x550
Apr 15 21:48:23 xps9320 kernel: [43261.751940] down_write+0x5c/0x80
Apr 15 21:48:23 xps9320 kernel: [43261.751945] snd_pcm_dev_disconnect+0x1d2/0x280 [snd_pcm]
Apr 15 21:48:23 xps9320 kernel: [43261.751964] snd_device_disconnect_all+0x47/0xa0 [snd]
Apr 15 21:48:23 xps9320 kernel: [43261.751979] snd_card_disconnect.part.0+0x10d/0x290 [snd]
Apr 15 21:48:23 xps9320 kernel: [43261.752019] ? rpm_idle+0x25/0x2b0
Apr 15 21:48:23 xps9320 kernel: [43261.752023] snd_card_disconnect+0x13/0x30 [snd]
Apr 15 21:48:23 xps9320 kernel: [43261.752039] usb_audio_disconnect+0x114/0x2c0 [snd_usb_audio]
Apr 15 21:48:23 xps9320 kernel: [43261.752064] usb_unbind_interface+0x8e/0x280
Apr 15 21:48:23 xps9320 kernel: [43261.752069] device_remove+0x65/0x80
Apr 15 21:48:23 xps9320 kernel: [43261.752072] device_release_driver_internal+0x20b/0x270
Apr 15 21:48:23 xps9320 kernel: [43261.752077] device_release_driver+0x12/0x20
Apr 15 21:48:23 xps9320 kernel: [43261.752080] bus_remove_device+0xcb/0x140
Apr 15 21:48:23 xps9320 kernel: [43261.752083] device_del+0x161/0x3e0
Apr 15 21:48:23 xps9320 kernel: [43261.752086] ? kobject_put+0x67/0xa0
Apr 15 21:48:23 xps9320 kernel: [43261.752090] usb_disable_device+0xd5/0x280
Apr 15 21:48:23 xps9320 kernel: [43261.752093] usb_disconnect+0xe9/0x2e0
Apr 15 21:48:23 xps9320 kernel: [43261.752097] usb_disconnect+0xcd/0x2e0
Apr 15 21:48:23 xps9320 kernel: [43261.752100] usb_disconnect+0xcd/0x2e0
Apr 15 21:48:23 xps9320 kernel: [43261.752102] ? usb_control_msg+0x106/0x160
Apr 15 21:48:23 xps9320 kernel: [43261.752105] hub_port_connect+0x90/0xc30
Apr 15 21:48:23 xps9320 kernel: [43261.752109] hub_port_connect_change+0x91/0x300
Apr 15 21:48:23 xps9320 kernel: [43261.752113] port_event+0x652/0x810
Apr 15 21:48:23 xps9320 kernel: [43261.752117] hub_event+0x155/0x450
Apr 15 21:48:23 xps9320 kernel: [43261.752120] process_one_work+0x23d/0x450
Apr 15 21:48:23 xps9320 kernel: [43261.752125...

Read more...

Revision history for this message
GuoqingJiang (guoqingjiang) wrote :
Download full text (4.1 KiB)

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 2...

Read more...

Revision history for this message
Richard van der Hoff (richvdh) wrote :

> 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 :

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 :
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...

Revision history for this message
GuoqingJiang (guoqingjiang) wrote :

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 :

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

Revision history for this message
Richard van der Hoff (richvdh) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.