From: "Jorge Ramirez-Ortiz, Foundries" <jorge@foundries.io>
To: Zhouyi Zhou <zhouzhouyi@gmail.com>
Cc: "Jorge Ramirez-Ortiz, Foundries" <jorge@foundries.io>,
paulmck@kernel.org, Josh Triplett <josh@joshtriplett.org>,
rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
"Joel Fernandes, Google" <joel@joelfernandes.org>,
rcu <rcu@vger.kernel.org>,
soc@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: rcu_preempt detected stalls
Date: Wed, 1 Sep 2021 10:23:21 +0200 [thread overview]
Message-ID: <20210901082321.GA6551@trex> (raw)
In-Reply-To: <CAABZP2zg8c_gkm4+h4-mPCv_uDf5-iJFHEExCDFoES0jmBeuKw@mail.gmail.com>
On 01/09/21, Zhouyi Zhou wrote:
> Hi,
>
> I perform following two new rounds of experiments:
>
>
> Test environment (x86_64 debian10 virtual machine: kvm -cpu host -smp
> 8 -hda ./debian10.qcow2 -m 4096 -net
> user,hostfwd=tcp::5556-:22,hostfwd=tcp::5555-:19 -net nic,model=e1000
> -vnc :30)
>
> 1. CONFIG_RCU_BOOST=y
> 1.1 as root, run #stress-ng --sequential 100 --class scheduler -t 5m --times
> 1.2 as regular user at the same time, run $stress-ng --sequential 100
> --class scheduler -t 5m --times
>
> System begin OOM kill after 6 minutes:
> 31 19:41:12 debian kernel: [ 847.171884] task:kworker/1:0 state:D
> stack: 0 pid: 1634 ppid: 2 flag\
> s:0x00004000
> Aug 31 19:41:12 debian kernel: [ 847.171890] Workqueue: ipv6_addrconf
> addrconf_verify_work
> Aug 31 19:41:12 debian kernel: [ 847.171897] Call Trace:
> Aug 31 19:41:12 debian kernel: [ 847.171903] __schedule+0x368/0xa40
> Aug 31 19:41:12 debian kernel: [ 847.171915] schedule+0x44/0xe0
> Aug 31 19:41:12 debian kernel: [ 847.171921]
> schedule_preempt_disabled+0x14/0x20
> Aug 31 19:41:12 debian kernel: [ 847.171924] __mutex_lock+0x4b1/0xa10
> Aug 31 19:41:12 debian kernel: [ 847.171935] ? addrconf_verify_work+0xa/0x20
> Aug 31 19:41:12 debian kernel: [ 847.171948] ? addrconf_verify_work+0xa/0x20
> Aug 31 19:41:12 debian kernel: [ 847.171951] addrconf_verify_work+0xa/0x20
> Aug 31 19:41:12 debian kernel: [ 847.171955] process_one_work+0x1fa/0x5b0
> Aug 31 19:41:12 debian kernel: [ 847.171967] worker_thread+0x64/0x3d0
> Aug 31 19:41:12 debian kernel: [ 847.171974] ? process_one_work+0x5b0/0x5b0
> Aug 31 19:41:12 debian kernel: [ 847.171978] kthread+0x131/0x180
> Aug 31 19:41:12 debian kernel: [ 847.171982] ? set_kthread_struct+0x40/0x40
> Aug 31 19:41:12 debian kernel: [ 847.171989] ret_from_fork+0x1f/0x30
> Aug 31 19:41:12 debian kernel: [ 847.176007]
> Aug 31 19:41:12 debian kernel: [ 847.176007] Showing all locks held
> in the system:
> Aug 31 19:41:12 debian kernel: [ 847.176016] 1 lock held by khungtaskd/56:
> Aug 31 19:41:12 debian kernel: [ 847.176018] #0: ffffffff82918b60
> (rcu_read_lock){....}-{1:2}, at: debug_show_a\
> ll_locks+0xe/0x1a0
>
> 2. # CONFIG_RCU_BOOST is not set
> 2.1 as root, run #stress-ng --sequential 100 --class scheduler -t 5m --times
> 2.2 as regular user at the same time, run $stress-ng --sequential 100
> --class scheduler -t 5m --times
> System begin OOM kill after 6 minutes:
> The system is so dead, that I can't save the backtrace to file nor did
> kernel has a chance to save the log to /var/log/messages
>
all,
Thanks for testing on x86. we can also reproduce on qemu arm64. So I
think it will point out to the stress-ng test itself; I will debug it
early next week - didnt expect so much support so fast TBH, it took me
by surprise - and will report then (thanks again)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-09-01 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 15:21 rcu_preempt detected stalls Jorge Ramirez-Ortiz, Foundries
2021-08-31 15:53 ` Paul E. McKenney
2021-08-31 17:01 ` Zhouyi Zhou
2021-08-31 17:11 ` Zhouyi Zhou
2021-09-01 1:03 ` Zhouyi Zhou
[not found] ` <2712e554-2058-d3c3-72ae-cca7562a2ec7@codeaurora.org>
2021-09-01 6:47 ` Zhouyi Zhou
2021-09-01 8:23 ` Jorge Ramirez-Ortiz, Foundries [this message]
2021-09-01 9:17 ` Zhouyi Zhou
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=20210901082321.GA6551@trex \
--to=jorge@foundries.io \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=soc@kernel.org \
--cc=zhouzhouyi@gmail.com \
/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