From: Waiman Long <longman@redhat.com>
To: Qian Cai <cai@lca.pw>, Thomas Gleixner <tglx@linutronix.de>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Joel Fernandes (Google)" <joel@joelfernandes.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
rcu@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: Hard lockups due to "tick/common: Make tick_periodic() check for missing ticks"
Date: Thu, 19 Mar 2020 15:00:35 -0400 [thread overview]
Message-ID: <218eed57-27c8-12c0-6f5f-111874798c21@redhat.com> (raw)
In-Reply-To: <11BEA1A5-2E93-4E01-A05C-A6BA73A74CEB@lca.pw>
On 3/19/20 9:58 AM, Qian Cai wrote:
>
>> On Mar 6, 2020, at 10:33 PM, Qian Cai <cai@lca.pw> wrote:
>>
>>
>>
>>> On Mar 5, 2020, at 11:06 PM, Qian Cai <cai@lca.pw> wrote:
>>>
>> Using this config,
>>
>>> https://raw.githubusercontent.com/cailca/linux-mm/master/x86.config
>> Reverted the linux-next commit d441dceb5dce (“tick/common: Make tick_periodic() check for missing ticks”)
>> fixed the lockup that could easily happen during boot.
>
> Thomas or Stephen, can you back out this patch from linux-next while Waiman is getting to the bottom of it?
> I can still reproduce it as today.
I am fine for reverting the patch for now. I am still having some
trouble reproducing it and I have other tasks to work on right now. I
will get to the bottom of it and resubmit a new patch later on.
Cheers,
Longman
next prev parent reply other threads:[~2020-03-19 19:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 4:06 PROVE_RCU_LIST + /proc/lockdep warning Qian Cai
2020-03-07 3:33 ` Hard lockups due to "tick/common: Make tick_periodic() check for missing ticks" Qian Cai
2020-03-08 21:18 ` Waiman Long
2020-03-19 13:58 ` Qian Cai
2020-03-19 19:00 ` Waiman Long [this message]
2020-03-20 2:00 ` Stephen Rothwell
2020-03-20 11:50 ` Thomas Gleixner
2020-03-07 17:16 ` PROVE_RCU_LIST + /proc/lockdep warning Joel Fernandes
2020-03-09 1:40 ` Boqun Feng
2020-03-10 18:42 ` Qian Cai
2020-03-11 3:30 ` Boqun Feng
2020-03-11 13:24 ` Qian Cai
2020-03-12 0:48 ` Boqun Feng
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=218eed57-27c8-12c0-6f5f-111874798c21@redhat.com \
--to=longman@redhat.com \
--cc=cai@lca.pw \
--cc=fweisbec@gmail.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).