From: Dave Hansen <dave.hansen@intel.com>
To: Kalle Valo <kvalo@kernel.org>, Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
x86@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
Jeff Johnson <quic_jjohnson@quicinc.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Daniel Sneddon <daniel.sneddon@linux.intel.com>
Subject: Re: [regression] suspend stress test stalls within 30 minutes
Date: Tue, 14 May 2024 09:10:07 -0700 [thread overview]
Message-ID: <feaefaae-e25b-4a48-b6be-e20054f2c8df@intel.com> (raw)
In-Reply-To: <874jb0jzx5.fsf@kernel.org>
On 5/14/24 06:17, Kalle Valo wrote:
> The kernel we use in our ath11k testing has almost all kernel debug
> features enabled so I decided disable all of them, which unsurprisingly
> also fixed my suspend problems. So maybe this is something which happens
> only when MITIGATION_IBRS_ENTRY and some debug option from 'Kernel
> hacking' are both enabled?
I had my money on DEBUG_ENTRY, but it doesn't look like you ever had it
enabled.
I've got basically two theories:
One, the IBRS value is getting mucked up somewhere, either that %r15
value is getting stepped on or the per-cpu value is corrupt and the
WRMSR #GP's, causing the hang.
Two, IBRS_{ENTER,EXIT} is called in a "wrong" context somewhere. Either
it is clobbering something it shouldn't or it is assuming something is
in place that is not (like a valid stack).
But the whole "'sudo shutdown -h now' then suspend somehow immediately
unstalls" thing is really perplexing. I hope Pawan has some ideas.
next prev parent reply other threads:[~2024-05-14 16:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 18:22 [regression] suspend stress test stalls within 30 minutes Kalle Valo
2024-05-11 18:48 ` Borislav Petkov
2024-05-11 18:49 ` Borislav Petkov
2024-05-11 20:26 ` Kalle Valo
2024-05-13 19:58 ` Kalle Valo
2024-05-14 13:17 ` Kalle Valo
2024-05-14 16:05 ` Borislav Petkov
2024-05-14 17:36 ` Pawan Gupta
2024-05-17 17:15 ` Kalle Valo
2024-05-17 17:22 ` Dave Hansen
2024-05-17 18:37 ` Kalle Valo
2024-05-17 18:48 ` Dave Hansen
2024-05-17 18:58 ` Kalle Valo
2024-05-17 19:08 ` Rafael J. Wysocki
2024-05-17 19:00 ` Rafael J. Wysocki
2024-05-22 1:52 ` Len Brown
2024-05-17 17:26 ` Borislav Petkov
2024-05-17 18:22 ` Kalle Valo
2024-05-14 16:10 ` Dave Hansen [this message]
2024-05-15 7:22 ` Pawan Gupta
2024-05-15 7:44 ` Borislav Petkov
2024-05-15 16:27 ` Pawan Gupta
2024-05-15 16:47 ` Kalle Valo
2024-05-16 7:03 ` Pawan Gupta
2024-05-16 14:25 ` Pawan Gupta
2024-05-16 14:32 ` Dave Hansen
2024-05-16 15:41 ` Pawan Gupta
2024-05-17 17:41 ` Kalle Valo
2024-05-17 18:31 ` Pawan Gupta
2024-05-17 17:23 ` Kalle Valo
2024-05-17 17:19 ` Kalle Valo
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=feaefaae-e25b-4a48-b6be-e20054f2c8df@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=quic_jjohnson@quicinc.com \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.