From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 215883] Unable to resume from suspend with module `intel_lpss_pci` enabled
Date: Thu, 10 Sep 2026 12:05:35 +0000 [thread overview]
Message-ID: <bug-215883-215701-4UqtZ5Fk5Q@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215883-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215883
silverducks@altlinux.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |silverducks@altlinux.org
--- Comment #6 from silverducks@altlinux.org ---
Greetings!
I believe I have the same bug on similiar hardware.
Here are the details:
Kernel:
Version: Linux host-175 7.3.0-rc2 #1 SMP PREEMPT_DYNAMIC
Wed Sep 9 16:26:06 MSK 2026 x86_64 GNU/Linux
Git commit/tree:
Architecture: x86_64
Distribution: Alt Linux Education 11.2 rc3
Compiler: GCC 13.2.1
Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-7.3.0-rc2 \
root=UUID=f35f4c9a-9e09-477f-ae34-33ea09d57042 ro \
resume=/dev/disk/by-uuid/9cb83606-d1a6-4839-b9ff-be22efdf26c3 \
panic=30 no_console_suspend ignore_loglevel
The problem was also reproduced with ALT Linux kernels 7.1, 7.0,
6.19, 6.18, and 6.12. Problem is exactly the same in all cases.
Hardware:
Motherboard: Gigabyte Z790 X AX Gaming
BIOS version: F15
CPU: Intel Core i5-14600K
Failure summary:
Suspending to S3 (deep) causes the system to hang. The fans and
indicator lights remain on, and the system does not respond to any
input, including short presses of the power button.
Steps to reproduce:
1. Boot with intel_lpss_pci module loaded
2. Suspend to S3 (deep)
Attachments (within archive):
- uname -a, lsmod, complete journal and kernel-only journal of the same
period for upstream kernel 7.3.0-rc2, Alt kernels 7.1, 6.12.
- Kernel configuration for upstream kernel 7.3.0-rc2, based on the
default ALT Linux kernel configuration with addition of debugging options
and a run through make olddefconfig
- Kernel module list
- lspci -vv and lspci -nnk, and list of devices with intel-lpss as driver
- dmidecode outputs
- /proc/acpi/wakeup
- Hardware and firmware information from sysfs
- os-release
- kernel command line used
Notes:
The problem appears related to intel_lpss_pci - when module is
blacklisted, S3 works normally.
Unbinding intel_lpss_pci from devices or removing it with modprobe -r
just before suspend does NOT prevent the failure.
S2 (s2idle) and hibernation to disk work fine.
Failure does NOT occur when booted with init=/bin/bash
Failure does occur when booted into multi-user.target
Let me know if I should open a new bug instead or if there's any
testing you'd like me to perform.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-09-10 12:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 8:24 [Bug 215883] New: Unable to resume from suspend with module `intel_lpss_pci` enabled bugzilla-daemon
2022-04-25 17:32 ` [Bug 215883] " bugzilla-daemon
2022-04-25 17:55 ` bugzilla-daemon
2022-04-25 19:21 ` bugzilla-daemon
2022-04-25 19:26 ` bugzilla-daemon
2022-04-25 19:46 ` bugzilla-daemon
2026-09-10 12:05 ` bugzilla-daemon [this message]
2026-09-10 12:05 ` bugzilla-daemon
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=bug-215883-215701-4UqtZ5Fk5Q@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@vger.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