linux-kernel - Re: NMI hardlock stacktrace deadlock [was Re: Linux 5.2-rc5]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.1906212130230.5503@nanos.tec.linutronix.de>
Date:   Fri, 21 Jun 2019 21:33:36 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Chris Wilson <chris@...is-wilson.co.uk>
cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        Joerg Roedel <joro@...tes.org>
Subject: Re: NMI hardlock stacktrace deadlock [was Re: Linux 5.2-rc5]

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