From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: Joerg Roedel <joro@8bytes.org>
Cc: SuraveeSuthikulpanit <suravee.suthikulpanit@amd.com>,
vasant.hegde@amd.com, WillDeacon <will@kernel.org>,
stable@vger.kernel.org
Subject: Re: Linux 5.17.5
Date: Fri, 20 May 2022 12:48:28 +0200 [thread overview]
Message-ID: <22b19b34-5cf8-e026-97f8-c66011ee535b@web.de> (raw)
In-Reply-To: <YodtvQJXInHDI3lD@8bytes.org>
Yes, I will test it on top of 5.17.9, o.k.?
Would you also be interested to get a timing from my computer?
Thank you and regards,
Jörg.
Joerg Roedel wrote on 20/05/2022 12:30:
> Hi Jörg,
>
> On Wed, May 04, 2022 at 03:21:45PM +0200, Jörg-Volker Peetz wrote:
>> now with the really patched kernel 5.17.5 the warning doesn't show up anymore. I
>> did two cold starts and one reboot.
>>
>> There are only two warnings regarding the CPU:
>>
>> [ 2.659141] amdgpu 0000:30:00.0: amdgpu: PSP runtime database doesn't exist
>> [ 3.538925] amdgpu: SRAT table not found
>>
>> Sorry for the confusion and many thanks for your help.
>
> I just sent out a fix increasing the loop timeout, can you please test
> it and report whether it also make the message disappear on your
> machine?
>
> Thanks,
>
> Jörg
next prev parent reply other threads:[~2022-05-20 10:53 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
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 [this message]
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=22b19b34-5cf8-e026-97f8-c66011ee535b@web.de \
--to=jvpeetz@web.de \
--cc=joro@8bytes.org \
--cc=stable@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@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