This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2013019
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/2013019
Title:
ubuntu_nbd_smoke_test- failure with lunar/linux 6.2
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Lunar:
Incomplete
Bug description:
[Impact]
nbd smoke test is triggering the following hung task timeout trace
with lunar/linux 6.2:
615 10:58:25 DEBUG| [stdout] [ 484.429923] INFO: task
systemd-udevd:16656 blocked for more than 120 seconds.
616 10:58:25 DEBUG| [stdout] [ 484.431061]
Not tainted 6.2.0-19-generic #19-Ubuntu
617 10:58:25 DEBUG| [stdout] [ 484.431909] "echo 0
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
618 10:58:25 DEBUG| [stdout] [ 484.433101]
task:systemd-udevd state:D stack:0 pid:16656 ppid:342 flags:0x00000805
619 10:58:25 DEBUG| [stdout] [ 484.433109] Call
trace:
620 10:58:25 DEBUG| [stdout] [ 484.433112]
__switch_to+0xbc/0x100
621 10:58:25 DEBUG| [stdout] [ 484.433121]
__schedule+0x2fc/0x7b0
622 10:58:25 DEBUG| [stdout] [ 484.433126]
schedule+0x68/0x160
623 10:58:25 DEBUG| [stdout] [ 484.433129]
schedule_preempt_disabled+0x30/0x60
624 10:58:25 DEBUG| [stdout] [ 484.433134]
__mutex_lock.constprop.0+0x2f4/0x670
625 10:58:25 DEBUG| [stdout] [ 484.433139]
__mutex_lock_slowpath+0x20/0x40
626 10:58:25 DEBUG| [stdout] [ 484.433143]
mutex_lock+0x98/0xc4
627 10:58:25 DEBUG| [stdout] [ 484.433147]
blkdev_get_by_dev.part.0+0x11c/0x320
628 10:58:25 DEBUG| [stdout] [ 484.433153]
blkdev_get_by_dev+0x84/0xb0
629 10:58:25 DEBUG| [stdout] [ 484.433158]
blkdev_open+0x74/0xd0
630 10:58:25 DEBUG| [stdout] [ 484.433163]
do_dentry_open+0x1e4/0x4b4
631 10:58:25 DEBUG| [stdout] [ 484.433167]
vfs_open+0x38/0x64
632 10:58:25 DEBUG| [stdout] [ 484.433171]
do_open+0x350/0x430
633 10:58:25 DEBUG| [stdout] [ 484.433177]
path_openat+0x144/0x290
634 10:58:25 DEBUG| [stdout] [ 484.433180]
do_filp_open+0xac/0x180
635 10:58:25 DEBUG| [stdout] [ 484.433183]
do_sys_openat2+0xf0/0x1ac
636 10:58:25 DEBUG| [stdout] [ 484.433188]
__arm64_sys_openat+0x70/0xd0
637 10:58:25 DEBUG| [stdout] [ 484.433192]
invoke_syscall+0x7c/0x124
638 10:58:25 DEBUG| [stdout] [ 484.433196]
el0_svc_common.constprop.0+0x1a4/0x1cc
639 10:58:25 DEBUG| [stdout] [ 484.433200]
do_el0_svc+0x38/0x60
640 10:58:25 DEBUG| [stdout] [ 484.433203]
el0_svc+0x30/0xe0
641 10:58:25 DEBUG| [stdout] [ 484.433208]
el0t_64_sync_handler+0x11c/0x150
642 10:58:25 DEBUG| [stdout] [ 484.433213]
el0t_64_sync+0x1a8/0x1ac
This trace seems to happen also with 6.1. In 5.19 the trace doesn't
happen, but the test is also broken, because it's not possible to
read/write from/to the nbd device that is created (/dev/nbd0).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013019/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
