From: JoergRoedel <joro@8bytes.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Jörg-Volker Peetz" <jvpeetz@web.de>,
SuraveeSuthikulpanit <suravee.suthikulpanit@amd.com>,
WillDeacon <will@kernel.org>,
stable@vger.kernel.org
Subject: Re: Linux 5.17.5
Date: Mon, 2 May 2022 11:23:43 +0200 [thread overview]
Message-ID: <Ym+jH9ekmZgwwU/H@8bytes.org> (raw)
In-Reply-To: <Ym6X3enhptEUyyJG@kroah.com>
On Sun, May 01, 2022 at 04:23:25PM +0200, Greg KH wrote:
> On Sun, May 01, 2022 at 02:37:36PM +0200, Jörg-Volker Peetz wrote:
> > Is this serious?
> > CPU is AMD Ryzen 7 5700G (RENOIR).
> > The config file is attached.
> > With kernel 5.17.3 this warning did not appear.
>
> Can you use 'git bisect' to track down the offending change?
This warning is not serious, it means that the GA log needs a very long
time to initialize. We have seen this upstream already and I am
currently working with AMD to find the root-cause for the large delay.
There is already a fix which increases the delay, but it doesn't seem to
help on every machine. The fix should already be in v5.17.5.
I also suspect this is hard to bisect, as it seems to be timing related.
I will send you a patch for testing in the next days, would be great if
you could report back then.
Regards,
Joerg
next prev parent reply other threads:[~2022-05-02 9:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 13:11 Linux 5.17.5 Greg Kroah-Hartman
2022-04-27 13:11 ` Greg Kroah-Hartman
2022-05-01 12:37 ` Jörg-Volker Peetz
2022-05-01 14:23 ` Greg KH
2022-05-02 9:23 ` JoergRoedel [this message]
2022-05-02 9:42 ` JoergRoedel
2022-05-02 9:45 ` JoergRoedel
2022-05-02 10:40 ` Jörg-Volker Peetz
2022-05-02 22:17 ` Jörg-Volker Peetz
2022-05-04 8:16 ` JoergRoedel
2022-05-04 9:51 ` Jörg-Volker Peetz
2022-05-04 13:21 ` Jörg-Volker Peetz
2022-05-20 10:30 ` Joerg Roedel
2022-05-20 10:48 ` Jörg-Volker Peetz
2022-05-20 11:14 ` Joerg Roedel
2022-05-20 16:21 ` Jörg-Volker Peetz
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=Ym+jH9ekmZgwwU/H@8bytes.org \
--to=joro@8bytes.org \
--cc=gregkh@linuxfoundation.org \
--cc=jvpeetz@web.de \
--cc=stable@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=will@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