mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Qian Cai <cai@lca.pw>, Thomas Gleixner <tglx@linutronix.de>
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: Sun, 8 Mar 2020 17:18:21 -0400	[thread overview]
Message-ID: <68ef67a1-306f-ee87-14c8-14f8863a67a1@redhat.com> (raw)
In-Reply-To: <F95F95DE-77D9-4A1D-AA5C-CAC165F6B4C8@lca.pw>

On 3/6/20 10:33 PM, Qian Cai 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.
>
I will take a look at that and get back to you ASAP.

Thanks,
Longman


  reply	other threads:[~2020-03-08 21:18 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 [this message]
2020-03-19 13:58   ` Qian Cai
2020-03-19 19:00     ` Waiman Long
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=68ef67a1-306f-ee87-14c8-14f8863a67a1@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=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
all inboxes | Powered by JetHome®