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

From: Chris Wilson
Date: Wed Jun 19 2019 - 08:45:10 EST

Next message: Steve Twiss: "[PATCH V2] regulator: da9061/62: Adjust LDO voltage selection minimum value"
Previous message: Will Deacon: "Re: [PATCH RFC 11/14] arm64: Move the ASID allocator code in a separate file"
In reply to: Linus Torvalds: "Linux 5.2-rc5"
Next in thread: Linus Torvalds: "Re: NMI hardlock stacktrace deadlock [was Re: Linux 5.2-rc5]"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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

Next message: Steve Twiss: "[PATCH V2] regulator: da9061/62: Adjust LDO voltage selection minimum value"
Previous message: Will Deacon: "Re: [PATCH RFC 11/14] arm64: Move the ASID allocator code in a separate file"
In reply to: Linus Torvalds: "Linux 5.2-rc5"
Next in thread: Linus Torvalds: "Re: NMI hardlock stacktrace deadlock [was Re: Linux 5.2-rc5]"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]