[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87eda0fj2u.fsf@kernel.org>
Date: Fri, 17 May 2024 20:23:53 +0300
From: Kalle Valo <kvalo@...nel.org>
To: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
Cc: Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...el.com>,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, "Rafael J. Wysocki"
<rafael@...nel.org>, x86@...nel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, regressions@...ts.linux.dev, Jeff Johnson
<quic_jjohnson@...cinc.com>, Daniel Sneddon
<daniel.sneddon@...ux.intel.com>
Subject: Re: [regression] suspend stress test stalls within 30 minutes
Pawan Gupta <pawan.kumar.gupta@...ux.intel.com> writes:
> On Wed, May 15, 2024 at 09:44:42AM +0200, Borislav Petkov wrote:
>> On May 15, 2024 9:22:31 AM GMT+02:00, Pawan Gupta
>> <pawan.kumar.gupta@...ux.intel.com> wrote:
>> > Other interesting thing to try is cmdline
>> >"dis_ucode_ldr".
>>
>> Right, is his microcode revision 0xf4 the right one for that model?
>
> 0xf4 microcode is not the latest one, the latest is 0xf8:
>
> https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/blob/main/intel-ucode/06-9e-09
>
> Kalle, can you please try with 0xf8 and see if the issue is still present?
I updated to this version:
[ 11.907565] microcode: Current revision: 0x000000f8
[ 11.907614] microcode: Updated early from: 0x000000ea
But unfortunately no luck, the suspend still fails after 29 loops.
Powered by blists - more mailing lists