From: Andrea Righi <andrea.righi@canonical.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Marco Elver <elver@google.com>,
Alexander Potapenko <glider@google.com>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: BUG: soft lockup in __kmalloc_node() with KFENCE enabled
Date: Mon, 11 Oct 2021 11:52:59 +0200 [thread overview]
Message-ID: <YWQJe1ccZ72FZkLB@arighi-desktop> (raw)
In-Reply-To: <YWQCknwPcGlOBfUi@arighi-desktop>
On Mon, Oct 11, 2021 at 11:23:32AM +0200, Andrea Righi wrote:
...
> > You seem to use the default 20s stall timeout. FWIW syzbot uses 160
> > secs timeout for TCG emulation to avoid false positive warnings:
> > https://github.com/google/syzkaller/blob/838e7e2cd9228583ca33c49a39aea4d863d3e36d/dashboard/config/linux/upstream-arm64-kasan.config#L509
> > There are a number of other timeouts raised as well, some as high as
> > 420 seconds.
>
> I see, I'll try with these settings and see if I can still hit the soft
> lockup messages.
Still getting soft lockup messages even with the new timeout settings:
[ 462.663766] watchdog: BUG: soft lockup - CPU#2 stuck for 430s! [systemd-udevd:168]
[ 462.755758] watchdog: BUG: soft lockup - CPU#3 stuck for 430s! [systemd-udevd:171]
[ 924.663765] watchdog: BUG: soft lockup - CPU#2 stuck for 861s! [systemd-udevd:168]
[ 924.755767] watchdog: BUG: soft lockup - CPU#3 stuck for 861s! [systemd-udevd:171]
-Andrea
next prev parent reply other threads:[~2021-10-11 9:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 13:53 Andrea Righi
2021-10-11 6:00 ` Marco Elver
2021-10-11 6:32 ` Andrea Righi
2021-10-11 6:48 ` Marco Elver
2021-10-11 7:10 ` Andrea Righi
2021-10-11 7:19 ` Dmitry Vyukov
2021-10-11 9:23 ` Andrea Righi
2021-10-11 9:52 ` Andrea Righi [this message]
2021-10-11 10:03 ` Marco Elver
2021-10-11 14:42 ` Andrea Righi
2021-10-11 15:00 ` Dmitry Vyukov
2021-10-11 15:11 ` Andrea Righi
2021-10-11 15:16 ` Dmitry Vyukov
2021-10-20 6:00 ` Marco Elver
2021-10-20 6:11 ` Andrea Righi
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=YWQJe1ccZ72FZkLB@arighi-desktop \
--to=andrea.righi@canonical.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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