From: gc-user <gc-user@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Linux kernel 6.5: System not waking up from standby / suspend.
Date: Wed, 04 Oct 2023 12:38:52 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46427@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1827 bytes --]
New issue by gc-user on void-packages repository
https://github.com/void-linux/void-packages/issues/46427
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.13_2 x86_64 GenuineIntel uptodate hold rrmDDFFFFFFFFF
### Package(s) Affected
linux / linux6.5 (maybe linux-headers / linux6.5-headers)
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
This problem seems to have been mentioned here:
https://github.com/linux-surface/linux-surface/issues/1258
They seem to have applied a workaround, but only for their proprietary kernel in v6.5.5. And it sounds like it's not a permanent / solid solution, which should come from upstream..
### Expected behaviour
The system should wake up from standby / suspend when hitting a key on the keyboard, but it doesn't.
This happened once in a while with previous kernel versions (<= 6.3), but with kernel v6.5 it happens 100% of the time.
Also: I put linux and linux-headers on hold and updated all the other packages that had updates yesterday, including zfs and linux6.3. No issues with waking up the system from standby with those updates. So, it most probably is linux / linux6.5 that's causing the issue.
### Actual behaviour
The system can't be woken up by hitting a key on the keyboard from standby / suspend.
### Steps to reproduce
0. linux / linux-headers was upgraded to kernel 6.5 from 6.3 yesterday.
1. Update linux / linux-headers (or install kernel 6.5 via installing linux6.5 / linux6.5-headers).
2. Reboot to make the system run kernel 6.5.
3. Send the system to standby / suspend.
4. Try to wake the system up from standby / suspend.
5. Notice (probably) nothing happening = the system (probably) not waking up from standby / suspend.
If it is DE dependent: My system runs xfce.
next reply other threads:[~2023-10-04 10:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 10:38 gc-user [this message]
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
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46427@inbox.vuxu.org \
--to=gc-user@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).