RCU stalls

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 1991951

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.

https://lists.ubuntu.com/archives/kernel-team/2022-October/133734.html

This bug was fixed in the package linux - 5.19.0-21.21

---------------
linux (5.19.0-21.21) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-21.21 -proposed tracker (LP: #1992639)

  * cannot change mount namespace (LP: #1991691)
    - SAUCE: apparmor: Fix getaatr mediation causing snap failures

  * Kernel regresses openjdk on riscv64 (LP: #1992484)
    - SAUCE: Revert "riscv: mmap with PROT_WRITE but no PROT_READ is invalid"

 -- Andrea Righi <email address hidden> Wed, 12 Oct 2022 19:53:36 +0200

This bug is awaiting verification that the linux-hwe-5.19/5.19.0-24.25~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

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!

Kernel 6.0.0 also has this bug

ASRock X670E Taichi
Ryzen 9 7950X
32GB DDR5-5600 C32
AMD Radeon 6700XT
1x NVMe 4.0 1TB SSD (boot, home, 64GB swap part)
1x NVMe 4.0 2TB SSD (dev, VMs, 128GB swapfile)
1x NVMe 3.0 2TB SSD (games)

dmesg excerpt:

5.626458] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 15-.... } 6 jiffies s: 185 root: 0x1/.
[ 5.626645] rcu: blocking rcu_node structures (internal RCU debug): l=1:0-15:0x8000/.
[ 5.626737] Task dump for CPU 15:
[ 5.626738] task:systemd-udevd state:R running task stack: 0 pid: 721 ppid: 700 flags:0x0000400a
[ 5.626740] Call Trace:
[ 5.626741] <TASK>
[ 5.626742] ? kallsyms_lookup_buildid+0x109/0x180
[ 5.626746] ? kallsyms_lookup+0x14/0x30
[ 5.626747] ? test_for_valid_rec+0x6d/0xc0
[ 5.626750] ? ftrace_module_enable+0xad/0x2c0
[ 5.626751] ? set_memory_x+0x4e/0x70
[ 5.626753] ? load_module+0x64b/0xc10
[ 5.626755] ? __do_sys_finit_module+0xc4/0x140
[ 5.626755] ? __do_sys_finit_module+0xc4/0x140
[ 5.626756] ? __x64_sys_finit_module+0x18/0x30
[ 5.626757] ? do_syscall_64+0x5b/0x90
[ 5.626760] ? do_syscall_64+0x67/0x90
[ 5.626761] ? sysvec_call_function_single+0x4b/0xd0
[ 5.626762] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 5.626764] </TASK>
[ 5.706458] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 15-.... } 26 jiffies s: 185 root: 0x1/.
[ 5.706655] rcu: blocking rcu_node structures (internal RCU debug): l=1:0-15:0x8000/.
[ 5.706756] Task dump for CPU 15:
[ 5.706757] task:systemd-udevd state:R running task stack: 0 pid: 721 ppid: 700 flags:0x0000400a
[ 5.706759] Call Trace:
[ 5.706759] <TASK>
[ 5.706760] ? kallsyms_lookup_buildid+0x109/0x180
[ 5.706762] ? kallsyms_lookup+0x14/0x30
[ 5.706763] ? test_for_valid_rec+0x6d/0xc0
[ 5.706765] ? ftrace_module_enable+0xad/0x2c0
[ 5.706766] ? set_memory_x+0x4e/0x70
[ 5.706767] ? load_module+0x64b/0xc10
[ 5.706768] ? __do_sys_finit_module+0xc4/0x140
[ 5.706769] ? __do_sys_finit_module+0xc4/0x140
[ 5.706771] ? __x64_sys_finit_module+0x18/0x30
[ 5.706771] ? do_syscall_64+0x5b/0x90
[ 5.706773] ? do_syscall_64+0x67/0x90
[ 5.706773] ? sysvec_call_function_single+0x4b/0xd0
[ 5.706774] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 5.706776] </TASK>
[ 5.786457] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 15-.... } 46 jiffies s: 185 root: 0x1/.
[ 5.786665] rcu: blocking rcu_node structures (internal RCU debug): l=1:0-15:0x8000/.
[ 5.786772] Task dump for CPU 15:
[ 5.786773] task:systemd-udevd state:R running task stack: 0 pid: 721 ppid: 700 flags:0x0000400a
[ 5.786774] Call Trace:
[ 5.786775] <TASK>
[ 5.786775] ? kallsyms_lookup_buildid+0x109/0x180
[ 5.786778] ? kallsyms_lookup+0x14/0x30
[ 5.786779] ? test_for_valid_rec+0x6d/0xc0
[ 5.786780] ? ftrace_module_enable+0xad/0x2c0
[ 5.786781] ? set_memory_x+0x4e/0x70
[ 5.786782] ? load_module+0x64b/0xc10
[ 5.786784] ? __do_sys_finit_module+0xc4/0x140
[ 5.786785] ? __do_sys_finit_module+0xc4/0x140
[ 5.786786] ? __x64_sys_finit_module+0...

