From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Linux kernel 6.5, 6.6: System not waking up from standby / suspend.
Date: Tue, 05 Dec 2023 10:46:29 +0100 [thread overview]
Message-ID: <20231205094629.MEnOm2xhqCqr9ZC4jhfHYxm0B9mDBGiD4cSYOCjq6zw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46427@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/issues/46427#issuecomment-1840397915
Comment:
Relevant kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=218191
There's a proposed fix in there, but it seems a bit dubious it's the proper fix (written for a bug in AMD workstation CPUs, while both cases here are on intel laptops).
Without confirmation that it would be a fix for the right thing, I don't really want to go down the rabbit hole of trying to build it on the affected laptop.
next prev parent reply other threads:[~2023-12-05 9:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 10:38 [ISSUE] Linux kernel 6.5: " gc-user
2023-10-06 19:11 ` gc-user
2023-10-09 4:22 ` Fremen2001
2023-10-09 7:55 ` gc-user
2023-10-30 21:31 ` gc-user
2023-10-30 21:44 ` gc-user
2023-11-02 20:04 ` gc-user
2023-11-02 20:43 ` 0x5c
2023-11-02 21:11 ` gc-user
2023-11-02 21:28 ` 0x5c
2023-11-03 9:38 ` gc-user
2023-11-22 18:02 ` gc-user
2023-11-26 18:54 ` Linux kernel 6.5, 6.6: " gc-user
2023-11-26 20:55 ` gc-user
2023-11-26 20:55 ` gc-user
2023-11-26 21:02 ` 0x5c
2023-11-27 11:06 ` gc-user
2023-11-29 5:16 ` 0x5c
2023-12-05 9:46 ` 0x5c [this message]
2023-12-05 15:11 ` gc-user
2023-12-06 9:06 ` 0x5c
2023-12-06 9:08 ` 0x5c
2023-12-07 11:31 ` 0x5c
2023-12-08 11:19 ` Fremen2001
2023-12-08 11:23 ` 0x5c
2023-12-20 18:35 ` gc-user
2023-12-30 18:26 ` gc-user
2024-01-03 13:16 ` [ISSUE] [CLOSED] " gc-user
2024-01-03 13:16 ` gc-user
2024-01-03 18:07 ` gc-user
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=20231205094629.MEnOm2xhqCqr9ZC4jhfHYxm0B9mDBGiD4cSYOCjq6zw@z \
--to=0x5c@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).