linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@windriver.com>
To: rt-users <linux-rt-users@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: [RT] hit recently-fixed PREEMPT_RT CFS-bandwidth timer locking issue in the wild
Date: Fri, 26 Jul 2019 13:36:51 -0600	[thread overview]
Message-ID: <feae6d57-e8a9-36cf-56c5-e9334d7df303@windriver.com> (raw)

Hi all,

I thought people might be interested to hear that we recently hit the 
bug fixed by git commit c0ad4aa4d8 on multiple lab systems running the 
RHEL 7 "kernel-rt" kernel.  (But I think other versions are at risk as 
well.)

Interestingly, when the bug hit the system just hung completely. Nothing 
was emitted on netconsole or serial console, neither the hung task timer 
nor the NMI watchdog triggered, CONFIG_DEBUG_SPINLOCK didn't output 
anything, and magic sysrq didn't work on the serial console.  As you can 
imagine this was a bit frustrating.  I was finally able to cause a panic 
by sending an NMI from the BMC and that allowed kdump to store the core 
file so I could get stack traces.

Given how annoying it was to debug, I'd recommend backporting this fix 
as far back as it applies.  HRTIMER_MODE_SOFT was introduced in mainline 
in 4.16, but at least in the RHEL7 kernel-rt package (and I think in the 
vanilla PREEMPT_RT patches as well) hrtimers are run by default in 
softirq context and so the fix might apply to all supported PREEMPT_RT 
versions.

Chris

                 reply	other threads:[~2019-07-26 19:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=feae6d57-e8a9-36cf-56c5-e9334d7df303@windriver.com \
    --to=chris.friesen@windriver.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;
as well as URLs for NNTP newsgroup(s).