From: James Feeney <james@nurealm.net>
To: linux-smp@vger.kernel.org
Subject: Re: linux 5.12 - fails to boot - soft lockup - CPU#0 stuck for 23s! - RIP smp_call_function_single
Date: Mon, 3 May 2021 03:44:10 -0600 [thread overview]
Message-ID: <3ee6e9b5-f325-82f2-28bc-c41a9e93394f@nurealm.net> (raw)
$ git bisect bad
7c70f3a7488d2fa62d32849d138bf2b8420fe788 is the first bad commit
commit 7c70f3a7488d2fa62d32849d138bf2b8420fe788
Merge: 20bf195e9391 4d12b7275386
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Mon Feb 22 13:29:55 2021 -0800
Merge tag 'nfsd-5.12-1' of git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux
Pull more nfsd updates from Chuck Lever:
"Here are a few additional NFSD commits for the merge window:
Optimization:
- Cork the socket while there are queued replies
Fixes:
- DRC shutdown ordering
- svc_rdma_accept() lockdep splat"
* tag 'nfsd-5.12-1' of git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux:
SUNRPC: Further clean up svc_tcp_sendmsg()
SUNRPC: Remove redundant socket flags from svc_tcp_sendmsg()
SUNRPC: Use TCP_CORK to optimise send performance on the server
svcrdma: Hold private mutex while invoking rdma_accept()
nfsd: register pernet ops last, unregister first
fs/nfsd/nfsctl.c | 14 ++++++-------
include/linux/sunrpc/svcsock.h | 2 ++
net/sunrpc/svcsock.c | 35 ++++++++++++++++----------------
net/sunrpc/xprtrdma/svc_rdma_transport.c | 6 +++---
4 files changed, 29 insertions(+), 28 deletions(-)
--------------
There is a small chance that this bisect is not precise, because sometimes the system can boot to a temporarily working state, then lock-up after a short time. I did not test every successful initial boot extensively.
This particular commit does not produce the same "watchdog: BUG: soft lockup" log message. Instead, after sometimes - mostly not - booting to an Xorg display, the system just completely freezes, with not so much as the system log still working.
next reply other threads:[~2021-05-03 9:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 9:44 James Feeney [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-17 8:13 linux 5.12 - fails to boot - soft lockup - CPU#0 stuck for 23s! - RIP smp_call_function_single James Feeney
2021-05-17 8:32 ` Borislav Petkov
2021-05-19 3:58 ` James Feeney
2021-05-19 11:12 ` Borislav Petkov
2021-05-19 20:03 ` James Feeney
2021-05-19 21:18 ` Borislav Petkov
2021-05-20 3:12 ` James Feeney
2021-05-20 9:21 ` Borislav Petkov
2021-05-21 22:11 ` James Feeney
2021-05-22 9:06 ` Borislav Petkov
2021-05-22 23:28 ` James Feeney
2021-05-23 17:05 ` Borislav Petkov
2021-05-23 23:02 ` James Feeney
2021-05-24 7:51 ` Borislav Petkov
2021-05-25 4:02 ` James Feeney
2021-05-14 18:39 James Feeney
2021-05-17 12:27 ` Christoph Hellwig
2021-05-19 15:50 ` James Feeney
2021-04-30 17:04 James Feeney
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=3ee6e9b5-f325-82f2-28bc-c41a9e93394f@nurealm.net \
--to=james@nurealm.net \
--cc=linux-smp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).