This bug is awaiting verification that the linux/5.15.0-59.65 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' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

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!

This bug was fixed in the package linux - 5.15.0-60.66

---------------
linux (5.15.0-60.66) jammy; urgency=medium

  * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)

  * Revoke & rotate to new signing key (LP: #2002812)
    - [Packaging] Revoke and rotate to new signing key

linux (5.15.0-59.65) jammy; urgency=medium

  * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801)

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts

  * CVE-2022-47940
    - ksmbd: validate length in smb2_write()

  * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115)
    - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled
    - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x

  * support for same series backports versioning numbers (LP: #1993563)
    - [Packaging] sameport -- add support for sameport versioning

  * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later
    (LP: #1999528)
    - [DEP-8] Fix regression suite to run on lowlatency

  * Micron NVME storage failure [1344,5407] (LP: #1998883)
    - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH

  * Jammy update: v5.15.78 upstream stable release (LP: #1998843)
    - scsi: lpfc: Rework MIB Rx Monitor debug info logic
    - serial: ar933x: Deassert Transmit Enable on ->rs485_config()
    - KVM: x86: Trace re-injected exceptions
    - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1)
    - drm/amd/display: explicitly disable psr_feature_enable appropriately
    - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page
    - HID: playstation: add initial DualSense Edge controller support
    - KVM: x86: Protect the unused bits in MSR exiting flags
    - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter()
    - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER
    - RDMA/cma: Use output interface for net_dev check
    - IB/hfi1: Correctly move list in sc_disable()
    - RDMA/hns: Remove magic number
    - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx()
    - RDMA/hns: Disable local invalidate operation
    - NFSv4: Fix a potential state reclaim deadlock
    - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors
    - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot
    - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed
    - NFSv4.2: Fixup CLONE dest file size for zero-length count
    - nfs4: Fix kmemleak when allocate slot failed
    - net: dsa: Fix possible memory leaks in dsa_loop_init()
    - RDMA/core: Fix null-ptr-deref in ib_core_cleanup()
    - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources()
    - net: dsa: fall back to default tagger if we can't load the one from DT
    - nfc: fdp: Fix potential memory leak in fdp_nci_send()
    - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send()
    - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send()
    - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send()
    - net: fec: fix improper use of NETDEV_TX_BUSY
    - ata: pata_legacy: fix pdc20230_set_piomode()
    - net: sched: Fix use after free in red_...

This bug is awaiting verification that the linux-azure/5.15.0-1034.41 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' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

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!

This bug is awaiting verification that the linux-aws/5.15.0-1031.35 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' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

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!

This bug is awaiting verification that the linux-realtime/5.15.0-1033.36 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' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

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!

I hit this problem 'rcp_preemp detected expedited stalls on CPUs/tasks' today. When it appears, ssh breaks and any command can not be run. After upgrading the kernel to a version larger than 5.15.0-60.66 (it's 5.15.0-74-generic now), the problem disappeared.

This bug is awaiting verification that the linux-aws-5.15/5.15.0-1046.51~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!

This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 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!

Alright, I don't know who you are. Or why you sound like a robocop While
you're spamming with this old crap, but whatever.

On Fri, Mar 1, 2024, 1:03 AM Ubuntu Kernel Bot <email address hidden>
wrote:

> This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
> 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
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1991027).
> https://bugs.launchpad.net/bugs/1991951
>
> Title:
> RCU stalls
>
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Fix Released
>
> Bug description:
> our RCU Stall Timeouts are different to upstream defaults; with
> regular one 3x longer; and expedited one 1000x shorter.
>
> not sure why.
>
> Let's harmonize on 60 & 0, which is 60 for regular ones that are set
> on most architectures; and upstream default for the expedited ones.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991951/+subscriptions
>
>

Written by nerds with no communication skil.

On Fri, Mar 1, 2024, 1:47 AM Stephen Crowley <email address hidden>
wrote:

> Alright, I don't know who you are. Or why you sound like a robocop While
> you're spamming with this old crap, but whatever.
>
> On Fri, Mar 1, 2024, 1:03 AM Ubuntu Kernel Bot <email address hidden>
> wrote:
>
>> This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
>> 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
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1991027).
>> https://bugs.launchpad.net/bugs/1991951
>>
>> Title:
>> RCU stalls
>>
>> Status in linux package in Ubuntu:
>> Fix Released
>> Status in linux source package in Jammy:
>> Fix Released
>>
>> Bug description:
>> our RCU Stall Timeouts are different to upstream defaults; with
>> regular one 3x longer; and expedited one 1000x shorter.
>>
>> not sure why.
>>
>> Let's harmonize on 60 & 0, which is 60 for regular ones that are set
>> on most architectures; and upstream default for the expedited ones.
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991951/+subscriptions
>>
>>