From: Don Zickus <dzickus@redhat.com>
To: Zhang Zhen <zhenzhang.zhang@huawei.com>
Cc: paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
morgan.wang@huawei.com, josh@freedesktop.org,
dipankar@in.ibm.com
Subject: Re: RCU CPU stall console spews leads to soft lockup disabled is reasonable ?
Date: Tue, 20 Jan 2015 10:25:31 -0500 [thread overview]
Message-ID: <20150120152531.GR116159@redhat.com> (raw)
In-Reply-To: <54BDC6DF.6000602@huawei.com>
On Tue, Jan 20, 2015 at 11:09:19AM +0800, Zhang Zhen wrote:
>
> > Of course back then, touch_nmi_watchdog touched all cpus. So a problem
> > like this was masked. I believe this upstream commit 62572e29bc53, solved
> > the problem.
>
> Thanks for your suggestion.
>
> Commit 62572e29bc53 changed the semantics of touch_nmi_watchdog and make it
> only touch local cpu not every one.
> But watchdog_nmi_touch = true only guarantee no hard lockup check on this cpu.
>
> Commit 62572e29bc53 didn't changed the semantics of touch_softlockup_watchdog.
Ah, yes. I reviewed the commit to quickly yesterday. I thought
touch_softlockup_watchdog was called on every cpu and that commit changed
it to the local cpu. But that was incorrect.
> >
> > You can apply that commit and see if you if you get both RCU stall
> > messages _and_ softlockup messages. I believe that is what you were
> > expecting, correct?
> >
> Correct, i expect i can get both RCU stall messages _and_ softlockup messages.
> I applied that commit, and i only got RCU stall messages.
Hmm, I believe the act of printing to the console calls touch_nmi_watchdog
which calls touch_softlockup_watchdog. I think that is the problem there.
This may not cause other problems but what happens if you comment out the
'touch_softlockup_watchdog' from the touch_nmi_watchdog function like
below (based on latest upstream cb59670870)?
The idea is that console printing for that cpu won't reset the softlockup
detector. Again other bad things might happen and this patch may not be a
good final solution, but it can help give me a clue about what is going
on.
Cheers,
Don
diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index 70bf118..833c015 100644
--- a/kernel/watchdog.c
+++ b/kernel/watchdog.c
@@ -209,7 +209,7 @@ void touch_nmi_watchdog(void)
* going off.
*/
raw_cpu_write(watchdog_nmi_touch, true);
- touch_softlockup_watchdog();
+ //touch_softlockup_watchdog();
}
EXPORT_SYMBOL(touch_nmi_watchdog);
next prev parent reply other threads:[~2015-01-20 15:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 8:07 RCU CPU stall console spews leads to soft lockup disabled is reasonable ? Zhang Zhen
2015-01-19 8:42 ` Paul E. McKenney
2015-01-19 9:04 ` Zhang Zhen
2015-01-19 11:09 ` Paul E. McKenney
2015-01-20 3:17 ` Zhang Zhen
2015-01-20 3:33 ` Paul E. McKenney
2015-01-19 14:06 ` Don Zickus
2015-01-20 3:09 ` Zhang Zhen
2015-01-20 15:25 ` Don Zickus [this message]
2015-01-21 2:26 ` Zhang Zhen
2015-01-21 3:13 ` Zhang Zhen
2015-01-21 6:54 ` Zhang Zhen
2015-01-21 7:02 ` Paul E. McKenney
2015-01-21 7:25 ` Zhang Zhen
2015-01-21 9:05 ` Zhang Zhen
2015-01-21 10:16 ` Paul E. McKenney
2015-01-21 11:11 ` Zhang Zhen
2015-01-21 20:04 ` Paul E. McKenney
2015-01-21 15:10 ` Don Zickus
2015-01-21 20:06 ` Paul E. McKenney
2015-01-22 3:08 ` Zhang Zhen
2015-01-22 5:15 ` Paul E. McKenney
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=20150120152531.GR116159@redhat.com \
--to=dzickus@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=josh@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan.wang@huawei.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=zhenzhang.zhang@huawei.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;
as well as URLs for NNTP newsgroup(s).