mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Joerg Roedel <joro@8bytes.org>
Subject: Re: NMI hardlock stacktrace deadlock [was Re: Linux 5.2-rc5]
Date: Fri, 21 Jun 2019 21:33:36 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1906212130230.5503@nanos.tec.linutronix.de> (raw)
In-Reply-To: <156114224132.2401.13297188928702045223@skylake-alporthouse-com>

On Fri, 21 Jun 2019, Chris Wilson wrote:

> Quoting Thomas Gleixner (2019-06-21 16:30:52)
> > Chris, do you have the actual NMI lockup detector splats somewhere?
> 
> Sorry, I'm having a hard time reproducing this at will now. The test
> case depends on the right timing of the wrong event to cause the GPU to
> hang.
> 
> From memory, I got the
> 	"Watchdog detected hard LOCKUP on cpu foo"
> followed by the register dump and then nothing. At which point I had to
> power cycle the machine.

Hmm. Do you have a serial log of that incident?

Thanks,

	tglx

  reply	other threads:[~2019-06-21 19:33 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
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 [this message]
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=alpine.DEB.2.21.1906212130230.5503@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=chris@chris-wilson.co.uk \
    --cc=joro@8bytes.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®