From: Matthew Wilcox <willy@infradead.org>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Chris Clayton <chris2553@googlemail.com>,
Chris Rankin <rankincj@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
rcu@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: linux-5.13.2: warning from kernel/rcu/tree_plugin.h:359
Date: Sun, 18 Jul 2021 22:22:21 +0100 [thread overview]
Message-ID: <YPSbjXrBYsRZagAv@casper.infradead.org> (raw)
In-Reply-To: <6698965.kvI7vG0SvZ@natalenko.name>
On Sun, Jul 18, 2021 at 11:03:51PM +0200, Oleksandr Natalenko wrote:
> + stable@vger.kernel.org
>
> On neděle 18. července 2021 23:01:24 CEST Oleksandr Natalenko wrote:
> > Hello.
> >
> > On sobota 17. července 2021 22:22:08 CEST Chris Clayton wrote:
> > > I checked the output from dmesg yesterday and found the following warning:
> > >
> > > [Fri Jul 16 09:15:29 2021] ------------[ cut here ]------------
> > > [Fri Jul 16 09:15:29 2021] WARNING: CPU: 11 PID: 2701 at
> > > kernel/rcu/tree_plugin.h:359 rcu_note_context_switch+0x37/0x3d0 [Fri Jul
Could you run ./scripts/faddr2line vmlinux rcu_note_context_switch+0x37/0x3d0
> > > [Fri Jul 16 09:15:29 2021] Call Trace:
> > > [Fri Jul 16 09:15:29 2021] __schedule+0x86/0x810
> > > [Fri Jul 16 09:15:29 2021] schedule+0x40/0xe0
> > > [Fri Jul 16 09:15:29 2021] io_schedule+0x3d/0x60
> > > [Fri Jul 16 09:15:29 2021] wait_on_page_bit_common+0x129/0x390
> > > [Fri Jul 16 09:15:29 2021] ? __filemap_set_wb_err+0x10/0x10
> > > [Fri Jul 16 09:15:29 2021] __lock_page_or_retry+0x13f/0x1d0
> > > [Fri Jul 16 09:15:29 2021] do_swap_page+0x335/0x5b0
> > > [Fri Jul 16 09:15:29 2021] __handle_mm_fault+0x444/0xb20
> > > [Fri Jul 16 09:15:29 2021] handle_mm_fault+0x5c/0x170
You were handling a page fault at the time. The page you wanted was
on swap and this warning fired as a result of waiting for the page
to come back in from swap. There are a number of warnings in that
function, so it'd be good to track down exactly which one it is.
next prev parent reply other threads:[~2021-07-18 21:22 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 20:22 linux-5.13.2: warning from kernel/rcu/tree_plugin.h:359 Chris Clayton
2021-07-18 6:18 ` Fwd: " Chris Clayton
2021-07-18 21:01 ` Oleksandr Natalenko
2021-07-18 21:03 ` Oleksandr Natalenko
2021-07-18 21:22 ` Matthew Wilcox [this message]
2021-07-18 21:36 ` Chris Clayton
2021-07-18 21:59 ` Paul E. McKenney
2021-07-18 22:51 ` Matthew Wilcox
2021-07-19 1:53 ` Paul E. McKenney
2021-07-19 2:24 ` Zhouyi Zhou
2021-07-19 2:24 ` Zhouyi Zhou
2021-07-19 2:27 ` Zhouyi Zhou
2021-07-19 2:27 ` Zhouyi Zhou
2021-07-19 2:43 ` Matthew Wilcox
2021-07-19 2:59 ` Zhouyi Zhou
2021-07-19 2:59 ` Zhouyi Zhou
2021-07-19 10:14 ` Boqun Feng
2021-07-19 11:12 ` Miaohe Lin
2021-07-19 11:17 ` Oleksandr Natalenko
2021-07-19 11:22 ` Matthew Wilcox
2021-07-19 11:50 ` Miaohe Lin
2021-07-19 11:59 ` Oleksandr Natalenko
2021-07-19 12:08 ` Miaohe Lin
2021-07-19 12:12 ` Oleksandr Natalenko
2021-07-19 12:16 ` Matthew Wilcox
2021-07-19 12:23 ` Oleksandr Natalenko
2021-07-19 16:47 ` Zhouyi Zhou
2021-07-19 16:47 ` Zhouyi Zhou
2021-07-19 16:56 ` Zhouyi Zhou
2021-07-19 16:56 ` Zhouyi Zhou
2021-07-22 7:30 ` Chris Clayton
2021-07-22 8:57 ` Zhouyi Zhou
2021-07-22 8:57 ` Zhouyi Zhou
2021-07-22 12:36 ` Matthew Wilcox
2021-07-22 13:26 ` Greg KH
2021-07-22 14:00 ` Greg KH
2021-07-23 1:51 ` Miaohe Lin
2021-07-23 7:02 ` Greg KH
2021-07-23 7:13 ` Miaohe Lin
2021-07-22 17:44 ` Zhouyi Zhou
2021-07-22 17:44 ` Zhouyi Zhou
2021-07-22 14:05 ` Paul E. McKenney
2021-07-19 12:17 ` Miaohe Lin
2021-07-19 7:32 ` Chris Clayton
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=YPSbjXrBYsRZagAv@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=chris2553@googlemail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=oleksandr@natalenko.name \
--cc=paulmck@kernel.org \
--cc=rankincj@gmail.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.