linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: NMI hardlock stacktrace deadlock [was Re: Linux 5.2-rc5]
Date: Wed, 19 Jun 2019 20:19:38 +0100	[thread overview]
Message-ID: <156097197830.664.13418742301997062555@skylake-alporthouse-com> (raw)
In-Reply-To: <CAHk-=wjhJNKVfHgwd0QX_bq769sxfP4jvfy0dd-WtFMfdivMwg@mail.gmail.com>

Quoting Linus Torvalds (2019-06-19 19:49:37)
> On Wed, Jun 19, 2019 at 5:40 AM Chris Wilson <chris@chris-wilson.co.uk> wrote:
> >
> > I haven't bisected this, but with the merge of rc5 into our CI we
> > started hitting an issue that resulted in a oops and the NMI watchdog
> > firing as we dumped the ftrace.
> 
> Do you have the oops itself at all?

An example at
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6310/fi-kbl-x1275/dmesg0.log
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6310/fi-kbl-x1275/boot0.log

The bug causing the oops is clearly a driver problem. The rc5 fallout
just seems to be because of some shrinker changes affecting some object
reaping that were unfortunately still active. What perturbed the CI
team was the machine failed to panic & reboot.
-Chris

  reply	other threads:[~2019-06-19 19:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-16 19:06 Linux 5.2-rc5 Linus Torvalds
2019-06-19 12:39 ` NMI hardlock stacktrace deadlock [was Re: Linux 5.2-rc5] Chris Wilson
2019-06-19 18:49   ` Linus Torvalds
2019-06-19 19:19     ` Chris Wilson [this message]
2019-06-19 20:42       ` Linus Torvalds
2019-06-21 15:30         ` Thomas Gleixner
2019-06-21 18:37           ` Chris Wilson
2019-06-21 19:33             ` Thomas Gleixner
2019-06-21 19:56               ` Chris Wilson
2019-06-25  3:03         ` Josh Poimboeuf
2019-06-26 12:26           ` Steven Rostedt

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=156097197830.664.13418742301997062555@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).