From: Peter Zijlstra <peterz@infradead.org>
To: Li Zhijian <zhijianx.li@intel.com>
Cc: mingo@redhat.com, will@kernel.org, longman@redhat.com,
boqun.feng@gmail.com, open list <linux-kernel@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"lkp@lists.01.org" <lkp@lists.01.org>
Subject: Re: ww_mutex.sh hangs since v5.16-rc1
Date: Thu, 2 Dec 2021 23:57:12 +0100 [thread overview]
Message-ID: <20211202225712.GG16608@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <895ef450-4fb3-5d29-a6ad-790657106a5a@intel.com>
On Wed, Dec 01, 2021 at 09:26:18AM +0800, Li Zhijian wrote:
> Hi Folks
>
>
> LKP/0Day found that ww_mutex.sh cannot complete since v5.16-rc1, but
> I'm pretty sorry that we failed to bisect the FBC, instead, the bisection pointed
> to a/below merge commit(91e1c99e17) finally.
>
> Due to this hang, other tests in the same group are also blocked in 0Day, we
> hope we can fix this hang ASAP.
>
> So if you have any idea about this, or need more debug information, feel free to let me know :)
>
> BTW, ww_mutex.sh was failed in v5.15 without hang, and looks it cannot reproduce on a vm.
On real hardware:
root@ivb-ep:/usr/src/linux-2.6/tools/testing/selftests/locking# uname -a
Linux ivb-ep 5.16.0-rc3-00284-g68601c558556 #1 SMP PREEMPT Thu Dec 2 23:03:29 CET 2021 x86_64 GNU/Linux
root@ivb-ep:/usr/src/linux-2.6/tools/testing/selftests/locking# ./ww_mutex.sh
locking/ww_mutex: ok
[ 1907.907801] Beginning ww mutex selftests
[ 1915.700077] All ww mutex selftests passed
What else do I try?
next prev parent reply other threads:[~2021-12-02 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 1:26 ww_mutex.sh hangs since v5.16-rc1 Li Zhijian
2021-12-02 22:57 ` Peter Zijlstra [this message]
2021-12-07 4:27 ` Li Zhijian
2023-07-07 20:23 ` John Stultz
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=20211202225712.GG16608@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=will@kernel.org \
--cc=zhijianx.li@intel.com \
/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