From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Sasha Levin <levinsasha928@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>,
alexander.levin@verizon.com, pmladek@suse.com,
sergey.senozhatsky@gmail.com, rostedt@goodmis.org
Subject: Re: sched: serial port lockdep warning when offlining CPUs
Date: Thu, 28 Sep 2017 19:30:32 +0900 [thread overview]
Message-ID: <20170928103032.GA2380@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20170928093847.zgcgvxb7ajiaywbr@hirez.programming.kicks-ass.net>
Hi all,
Peter, thanks for Cc-ing.
On (09/28/17 11:38), Peter Zijlstra wrote:
> On Thu, Sep 28, 2017 at 02:19:46AM -0700, Sasha Levin wrote:
> > Hi all,
> >
> > I seem to be hitting the following warning when offlining CPUs on the
> > latest -next kernel:
> >
> > [289683102.607076] Unregister pv shared memory for cpu 8
> > [289683102.622922] select_fallback_rq: 3 callbacks suppressed
>
> This is because you hit a printk() from the scheduler, that's known
> broken (along with the rest of printk).
>
> You forgot to actually include that printk() though I suspect it reads
> like:
>
> "process %d (%s) no longer affine to cpu%d\n"
>
> Now that uses printk_deferred() which _should_ work lots better, but
> clearly the printk() stuff went wobbly again.
>
> > [289683102.626292] vprintk_emit (kernel/printk/printk.c:1876)
> > [289683102.626294] vprintk_default (kernel/printk/printk.c:1918)
> > [289683102.626295] vprintk_func (kernel/printk/printk_safe.c:382)
> > [289683102.626297] printk (kernel/printk/printk.c:1943)
> > [289683102.626299] ? show_regs_print_info (kernel/printk/printk.c:1943)
> > [289683102.626301] ? lock_acquire (kernel/locking/lockdep.c:4004)
> > [289683102.626306] ___ratelimit (lib/ratelimit.c:52)
> > [289683102.626309] __printk_ratelimit (kernel/printk/printk.c:2874)
> > [289683102.626311] select_fallback_rq (kernel/sched/core.c:1525 (discriminator 1))
> > [289683102.626313] sched_cpu_dying (kernel/sched/core.c:5500 kernel/sched/core.c:5687)
>
> Also, could you pretty please not line wrap logs?
I think it's
if (p->mm && printk_ratelimit())
which calls int ___ratelimit(), which ends up doing
pr_warn("%s: %d callbacks suppressed\n", func, rs->missed);
which is a "normal" printk from within the scheduler.
out of curiosity, will the following fix the warning
---
lib/ratelimit.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/ratelimit.c b/lib/ratelimit.c
index 08f8043cac61..bddc55834c2e 100644
--- a/lib/ratelimit.c
+++ b/lib/ratelimit.c
@@ -48,7 +48,8 @@ int ___ratelimit(struct ratelimit_state *rs, const char *func)
if (time_is_before_jiffies(rs->begin + rs->interval)) {
if (rs->missed) {
if (!(rs->flags & RATELIMIT_MSG_ON_RELEASE)) {
- pr_warn("%s: %d callbacks suppressed\n", func, rs->missed);
+ printk_deferred(KERN_WARN "%s: %d callbacks suppressed\n",
+ func, rs->missed);
rs->missed = 0;
}
}
next prev parent reply other threads:[~2017-09-28 10:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 9:19 Sasha Levin
2017-09-28 9:38 ` Peter Zijlstra
2017-09-28 10:30 ` Sergey Senozhatsky [this message]
2017-09-28 11:36 ` Sergey Senozhatsky
2017-09-28 11:45 ` Levin, Alexander (Sasha Levin)
2017-09-28 11:55 ` Sergey Senozhatsky
2017-09-28 12:05 ` Peter Zijlstra
2017-09-28 12:07 ` Peter Zijlstra
2017-09-28 12:15 ` Sergey Senozhatsky
2017-09-28 12:28 ` Peter Zijlstra
2017-09-28 11:47 ` Peter Zijlstra
2017-09-28 11:51 ` Sergey Senozhatsky
2017-09-28 11:04 ` Levin, Alexander (Sasha Levin)
2017-09-28 11:13 ` Sergey Senozhatsky
2017-09-28 11:38 ` Peter Zijlstra
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=20170928103032.GA2380@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky.work@gmail.com \
--cc=alexander.levin@verizon.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®