[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <78a26d15-68eb-4a6f-a092-f7a554aa29e7@roeck-us.net>
Date: Thu, 24 Aug 2023 08:58:46 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Naresh Kamboju <naresh.kamboju@...aro.org>, stable@...r.kernel.org,
patches@...ts.linux.dev, linux-kernel@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
f.fainelli@...il.com, sudipm.mukherjee@...il.com,
srw@...dewatkins.net, rwarsow@....de, conor@...nel.org
Subject: Re: [PATCH 6.1 000/194] 6.1.47-rc1 review
On Thu, Aug 24, 2023 at 05:15:30PM +0200, Greg Kroah-Hartman wrote:
[ ... ]
>
> This might be an issue on AMD chips, but for some reason, in running
> this kernel on my systems here, I have no boot warnings at all. I
> blamed it on them being only AMD chips. If that's not the issue then I
> really have no idea, sorry.
>
AFAIK it depends on the compiler used and on the enabled debug options.
At some point I lost track about what exactly has to be enabled to see
the problem. We see it a lot with our (ChromeOS) debug kernel testing
which has various debug options enabled, to the point where we may
temporarily remove the warning from the kernel to stop the noise.
Alternatively, as I had suggested earlier, we could revert all srso patches
because they only seem to cause trouble. So far I have been resisting that
because I am concerned that it would make things even worse (like one can
not really revert a heart surgery without doing even more damage).
Guenter
Powered by blists - more mailing lists