From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: linux5.19: Set CONFIG_RCU_EXP_CPU_STALL_TIMEOUT to zero
Date: Fri, 02 Sep 2022 17:33:48 +0200 [thread overview]
Message-ID: <20220902153348.nj85lTLzooKQ9VKgzTuIz9_MnSF7WvIxpEs-nC0h438@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39023@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 4174 bytes --]
There's a closed pull request on the void-packages repository
linux5.19: Set CONFIG_RCU_EXP_CPU_STALL_TIMEOUT to zero
https://github.com/void-linux/void-packages/pull/39023
Description:
Linux 5.19 causes an rcu stall error on boot.
Diffing the 5.19 and 5.15 config I found the addition of the new CONFIG_RCU_EXP_CPU_STALL_TIMEOUT,
which appears erroneously defined as 20, as the Void kernel config defines CONFIG_ANDROID ¹.
Setting CONFIG_RCU_EXP_CPU_STALL_TIMEOUT to zero, which should be the same behaviour as in previous kernels,
fixes the problem.
¹ https://www.kernel.org/doc/html/latest/RCU/stallwarn.html
This has been fixed in kernel v6.0: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1045a06724f322ed61f1ffb994427c7bdbe64647
Thread I found this fix and information from:
https://lkml.org/lkml/2022/6/28/1051
https://lore.kernel.org/all/1656357116.rhe0mufk6a.none@localhost/
dmesg when set to 20:
```
kern.err: [ 2.424048] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-... } 21 jiffies s: 29 root: 0x1/.
kern.info: [ 2.424059] fbcon: Taking over console
kern.err: [ 2.424063] rcu: blocking rcu_node structures (internal RCU debug):
kern.info: [ 2.424066] Task dump for CPU 0:
kern.info: [ 2.424068] task:kworker/0:3 state:R running task stack: 0 pid: 324 ppid: 2 flags:0x00004008
kern.info: [ 2.424073] Workqueue: events work_for_cpu_fn
kern.info: [ 2.424078] Call Trace:
kern.info: [ 2.424080] <TASK>
kern.info: [ 2.424082] ? __slab_free+0xa0/0x2d0
kern.info: [ 2.424087] ? radeon_ttm_tt_create+0x36/0xa0 [radeon]
kern.info: [ 2.424155] ? put_cpu_partial+0x6d/0xb0
kern.info: [ 2.424158] ? ttm_resource_free+0x67/0x80 [ttm]
kern.info: [ 2.424164] ? kmem_cache_alloc_lru+0x1b4/0x3b0
kern.info: [ 2.424167] ? _raw_spin_unlock_irqrestore+0x20/0x40
kern.info: [ 2.424170] ? __wake_up_common_lock+0x8a/0xc0
kern.info: [ 2.424173] ? sysvec_apic_timer_interrupt+0xaf/0xd0
kern.info: [ 2.424177] ? sysvec_apic_timer_interrupt+0xaf/0xd0
kern.info: [ 2.424179] ? asm_sysvec_apic_timer_interrupt+0x16/0x20
kern.info: [ 2.424183] ? delay_tsc+0x4a/0xc0
kern.info: [ 2.424187] ? delay_tsc+0x42/0xc0
kern.info: [ 2.424190] ? rv770_set_uvd_clocks+0x27e/0x350 [radeon]
kern.info: [ 2.424255] ? uvd_v1_0_init+0x37/0x570 [radeon]
kern.info: [ 2.424317] ? rv770_startup+0xfce/0x1740 [radeon]
kern.info: [ 2.424383] ? rv770_init+0x259/0x2c0 [radeon]
kern.info: [ 2.424448] ? radeon_device_init+0x553/0xa10 [radeon]
kern.info: [ 2.424502] ? radeon_driver_load_kms+0xc8/0x260 [radeon]
kern.info: [ 2.424556] ? drm_dev_register+0xcc/0x1c0 [drm]
kern.info: [ 2.424572] ? radeon_pci_probe+0xc4/0x110 [radeon]
kern.info: [ 2.424626] ? local_pci_probe+0x45/0x80
kern.info: [ 2.424628] ? work_for_cpu_fn+0x16/0x20
kern.info: [ 2.424631] ? process_one_work+0x1e5/0x3b0
kern.info: [ 2.424634] ? worker_thread+0x1c4/0x3a0
kern.info: [ 2.424636] ? rescuer_thread+0x390/0x390
kern.info: [ 2.424639] ? kthread+0xe7/0x110
kern.info: [ 2.424641] ? kthread_complete_and_exit+0x20/0x20
kern.info: [ 2.424644] ? ret_from_fork+0x22/0x30
kern.info: [ 2.424647] </TASK>
```
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
(Only on x86_64 on the affected hardware.)
[ci skip]
prev parent reply other threads:[~2022-09-02 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 13:47 [PR PATCH] " mmnmnnmnmm
2022-09-02 15:33 ` sgn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220902153348.nj85lTLzooKQ9VKgzTuIz9_MnSF7WvIxpEs-nC0h438@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).