From: Kalle Valo <kvalo@kernel.org>
To: 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>
Subject: Re: [regression] suspend stress test stalls within 30 minutes
Date: Sat, 11 May 2024 23:26:49 +0300 [thread overview]
Message-ID: <87h6f4jdrq.fsf@kernel.org> (raw)
In-Reply-To: <20240511184945.GDZj-9yaOEWqf1ng8u@fat_crate.local> (Borislav Petkov's message of "Sat, 11 May 2024 20:49:45 +0200")
Borislav Petkov <bp@alien8.de> writes:
> On Sat, May 11, 2024 at 08:48:47PM +0200, Borislav Petkov wrote:
>> On Sat, May 11, 2024 at 09:22:43PM +0300, Kalle Valo wrote:
>> > Here's the diff between broken and working .config:
>> >
>> > $ diffconfig broken.config works.config
>> > -CALL_PADDING y
>> > -CALL_THUNKS y
>> > -CALL_THUNKS_DEBUG n
>> > -HAVE_CALL_THUNKS y
>> > -MITIGATION_CALL_DEPTH_TRACKING y
>> > -MITIGATION_GDS_FORCE y
>> > -MITIGATION_IBPB_ENTRY y
>> > -MITIGATION_IBRS_ENTRY y
>> > -MITIGATION_PAGE_TABLE_ISOLATION y
>> > -MITIGATION_RETHUNK y
>> > -MITIGATION_RETPOLINE y
>> > -MITIGATION_RFDS y
>> > -MITIGATION_SLS y
>> > -MITIGATION_SPECTRE_BHI y
>
> ... and if it started with -rc4, I'd try this one first.
I'm not sure if this bug started with -rc4, let's say somewhere between
-rc3 and -rc6. I'll start with disabling MITIGATION_SPECTRE_BHI and then
I'll disable them one by one. But that has to wait next week, tomorrow
is Mother's Day in Finland.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-05-11 20:26 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 [this message]
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
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=87h6f4jdrq.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).