From: Marc Herbert <Marc.Herbert@linux.intel.com>
To: Itaru Kitayama <itaru.kitayama@linux.dev>,
Dave Jiang <dave.jiang@intel.com>
Cc: linux-cxl@vger.kernel.org
Subject: Re: ndctl cxl test suite fails in arm64 QEMU
Date: Fri, 28 Feb 2025 16:27:36 -0800 [thread overview]
Message-ID: <6c3c85c1-7bf1-4039-aa72-2a0086c22865@linux.intel.com> (raw)
In-Reply-To: <98DAF41D-01E0-4594-B8C9-D8FF046FA19C@linux.dev>
On 2025-02-26 14:04, Itaru Kitayama wrote:
>> There's a known lockdep false positive that can trigger and cause cxl_test to fail. Does the kernel OOPS go away once you disable lockdep?
>
> Instead of disabling lockdep, pulling cxl next this morning, so far made the spurious error go away.
I think that's just luck. I've also seen this lockdep test failure
coming and going (in QEMU) depending on configuration changes, kernel
commit, phase of the moon and weather of the day. There's clearly a race
somewhere (whether it's a false or true positive) and in my experience
the only reliable way to silence this message has been to turn off
lockdep etc. in .config.
Maybe the fancy new concurrency-fuzz-scheduler could help reproduce?
https://lwn.net/Articles/1007689/ It sounds really cool. It could also
wake up too many zombie races and meltdown the whole system :-D
next prev parent reply other threads:[~2025-03-01 0:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 4:09 ndctl cxl test suite fails in arm64 QEMU Itaru Kitayama
2025-02-25 17:08 ` Marc Herbert
2025-02-25 22:37 ` Itaru Kitayama
2025-02-25 22:48 ` Alison Schofield
2025-02-25 23:53 ` Itaru Kitayama
2025-02-26 18:45 ` Alison Schofield
2025-02-26 22:07 ` Itaru Kitayama
2025-02-27 0:44 ` Itaru Kitayama
2025-02-27 5:31 ` Itaru Kitayama
2025-02-26 19:30 ` Dave Jiang
2025-02-26 22:04 ` Itaru Kitayama
2025-03-01 0:27 ` Marc Herbert [this message]
2025-02-26 8:02 ` Itaru Kitayama
2025-02-25 22:40 ` Alison Schofield
2025-02-28 12:15 ` Itaru Kitayama
2025-02-28 14:34 ` Itaru Kitayama
2025-03-07 1:44 ` Itaru Kitayama
2025-03-13 9:11 ` Jonathan Cameron
2025-03-25 10:14 ` Itaru Kitayama
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=6c3c85c1-7bf1-4039-aa72-2a0086c22865@linux.intel.com \
--to=marc.herbert@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=itaru.kitayama@linux.dev \
--cc=linux-cxl@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