Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp648592ybi;
        Wed, 19 Jun 2019 05:40:54 -0700 (PDT)
X-Google-Smtp-Source: APXvYqx2Xyv2N+MA5nH3qlhqu3viJXOSdGrvSHqioYxrLSbrZVq16asulM5c6JfIPYKmTgGZGZwU
X-Received: by 2002:a17:902:2ba7:: with SMTP id l36mr118104395plb.334.1560948054098;
        Wed, 19 Jun 2019 05:40:54 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1560948054; cv=none;
        d=google.com; s=arc-20160816;
        b=TIVq1iAzTzdFrAvNoxsBAUMH1vXRzLVpCmad0KND53YXoSb8qwCbPmEfUtgL3C/YSu
         yawUtFJByu8hiWDpFL+dp8KcnVD9axwpFlLPLasKWq+IuunGmVNtWTtYm35ScVee4KHm
         DVCfLXk4fH2V9TSkqbbrbrO1q9osW9o71nzot++iJy1J059LZAbLvU8DHALL+kAHfDpS
         4J9IAstIl6cw8J8B5NIbbleTK95UEQwD9R9UdQFjrRqtVPhwFYQwdg3KLfeCGMmL5aDn
         /L2z1TSNz09J/q+jcS4plpQCk2BOasRBicI4iDt7w4/hbeJKDKpqlEVTiG8YxzZVH32Y
         aTuw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:sender:date:subject:message-id:in-reply-to
         :references:to:user-agent:from:content-transfer-encoding
         :mime-version;
        bh=iOzp58h2UzqjxKcIWCZXNGfpdZTUh46VOXTaViLnUic=;
        b=g4ka60UnITef0CUb/vpQQLCfueML9/eZZ7Q5M/ddGQHMo1IMFugVR3PuHUfAsD4xZx
         EMH9g993pVTZVyfPHNuEpBZG38Tj1ZABItyqGqYUAt/thSYDJb9L9JL/YIvvOMwiSg4P
         9OcXXbvaxXLKH45k5VS5aNiz1iOaKPTq0vBZpxHiR3WH7546ys5/aMX7Arzgr5iFRqUq
         H0ooP3/dshqJwopA461mrF5FwZ/cnCCC77VEYhmmttKj3Eeb3rvAe05das0rn5zYo2At
         QMhOLhCCk1EW0uOC+YuIs7Mhjz4TJoElZGOFOInL3lCta3nTuQjZWHPyrNTiR3OSu53h
         UTEg==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67])
        by mx.google.com with ESMTP id m3si17183840pld.40.2019.06.19.05.40.39;
        Wed, 19 Jun 2019 05:40:54 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Authentication-Results: mx.google.com;
       spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1731915AbfFSMkC convert rfc822-to-8bit (ORCPT
        <rfc822;carmate383@gmail.com> + 99 others);
        Wed, 19 Jun 2019 08:40:02 -0400
Received: from mail.fireflyinternet.com ([109.228.58.192]:64033 "EHLO
        fireflyinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org
        with ESMTP id S1727314AbfFSMkC (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 19 Jun 2019 08:40:02 -0400
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=78.156.65.138;
Received: from localhost (unverified [78.156.65.138]) 
        by fireflyinternet.com (Firefly Internet (M1)) with ESMTP (TLS) id 16952903-1500050 
        for multiple; Wed, 19 Jun 2019 13:39:55 +0100
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8BIT
From:   Chris Wilson <chris@chris-wilson.co.uk>
User-Agent: alot/0.6
To:     Linus Torvalds <torvalds@linux-foundation.org>,
        Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
References: <CAHk-=whEQPvLpDbx+WR4Q4jf2FxXjf_zTX3uLy_6ZzHtgTV4LA@mail.gmail.com>
In-Reply-To: <CAHk-=whEQPvLpDbx+WR4Q4jf2FxXjf_zTX3uLy_6ZzHtgTV4LA@mail.gmail.com>
Message-ID: <156094799629.21217.4574572565333265288@skylake-alporthouse-com>
Subject: NMI hardlock stacktrace deadlock [was Re: Linux 5.2-rc5]
Date:   Wed, 19 Jun 2019 13:39:56 +0100
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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. This NMI watchdog locks up prior to the
backtraces being printed, preventing the machine from rebooting, and can
be avoided with hardlockup_all_cpu_backtrace=0. Running on arch/x86.
-Chris