From: Peter Zijlstra <peterz@infradead.org>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
vschneid@redhat.com
Subject: Re: 6.12;bisected;regression - psi: inconsistent task state warning appeared in kernel log between 2e0199df252 and 54a58a787791 commits
Date: Tue, 15 Oct 2024 21:55:48 +0200 [thread overview]
Message-ID: <20241015195548.GV17263@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CABXGCsPprMWjj=u_kJkLcQOQcR3M3iF797zsmSqQin8UUkkppg@mail.gmail.com>
On Tue, Oct 15, 2024 at 04:50:00PM +0500, Mikhail Gavrilov wrote:
> Hi,
> I spotted a new warning message when kernel
> 6.12.0-0.rc0.20240920gitbaeb9a7d8b60.7.fc42.x86_64+debug manded on my
> machine.
Should be fixed in tip/sched/urgent -- also in next.
prev parent reply other threads:[~2024-10-15 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 11:50 6.12;bisected;regression - psi: inconsistent task state warning appeared in kernel log between 2e0199df252 and 54a58a787791 commits Mikhail Gavrilov
2024-10-15 19:55 ` Peter Zijlstra [this message]
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=20241015195548.GV17263@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=vschneid@redhat.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