linux-kernel - Re: [regression] suspend stress test stalls within 30 minutes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 16 May 2024 08:41:50 -0700
From: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Kalle Valo <kvalo@...nel.org>, Borislav Petkov <bp@...en8.de>,
	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

On Thu, May 16, 2024 at 07:32:54AM -0700, Dave Hansen wrote:
> On 5/16/24 07:25, Pawan Gupta wrote:
> > On Thu, May 16, 2024 at 12:03:22AM -0700, Pawan Gupta wrote:
> >> I am running the suspend test now and will update in the morning if I
> >> could reproduce the hang.
> > Completed 500 suspend iterations, but the hang is not reproduced 🙁
> > I have restarted the test.
> > 
> > BTW, could you please share your /proc/cmdline? Also, was there any
> > workload running with the suspend test? If I could not reproduce it in the
> > next run, I will run stress-ng with the suspend test.
> 
> I'd suggest two things:
> 
>   * Run everything in tools/testing/selftests/x86 in a loop during the
>     suspend test.
>   * Run perf or something else to generate some NMIs.

Will do.

> Those will ensure the dark corners of the entry code are being
> sufficiently prodded.
> 
> I also have sneaking suspicion that microcode updates during resume are
> the aggravating factor.

Lets see if Kalle is able to reproduce the hang with "dis_ucode_ldr".