[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <875xvcfgdq.fsf@kernel.org>
Date: Fri, 17 May 2024 21:22:09 +0300
From: Kalle Valo <kvalo@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Pawan Gupta <pawan.kumar.gupta@...ux.intel.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>
Subject: Re: [regression] suspend stress test stalls within 30 minutes
Borislav Petkov <bp@...en8.de> writes:
> On Fri, May 17, 2024 at 08:15:58PM +0300, Kalle Valo wrote:
>> So the weird part is that when the bug happens (ie. suspend stalls) I
>> can access the box normally using ssh and I don't see anything special
>> in dmesg. Below is a full copy of dmesg output after the suspend
>> stalled. Do note that I copied this dmesg before I updated microcode so
>> it will still show the old microcode version.
>
> Does that mean that you'd still see the stall even with the latest
> microcode revision 0xf8?
Yeah, no luck with that. I have more information in my other email.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists