From: Steve McIntyre <steve@einval.com>
To: Jann Horn <jannh@google.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
John Johansen <john.johansen@canonical.com>,
Sasha Levin <sashal@kernel.org>, stable <stable@vger.kernel.org>,
963493@bugs.debian.org
Subject: Re: Repeatable hard lockup running strace testsuite on 4.19.98+ onwards
Date: Fri, 26 Jun 2020 18:52:01 +0100 [thread overview]
Message-ID: <20200626175201.GA9110@unset.einval.com> (raw)
In-Reply-To: <20200626165000.GB2950@unset.einval.com>
[-- Attachment #1: Type: text/plain, Size: 1999 bytes --]
Hi again,
On Fri, Jun 26, 2020 at 05:50:00PM +0100, Steve McIntyre wrote:
>On Fri, Jun 26, 2020 at 04:25:59PM +0200, Jann Horn wrote:
>>On Fri, Jun 26, 2020 at 3:41 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>>> On Fri, Jun 26, 2020 at 12:35:58PM +0100, Steve McIntyre wrote:
>
>...
>
>>> > Considering I'm running strace build tests to provoke this bug,
>>> > finding the failure in a commit talking about ptrace changes does look
>>> > very suspicious...!
>>> >
>>> > Annoyingly, I can't reproduce this on my disparate other machines
>>> > here, suggesting it's maybe(?) timing related.
>>
>>Does "hard lockup" mean that the HARDLOCKUP_DETECTOR infrastructure
>>prints a warning to dmesg? If so, can you share that warning?
>
>I mean the machine locks hard - X stops updating, the mouse/keyboard
>stop responding. No pings, etc. When I reboot, there's nothing in the
>logs.
>
>>If you don't have any way to see console output, and you don't have a
>>working serial console setup or such, you may want to try re-running
>>those tests while the kernel is booted with netconsole enabled to log
>>to a different machine over UDP (see
>>https://www.kernel.org/doc/Documentation/networking/netconsole.txt).
>
>ACK, will try that now for you.
>
>>You may want to try setting the sysctl kernel.sysrq=1 , then when the
>>system has locked up, press ALT+PRINT+L (to generate stack traces for
>>all active CPUs from NMI context), and maybe also ALT+PRINT+T and
>>ALT+PRINT+W (to collect more information about active tasks).
>
>Nod.
>
>>(If you share stack traces from these things with us, it would be
>>helpful if you could run them through scripts/decode_stacktrace.pl
>>from the kernel tree first, to add line number information.)
>
>ACK.
Output passed through scripts/decode_stacktrace.sh attached.
Just about to try John's suggestion next.
--
Steve McIntyre, Cambridge, UK. steve@einval.com
Dance like no one's watching. Encrypt like everyone is.
- @torproject
[-- Attachment #2: tack.log.decoded.gz --]
[-- Type: application/gzip, Size: 32484 bytes --]
next prev parent reply other threads:[~2020-06-26 17:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 11:35 Repeatable hard lockup running strace testsuite on 4.19.98+ onwards Steve McIntyre
2020-06-26 13:41 ` Greg KH
2020-06-26 13:45 ` Steve McIntyre
2020-06-26 15:20 ` Steve McIntyre
2020-06-26 14:25 ` Jann Horn
2020-06-26 16:50 ` Steve McIntyre
2020-06-26 17:29 ` John Johansen
2020-06-26 19:01 ` Steve McIntyre
2020-06-26 19:57 ` Sasha Levin
2020-06-26 17:52 ` Steve McIntyre [this message]
2020-06-26 18:27 ` Jann Horn
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=20200626175201.GA9110@unset.einval.com \
--to=steve@einval.com \
--cc=963493@bugs.debian.org \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=john.johansen@canonical.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.