Can't resume from sleep with Alder Lake and AMD GPU

Bug #1971642 reported by M Willis Monroe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Since upgrading to Jammy I can no longer put the desktop to sleep and successfully resume. I'm using the stock kernel and stock mesa drivers for the GPU.

When I press the wake button on my desktop the computer lights turn on briefly, but no power is going to USB devices (e.g. the mouse doesn't light up) and the computer never seems to wake. It also can't be reached via SSH on the local network.

The /var/log/syslog is not helpful as its corrupted right at the point of sleep.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-27-generic 5.15.0-27.28
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: willis 2954 F.... pulseaudio
 /dev/snd/controlC0: willis 2954 F.... pulseaudio
 /dev/snd/controlC3: willis 2954 F.... pulseaudio
 /dev/snd/controlC1: willis 2954 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed May 4 18:26:55 2022
HibernationDevice: RESUME=UUID=9f2b41d9-3869-487f-b10f-14b6653df4fb
InstallationDate: Installed on 2017-10-25 (1652 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Gigabyte Technology Co., Ltd. B660M DS3H DDR4
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=918ad661-6679-4439-97a7-cbf8be0f0981 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-27-generic N/A
 linux-backports-modules-5.15.0-27-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-04-28 (6 days ago)
dmi.bios.date: 11/10/2021
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F3
dmi.board.asset.tag: Default string
dmi.board.name: B660M DS3H DDR4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF3:bd11/10/2021:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnB660MDS3HDDR4:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB660MDS3HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B660 MB
dmi.product.name: B660M DS3H DDR4
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
M Willis Monroe (willismonroe) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
M Willis Monroe (willismonroe) wrote :

Still an issue with 5.15.0-30-generic

Revision history for this message
M Willis Monroe (willismonroe) wrote :

Still an issue with 5.15.0-40-generic

This is the best log I can get out of the situation:

Jun 24 10:54:05 willis-desktop systemd[1]: Reached target Sleep.
Jun 24 10:54:05 willis-desktop systemd[1]: Starting Record successful boot for GRUB...
Jun 24 10:54:05 willis-desktop systemd[1]: Starting System Suspend...
Jun 24 10:54:05 willis-desktop systemd[1]: grub-common.service: Deactivated successfully.
Jun 24 10:54:05 willis-desktop systemd[1]: Finished Record successful boot for GRUB.
Jun 24 10:54:05 willis-desktop systemd-sleep[89176]: Entering sleep state 'suspend'...
Jun 24 10:54:05 willis-desktop kernel: [14491.441489] PM: suspend entry (deep)
<At this point I have to reset the computer because it won't resume, below is the next boot>
Jun 24 10:56:29 willis-desktop systemd-modules-load[477]: Inserted module 'lp'
Jun 24 10:56:29 willis-desktop systemd-modules-load[477]: Inserted module 'ppdev'
Jun 24 10:56:29 willis-desktop systemd[1]: Starting Flush Journal to Persistent Storage...
Jun 24 10:56:29 willis-desktop systemd[1]: Finished Load/Save Random Seed.

There seems to be nothing between sleeping and hard restarting which would indicate why it can't resume

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.