From: Dave Hansen <dave.hansen@intel.com>
To: Kalle Valo <kvalo@kernel.org>, Borislav Petkov <bp@alien8.de>
Cc: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
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: Fri, 17 May 2024 10:22:32 -0700 [thread overview]
Message-ID: <35086bb6-ee11-4ac6-b8ba-5fab20065b54@intel.com> (raw)
In-Reply-To: <87msoofjg1.fsf@kernel.org>
On 5/17/24 10:15, Kalle Valo wrote:
> Borislav Petkov <bp@alien8.de> writes:
>> There might be some #GP or so in the logs in case we've managed to f*ck
>> up microcode application which emulates that IBRS MSR bit and the
>> actual toggling or so when suspending...
> 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.
>
> Let me know if you need more info.
Kalle, could you remind us what we're seeing here? Does this show 30
working rtcwake tests followed by a failure at "rtcwake test 31" where
the system failed to suspend?
next prev parent reply other threads:[~2024-05-17 17:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 18:22 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 [this message]
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=35086bb6-ee11-4ac6-b8ba-5fab20065b54@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®