From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: fupan li <lifupan@gmail.com>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: RCU stall and the system boot hang
Date: Tue, 1 Dec 2015 11:55:37 -0800 [thread overview]
Message-ID: <20151201195537.GA13568@linux.vnet.ibm.com> (raw)
In-Reply-To: <20151130171918.GR26643@linux.vnet.ibm.com>
On Mon, Nov 30, 2015 at 09:19:18AM -0800, Paul E. McKenney wrote:
> On Mon, Nov 30, 2015 at 02:54:13PM +0800, fupan li wrote:
[ . . . ]
> > No, just a normal boot, and these stalls were happened before
> > systemd services running.
>
> Interesting. My testing show v4.1 being OK, with the first issues showing
> up somewhere between v4.1 and v4.2. Or at least v4.1 is reliable enough
> that is passes 42 hours of focused rcutorture testing, where v4.2 tends
> to fail in under two hours. And it seems to happen only on multisocket
> systems -- I seem to be able to hammer as hard as I want on my four-core
> (eight hardware thread) laptop without an issue.
And I take it back. After beating on it for the better part of a week,
I did get one failure on my single-socket laptop.
So maybe I need to make my rcutorture scripts force tests to cross socket
boundaries where possible...
Thanx, Paul
prev parent reply other threads:[~2015-12-01 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADUONQMsaiTyFPRxm8TfB4ec__XjXUCAhjxZHG8Mz=cExvz5Sw@mail.gmail.com>
2015-11-27 16:28 ` RCU stall and the system boot hang Paul E. McKenney
[not found] ` <CADUONQN3yFyFQ8pfkS9u7UAYNjQym8f1JAGapeR9YV4E=7_xXg@mail.gmail.com>
2015-11-28 14:53 ` Paul E. McKenney
[not found] ` <CADUONQOYtHvwzoWNW33=WXy5r-UBTqs_vKdeRUgg=YEqq1meWg@mail.gmail.com>
2015-11-29 6:05 ` Paul E. McKenney
[not found] ` <CADUONQOc1x_gboKOmigwUX9GrZhukH4KkN1SXRGyjwvXfoGqTg@mail.gmail.com>
2015-11-30 17:19 ` Paul E. McKenney
2015-12-01 19:55 ` Paul E. McKenney [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=20151201195537.GA13568@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=lifupan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox