https://bugzilla.kernel.org/show_bug.cgi?id=220881
Bug ID: 220881
Summary: ASUS Vivobook Pro 15 Q533mj (Meteor Lake + RTX 3050)
fails to resume from suspend (s2idle and deep) on
Fedora 43
Product: ACPI
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: Power-Sleep-Wake
Assignee: [email protected]
Reporter: [email protected]
Regression: No
On an ASUS Vivobook Pro 15 with Intel Meteor Lake (Core Ultra / Arc iGPU) and
NVIDIA RTX 3050, Linux fails to resume from suspend in both s2idle and deep
modes. The system enters suspend, but never resumes: closing the lid or running
systemctl suspend leads to a black screen and requires a hard power-off. This
happens on a fresh Fedora 43 install without the NVIDIA proprietary driver and
with the SD card reader disabled in BIOS.
Hardware
Laptop: ASUS Vivobook Pro 15 (Q533MJ-like Meteor Lake model)
lspci (shortened):
0000:00:00.0 Host bridge: Intel Corporation Meteor Lake-H 6p+8e cores Host
Bridge/DRAM Controller (rev 04)
0000:00:01.0 PCI bridge: Intel Corporation Meteor Lake-H PCIe Root Port #12
(rev 10)
0000:00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel
Arc Graphics] (rev 08)
0000:00:04.0 Signal processing controller: Intel Corporation Meteor Lake-P
Dynamic Tuning Technology (rev 04)
0000:00:07.0 PCI bridge: Intel Corporation Meteor Lake-P Thunderbolt 4 PCI
Express Root Port #0 (rev 10)
0000:00:08.0 System peripheral: Intel Corporation Meteor Lake-P Gaussian &
Neural-Network Accelerator (rev 20)
0000:00:0a.0 Signal processing controller: Intel Corporation Meteor Lake-P
Platform Monitoring Technology (rev 01)
0000:00:0b.0 Processing accelerators: Intel Corporation Meteor Lake NPU (rev
04)
0000:00:0d.0 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 USB
Controller (rev 10)
0000:00:0d.2 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 NHI
#0 (rev 10)
0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management Device
NVMe RAID Controller Intel Corporation
0000:00:12.0 Serial controller: Intel Corporation Meteor Lake-P Integrated
Sensor Hub (rev 20)
0000:00:14.0 USB controller: Intel Corporation Meteor Lake-P USB 3.2 Gen 2x1
xHCI Host Controller (rev 20)
0000:00:14.2 RAM memory: Intel Corporation Meteor Lake-H/U Shared SRAM (rev 20)
0000:00:15.0 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO
I2C Controller #0 (rev 20)
0000:00:15.1 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO
I2C Controller #1 (rev 20)
0000:00:16.0 Communication controller: Intel Corporation Meteor Lake-P CSME
HECI #1 (rev 20)
0000:00:19.0 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO
I2C Controller #4 (rev 20)
0000:00:1c.0 PCI bridge: Intel Corporation Device 7e3e (rev 20)
0000:00:1c.7 PCI bridge: Intel Corporation Meteor Lake-H/U PCIe Root Port #8
(rev 20)
0000:00:1f.0 ISA bridge: Intel Corporation Meteor Lake-H eSPI Controller (rev
20)
0000:00:1f.3 Multimedia audio controller: Intel Corporation Meteor Lake-P HD
Audio Controller (rev 20)
0000:00:1f.4 SMBus: Intel Corporation Meteor Lake-P SMBus Controller (rev 20)
0000:00:1f.5 Serial bus controller: Intel Corporation Meteor Lake-P SPI
Controller (rev 20)
0000:01:00.0 VGA compatible controller: NVIDIA Corporation GA107BM /
GN20-P0-R-K2 [GeForce RTX 3050 6GB Laptop GPU] (rev a1)
0000:01:00.1 Audio device: NVIDIA Corporation GA107 High Definition Audio
Controller (rev a1)
0000:2c:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
0000:2d:00.0 Network controller: Intel Corporation Wi-Fi 6E(802.11ax)
AX210/AX1675* 2x2 [Typhoon Peak] (rev 1a)
10000:e0:06.0 System peripheral: Intel Corporation RST VMD Managed Controller
10000:e0:06.2 PCI bridge: Intel Corporation Device 7ecb (rev 10)
10000:e1:00.0 Non-Volatile memory controller: Micron Technology Inc 2400 NVMe
SSD (DRAM-less) (rev 03)
The internal SD card reader (Genesys Logic GL9755) is present in Windows but
has been disabled in BIOS during testing.
BIOS:
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.6.0 present.
Table at 0x66AC3000.
Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
Vendor: American Megatrends International, LLC.
Version: N6506MJ.313
Release Date: 10/13/2025
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 0 MB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
ACPI is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.32
Firmware Revision: 18.239
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ASUS Vivobook Pro 15 N6506MJ_Q533MJ
Version: 1.0
Serial Number: S7N0CV02C920275
UUID: 7fc7a720-5889-ce4d-80fc-0513d956d775
Wake-up Type: Power Switch
SKU Number:
Family: ASUS Vivobook Pro 15
Handle 0x0002, DMI type 2, 15 bytes
Software
Distribution: Fedora 43 Workstation (fresh install)
Kernel: Linux fedora 6.17.12-300.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Dec
13 05:06:24 UTC 2025 x86_64 GNU/Linux
Graphics: only Intel iGPU in use (no NVIDIA proprietary driver installed;
default modesetting/i915)
Secure Boot: disabled
Sleep state information
$ cat /sys/power/mem_sleep
[s2idle] deep
ACPI in dmesg/journal:
ACPI: PM: (supports S0 S3 S4 S5)
Low-power S0 idle used by default for system suspend
So both s2idle and deep are advertised.
Reproduction steps:
1. Boot Fedora 43 with default kernel, fresh user session.
2. Confirm no proprietary NVIDIA driver is installed.
3. Ensure internal SD card reader is disabled in BIOS (to rule out known GL9755
issues).
4. Test suspend by closing the lid (logind default) OR by running:
systemctl suspend
5. Wait ~20–30 seconds for the machine to fully enter suspend.
6. Attempt to resume with power button or keyboard.
Observed result (s2idle default):
- Keyboard backlight turns on.
- Screen remains black, no backlight, no response to keyboard/mouse.
- Machine never reaches a state where it reacts to input; requires long press
of power button to force power-off.
- journalctl -b -1 shows suspend entry but no resume line.
Observed result with mem_sleep_default=deep:
- GRUB configured with: mem_sleep_default=deep in GRUB_CMDLINE_LINUX.
- cat /sys/power/mem_sleep after boot shows s2idle [deep].
- Running systemctl suspend powers the machine down.
- On wake (power button or keys): no reaction for several seconds; then
keyboard backlight goes off and the machine effectively dies.
- Again, no resume log in journalctl -b -1, only suspend entry.
Relevant logs (previous boot)
From sudo journalctl -b -1 | grep -Ei 'suspend|sleep|resume|pm:':
PM: RTC time: 08:45:48, date: 2025-12-20
ACPI: PM: (supports S0 S3 S4 S5)
Low-power S0 idle used by default for system suspend
...
Dec 20 12:24:00 fedora systemd-logind[1107]: Lid closed.
Dec 20 12:24:04 fedora systemd-logind[1107]: Suspending...
Dec 20 12:24:09 fedora systemd[1]: Reached target sleep.target - Sleep.
Dec 20 12:24:09 fedora systemd[1]: Starting systemd-suspend.service - System
Suspend...
Dec 20 12:24:09 fedora systemd-sleep[11736]: Successfully froze unit
'user.slice'.
Dec 20 12:24:09 fedora systemd-sleep[11736]: Performing sleep operation
'suspend'...
Dec 20 12:24:09 fedora kernel: PM: suspend entry (s2idle)
There is no corresponding PM: suspend exit or resume message before the next
hard-boot.
From sudo journalctl -b -1 -u systemd-logind -u systemd-suspend -u
systemd-sleep:
Dec 20 12:24:00 fedora systemd-logind[1107]: Lid closed.
Dec 20 12:24:04 fedora systemd-logind[1107]: Suspending...
Dec 20 12:24:09 fedora systemd[1]: Starting systemd-suspend.service - System
Suspend...
Dec 20 12:24:09 fedora systemd-sleep[11736]: Successfully froze unit
'user.slice'.
Dec 20 12:24:09 fedora systemd-sleep[11736]: Performing sleep operation
'suspend'...
Again, no resume logs.
What I’ve already tried
- Fresh Fedora 43 install (Btrfs, default settings).
- No NVIDIA proprietary driver installed (only Intel GPU in use).
- Disabled built-in SD card reader (Genesys Logic GL9755) in BIOS to avoid
known suspend/SD issues.
Tested both:
- Default s2idle
- mem_sleep_default=deep (S3) in kernel command line.
- Tested suspend triggered by lid-close and by systemctl suspend.
- Same behavior on both: successful suspend entry, never resumes; only hard
power-off recovers the system.
Expected behavior:
-System should resume from suspend (either s2idle or deep) when pressing power
button or opening the lid, with display and input working normally.
Actual behavior:
- System enters suspend, then never resumes:
- With s2idle: keyboard backlight on but black screen, no input; requires hard
power-off.
- With deep: no visible reaction to wake key, then eventually powers off; no
resume logged.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
acpi-bugzilla mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
