[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
Seems I was mistaken. This happens on 6.8 as well. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+attachment/5773507/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New 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:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] 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.96] ? 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:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
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:0x0002 Apr 29 21:24:36 xps9320 kernel: [280990.641360] Call Trace: Apr 29 21:24:36 xps9320 kernel: [280990.641367] 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:7ffc84003090 EFLAGS: 0246 ORIG_RAX: 0010 Apr 29 21:24:36 xps9320 kernel: [280990.641701] RAX: ffda RBX: 7ffc84003100 RCX: 70991f71a94f Apr 29 21:24:36 xps9320 kernel: [280990.641707] RDX: 7ffc84003100 RSI: c1105511 RDI: 0022 Apr 29 21:24:36 xps9320 kernel: [280990.641713] RBP: 7ffc840032e0 R08: 6231bc666330 R09: 0004 Apr 29 21:24:36 xps9320 kernel: [280990.641718] R10: f314 R11: 0246 R12: 6231bc90dc50 Apr 29 21:24:36 xps9320 kernel: [280990.641723] R13: 6231bc7c9140 R14: 7ffc84003280 R15: 7ffc84003220 Apr 29 21:24:36 xps9320 kernel: [280990.641745] Apr 29 21:24:36 xps9320 kernel: [280990.64] 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:0x4000 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] 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] d
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New 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:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] 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.96] ? 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:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
> 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New 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:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] 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.96] ? 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:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` 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: u
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
Here's the kern.log since the last-but-one reboot. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+attachment/5766127/+files/kern.log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New 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:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] 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.96] ? 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:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
rav@xps9320:~$ cat /proc/asound/modules 0 snd_soc_sof_sdw 1 snd_usb_audio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New 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:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] 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.96] ? 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:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New 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:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] 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.96] ? 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:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061091] [NEW] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
Public bug reported: 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:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] 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.96] ? 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:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` 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) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New 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:0x0006 Apr 12 08:59:54 xps9320 kernel: [1731
[Kernel-packages] [Bug 1919307] Re: kernel hang
5.4 was a long time ago, so I guess there's no point keeping this open ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1919307 Title: kernel hang Status in linux package in Ubuntu: Invalid Bug description: My system locked up, and stopped responding to mouse movement, keyboard, network traffic, etc. A few minutes later, it appeared to recover, although my X session restarted and I had to log back in. I found this in my kern.log: Mar 16 09:08:33 fred kernel: [83775.521219] INFO: task jbd2/dm-1-8:1142 blocked for more than 10 seconds. Mar 16 09:08:33 fred kernel: [83775.521223] Tainted: G OE 5.4.0-65-generic #73-Ubuntu Mar 16 09:08:33 fred kernel: [83775.521224] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 16 09:08:33 fred kernel: [83775.521226] jbd2/dm-1-8 D0 1142 2 0x80004000 Mar 16 09:08:33 fred kernel: [83775.521228] Call Trace: Mar 16 09:08:33 fred kernel: [83775.521235] __schedule+0x2e3/0x740 Mar 16 09:08:33 fred kernel: [83775.521238] ? dm_process_bio+0x89/0x100 Mar 16 09:08:33 fred kernel: [83775.521240] ? bit_wait_timeout+0xa0/0xa0 Mar 16 09:08:33 fred kernel: [83775.521241] schedule+0x42/0xb0 Mar 16 09:08:33 fred kernel: [83775.521243] io_schedule+0x16/0x40 Mar 16 09:08:33 fred kernel: [83775.521244] bit_wait_io+0x11/0x50 Mar 16 09:08:33 fred kernel: [83775.521246] __wait_on_bit+0x33/0xa0 Mar 16 09:08:33 fred kernel: [83775.521248] ? submit_bio+0x48/0x1d0 Mar 16 09:08:33 fred kernel: [83775.521250] out_of_line_wait_on_bit+0x8d/0xb0 Mar 16 09:08:33 fred kernel: [83775.521252] ? var_wake_function+0x30/0x30 Mar 16 09:08:33 fred kernel: [83775.521254] __wait_on_buffer+0x34/0x40 Mar 16 09:08:33 fred kernel: [83775.521258] jbd2_journal_commit_transaction+0xf50/0x17e8 Mar 16 09:08:33 fred kernel: [83775.521262] kjournald2+0xb6/0x280 Mar 16 09:08:33 fred kernel: [83775.521264] ? wait_woken+0x80/0x80 Mar 16 09:08:33 fred kernel: [83775.521267] kthread+0x104/0x140 Mar 16 09:08:33 fred kernel: [83775.521268] ? commit_timeout+0x20/0x20 Mar 16 09:08:33 fred kernel: [83775.521269] ? kthread_park+0x90/0x90 Mar 16 09:08:33 fred kernel: [83775.521271] ret_from_fork+0x35/0x40 Mar 16 09:08:33 fred kernel: [83775.521324] INFO: task alsa-sink-USB A:3405 blocked for more than 10 seconds. Mar 16 09:08:33 fred kernel: [83775.521326] Tainted: G OE 5.4.0-65-generic #73-Ubuntu Mar 16 09:08:33 fred kernel: [83775.521327] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 16 09:08:33 fred kernel: [83775.521328] alsa-sink-USB A D0 3405 3321 0x0320 Mar 16 09:08:33 fred kernel: [83775.521329] Call Trace: Mar 16 09:08:33 fred kernel: [83775.521332] __schedule+0x2e3/0x740 Mar 16 09:08:33 fred kernel: [83775.521334] ? __switch_to_asm+0x34/0x70 Mar 16 09:08:33 fred kernel: [83775.521336] schedule+0x42/0xb0 Mar 16 09:08:33 fred kernel: [83775.521337] io_schedule+0x16/0x40 Mar 16 09:08:33 fred kernel: [83775.521340] wait_on_page_bit+0x11c/0x200 Mar 16 09:08:33 fred kernel: [83775.521342] ? file_fdatawait_range+0x30/0x30 Mar 16 09:08:33 fred kernel: [83775.521344] wait_on_page_writeback+0x43/0x90 Mar 16 09:08:33 fred kernel: [83775.521346] shmem_swapin_page+0x23b/0x660 Mar 16 09:08:33 fred kernel: [83775.521348] ? xas_load+0xd/0x80 Mar 16 09:08:33 fred kernel: [83775.521349] ? find_get_entry+0x5e/0x170 Mar 16 09:08:33 fred kernel: [83775.521351] shmem_getpage_gfp+0x3c8/0x940 Mar 16 09:08:33 fred kernel: [83775.521354] ? page_add_file_rmap+0xff/0x1a0 Mar 16 09:08:33 fred kernel: [83775.521355] shmem_fault+0x79/0x210 Mar 16 09:08:33 fred kernel: [83775.521358] __do_fault+0x3c/0x130 Mar 16 09:08:33 fred kernel: [83775.521359] do_fault+0x24b/0x640 Mar 16 09:08:33 fred kernel: [83775.521361] __handle_mm_fault+0x4c5/0x7a0 Mar 16 09:08:33 fred kernel: [83775.521363] handle_mm_fault+0xca/0x200 Mar 16 09:08:33 fred kernel: [83775.521365] do_user_addr_fault+0x1f9/0x450 Mar 16 09:08:33 fred kernel: [83775.521368] __do_page_fault+0x58/0x90 Mar 16 09:08:33 fred kernel: [83775.521369] do_page_fault+0x2c/0xe0 Mar 16 09:08:33 fred kernel: [83775.521371] page_fault+0x34/0x40 Mar 16 09:08:33 fred kernel: [83775.521373] RIP: 0033:0x7f94a7e13210 Mar 16 09:08:33 fred kernel: [83775.521378] Code: Bad RIP value. Mar 16 09:08:33 fred kernel: [83775.521378] RSP: 002b:7f94a0a54390 EFLAGS: 00010206 Mar 16 09:08:33 fred kernel: [83775.521380] RAX: 7f94a2e37000 RBX: 558cba86ea00 RCX: 0001 Mar 16 09:08:33 fred kernel: [83775.521381] RDX: 000327d20610 RSI: 7f94a0a54680 RDI: 7f94a2e37000 Mar 16 09:08:33 fred kernel: [83775.521382] RBP: 7f94a0a54680 R08:
[Kernel-packages] [Bug 1992362] [NEW] USB stops responding on XPS9320
Public bug reported: An intermittent problem, but to reproduce: * unplug a USB device * plug it back in * notice it hasn't been detected After this point, no amount of plugging or unplugging seems to change anything: nothing appears in `dmesg`, `lsusb` shows only internal USB hardware, and video-over-USB devices do not appear in `/sys/class/drm`. Both USB ports are similarly unresponsive. The only remedy appears to be to reboot. `dmesg` shows the unplug event, but nothing after that: ``` Oct 10 16:38:55 xps9320 kernel: [ 2103.140449] usb 3-1: USB disconnect, device number 2 Oct 10 16:38:55 xps9320 kernel: [ 2103.140457] usb 3-1.2: USB disconnect, device number 4 Oct 10 16:38:55 xps9320 kernel: [ 2103.140459] usb 3-1.2.3: USB disconnect, device number 7 Oct 10 16:38:55 xps9320 kernel: [ 2103.140462] usb 3-1.2.3.1: USB disconnect, device number 10 Oct 10 16:38:55 xps9320 kernel: [ 2103.221393] r8152 2-1.2.4:1.0 enx00e04c681052: Stop submitting intr, status -71 Oct 10 16:38:55 xps9320 kernel: [ 2103.423464] usb 3-1.2.3.2: USB disconnect, device number 11 Oct 10 16:38:55 xps9320 kernel: [ 2103.753373] usb 3-1.2.5: USB disconnect, device number 9 Oct 10 16:38:55 xps9320 kernel: [ 2103.772563] usb 3-1.5: USB disconnect, device number 6 Oct 10 16:38:55 xps9320 kernel: [ 2103.904926] usb 2-1: USB disconnect, device number 2 Oct 10 16:38:55 xps9320 kernel: [ 2103.904947] usb 2-1.2: USB disconnect, device number 3 Oct 10 16:38:55 xps9320 kernel: [ 2103.904954] usb 2-1.2.4: USB disconnect, device number 4 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rav2115 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Mon Oct 10 17:01:04 2022 InstallationDate: Installed on 2022-06-28 (103 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 9320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2022 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0CW9KM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/13/2022:br1.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn0CW9KM:rvrA00:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992362 Title: USB stops responding on XPS9320 Status in linux package in Ubuntu: New Bug description: An intermittent problem, but to reproduce: * unplug a USB device * plug it back in * notice it hasn't been detected After this point, no amount of plugging or unplugging seems to change anything: nothing appears in `dmesg`, `lsusb` shows only internal USB hardware, and video-over-USB devices do not appear in `/sys/class/drm`. Both USB ports are similarly unresponsive. The only remedy appears to be to reboot. `dmesg` shows the unplug event, but nothing after that: ``` Oct 10 16:38:55 xps9320 kernel: [ 2103.140449] usb 3-1: USB disconnect, device number 2 Oct 10 16:38:55 xps9320 kernel: [ 2103.140457] usb 3-1.2: USB disconnect, device number 4 Oct 10 16:38:55 xps9320 kernel: [ 2103.140459] usb 3-1.2.3: USB disconnect, device number 7 Oct 10 16:38:55 xps9320 kernel: [ 2103.140462] usb 3-1.2.3.1: USB disconnect, device number 10 Oct 10 16:38:55 xps9320 kernel: [ 2103.221393] r8152 2-1.2.4:1.0 enx00e04c681052: Stop submitting intr, status -71 Oct 10 16:38:55 xps9320 kernel: [ 2103.423464] usb 3-1.2.3.2: USB disconnect, device number 11 Oct 10 16:38:55 xps9320 kernel: [ 2103.753373] usb 3-1.2.5: USB disconnect, device number 9 Oct 10 16:38:55 xps9320 kernel: [ 2103.772563] usb 3-1.5: USB disconnect, device number 6 Oct 10 16:38:55 xps9320 kernel: [ 2103.904926] usb 2-1: USB disconnect, device number 2 Oct 10 16:38:55 xps9320 kernel: [ 2103.904947] usb 2-1.2: USB disconnect, device number 3 Oct 10 16:38:55 xps9320 kernel: [ 2103.904954] usb 2-1.2.4: USB disconnect, device number 4 ``` Probl
[Kernel-packages] [Bug 1919307] [NEW] kernel hang
Public bug reported: My system locked up, and stopped responding to mouse movement, keyboard, network traffic, etc. A few minutes later, it appeared to recover, although my X session restarted and I had to log back in. I found this in my kern.log: Mar 16 09:08:33 fred kernel: [83775.521219] INFO: task jbd2/dm-1-8:1142 blocked for more than 10 seconds. Mar 16 09:08:33 fred kernel: [83775.521223] Tainted: G OE 5.4.0-65-generic #73-Ubuntu Mar 16 09:08:33 fred kernel: [83775.521224] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 16 09:08:33 fred kernel: [83775.521226] jbd2/dm-1-8 D0 1142 2 0x80004000 Mar 16 09:08:33 fred kernel: [83775.521228] Call Trace: Mar 16 09:08:33 fred kernel: [83775.521235] __schedule+0x2e3/0x740 Mar 16 09:08:33 fred kernel: [83775.521238] ? dm_process_bio+0x89/0x100 Mar 16 09:08:33 fred kernel: [83775.521240] ? bit_wait_timeout+0xa0/0xa0 Mar 16 09:08:33 fred kernel: [83775.521241] schedule+0x42/0xb0 Mar 16 09:08:33 fred kernel: [83775.521243] io_schedule+0x16/0x40 Mar 16 09:08:33 fred kernel: [83775.521244] bit_wait_io+0x11/0x50 Mar 16 09:08:33 fred kernel: [83775.521246] __wait_on_bit+0x33/0xa0 Mar 16 09:08:33 fred kernel: [83775.521248] ? submit_bio+0x48/0x1d0 Mar 16 09:08:33 fred kernel: [83775.521250] out_of_line_wait_on_bit+0x8d/0xb0 Mar 16 09:08:33 fred kernel: [83775.521252] ? var_wake_function+0x30/0x30 Mar 16 09:08:33 fred kernel: [83775.521254] __wait_on_buffer+0x34/0x40 Mar 16 09:08:33 fred kernel: [83775.521258] jbd2_journal_commit_transaction+0xf50/0x17e8 Mar 16 09:08:33 fred kernel: [83775.521262] kjournald2+0xb6/0x280 Mar 16 09:08:33 fred kernel: [83775.521264] ? wait_woken+0x80/0x80 Mar 16 09:08:33 fred kernel: [83775.521267] kthread+0x104/0x140 Mar 16 09:08:33 fred kernel: [83775.521268] ? commit_timeout+0x20/0x20 Mar 16 09:08:33 fred kernel: [83775.521269] ? kthread_park+0x90/0x90 Mar 16 09:08:33 fred kernel: [83775.521271] ret_from_fork+0x35/0x40 Mar 16 09:08:33 fred kernel: [83775.521324] INFO: task alsa-sink-USB A:3405 blocked for more than 10 seconds. Mar 16 09:08:33 fred kernel: [83775.521326] Tainted: G OE 5.4.0-65-generic #73-Ubuntu Mar 16 09:08:33 fred kernel: [83775.521327] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 16 09:08:33 fred kernel: [83775.521328] alsa-sink-USB A D0 3405 3321 0x0320 Mar 16 09:08:33 fred kernel: [83775.521329] Call Trace: Mar 16 09:08:33 fred kernel: [83775.521332] __schedule+0x2e3/0x740 Mar 16 09:08:33 fred kernel: [83775.521334] ? __switch_to_asm+0x34/0x70 Mar 16 09:08:33 fred kernel: [83775.521336] schedule+0x42/0xb0 Mar 16 09:08:33 fred kernel: [83775.521337] io_schedule+0x16/0x40 Mar 16 09:08:33 fred kernel: [83775.521340] wait_on_page_bit+0x11c/0x200 Mar 16 09:08:33 fred kernel: [83775.521342] ? file_fdatawait_range+0x30/0x30 Mar 16 09:08:33 fred kernel: [83775.521344] wait_on_page_writeback+0x43/0x90 Mar 16 09:08:33 fred kernel: [83775.521346] shmem_swapin_page+0x23b/0x660 Mar 16 09:08:33 fred kernel: [83775.521348] ? xas_load+0xd/0x80 Mar 16 09:08:33 fred kernel: [83775.521349] ? find_get_entry+0x5e/0x170 Mar 16 09:08:33 fred kernel: [83775.521351] shmem_getpage_gfp+0x3c8/0x940 Mar 16 09:08:33 fred kernel: [83775.521354] ? page_add_file_rmap+0xff/0x1a0 Mar 16 09:08:33 fred kernel: [83775.521355] shmem_fault+0x79/0x210 Mar 16 09:08:33 fred kernel: [83775.521358] __do_fault+0x3c/0x130 Mar 16 09:08:33 fred kernel: [83775.521359] do_fault+0x24b/0x640 Mar 16 09:08:33 fred kernel: [83775.521361] __handle_mm_fault+0x4c5/0x7a0 Mar 16 09:08:33 fred kernel: [83775.521363] handle_mm_fault+0xca/0x200 Mar 16 09:08:33 fred kernel: [83775.521365] do_user_addr_fault+0x1f9/0x450 Mar 16 09:08:33 fred kernel: [83775.521368] __do_page_fault+0x58/0x90 Mar 16 09:08:33 fred kernel: [83775.521369] do_page_fault+0x2c/0xe0 Mar 16 09:08:33 fred kernel: [83775.521371] page_fault+0x34/0x40 Mar 16 09:08:33 fred kernel: [83775.521373] RIP: 0033:0x7f94a7e13210 Mar 16 09:08:33 fred kernel: [83775.521378] Code: Bad RIP value. Mar 16 09:08:33 fred kernel: [83775.521378] RSP: 002b:7f94a0a54390 EFLAGS: 00010206 Mar 16 09:08:33 fred kernel: [83775.521380] RAX: 7f94a2e37000 RBX: 558cba86ea00 RCX: 0001 Mar 16 09:08:33 fred kernel: [83775.521381] RDX: 000327d20610 RSI: 7f94a0a54680 RDI: 7f94a2e37000 Mar 16 09:08:33 fred kernel: [83775.521382] RBP: 7f94a0a54680 R08: 0dc8 R09: 558cba90ca70 Mar 16 09:08:33 fred kernel: [83775.521382] R10: 0e60 R11: 0246 R12: 485c Mar 16 09:08:33 fred kernel: [83775.521383] R13: R14: 558cba873810 R15: 0001 Mar 16 09:08:33 fred kernel: [83775.521420] Call Trace: Mar 16 09:08:33 fred kernel: [83775.521422] __schedule+0x2e3/0x740 Mar 16 09:08:33 fred kernel: [83775.521424] schedule+0x42/0xb0 Mar 16 09:08:33 fred kernel: [83775.52
[Kernel-packages] [Bug 1404558] Re: IPv6 related kernel panic following upgrade to 3.13.0-43
I was previously seeing this problem; I've now upgraded to 3.1.0-46 and am seeing a similar, but slightly different, panic (see attached) ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404558/+attachment/4329425/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1404558 Title: IPv6 related kernel panic following upgrade to 3.13.0-43 Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Released Bug description: After updating a dozen machines from 3.13.0-40 to 3.13.0-43, they all kernel panic within the next 24 hours. I managed to pull the console from one over an IP KVM and it shows a panic related to IPv6 networking: https://dl.stgraber.org/panic-3.13-43.png All affected machines had native IPv6 connectivity to the Internet. Downgrading to 3.13.0-40 resolved the issue (so it's clearly a regression) and upgrading to lts-utopic 3.16.0-28-generic also appeared to do the trick. A friend also just reported seeing the exact same problem on his server which also has native IPv6 connectivity so the issue appears pretty widespread. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
