You are not logged in.
Pages: 1
I'm running suspend, but the fans stay on, and the machine doesn't wake after suspend. The logs from last boot:
Jun 05 22:00:03 exia systemd[1]: Starting Snapshot ZFS Pool...
Jun 05 22:00:03 exia systemd[1]: Starting system activity accounting tool...
Jun 05 22:00:03 exia systemd[1]: sysstat-collect.service: Deactivated successfully.
Jun 05 22:00:03 exia systemd-logind[2731]: The system will suspend now!
Jun 05 22:00:03 exia systemd[1]: Finished system activity accounting tool.
Jun 05 22:00:03 exia NetworkManager[3120]: <info> [1685995203.3677] manager: sleep: sleep requested (sleeping: no enabled: yes)
Jun 05 22:00:03 exia NetworkManager[3120]: <info> [1685995203.3723] device (enp1s0f0u4): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jun 05 22:00:03 exia systemd-networkd[522]: enp1s0f0u4: Link DOWN
Jun 05 22:00:03 exia systemd-networkd[522]: enp1s0f0u4: Lost carrier
Jun 05 22:00:03 exia NetworkManager[3120]: <info> [1685995203.3828] manager: NetworkManager state is now ASLEEP
Jun 05 22:00:03 exia sanoid[3675179]: INFO: cache expired - updating from zfs list.
Jun 05 22:00:04 exia kscreenlocker_greet[3675212]: Qt: Session management error: networkIdsList argument is NULL
Jun 05 22:00:05 exia kscreenlocker_greet[3675212]: kf.kirigami: Failed to find a Kirigami platform plugin
Jun 05 22:00:06 exia kscreenlocker_greet[3675212]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
Jun 05 22:00:06 exia systemd[1]: Reached target Sleep.
Jun 05 22:00:06 exia systemd[1]: Starting System Suspend...
Jun 05 22:00:06 exia systemd-sleep[3675408]: Entering sleep state 'suspend'...
Jun 05 22:00:06 exia kernel: PM: suspend entry (deep)Hardware:
H/W path Device Class Description
==================================================================
system System Product Name (SKU)
/0 bus ROG STRIX B450-F GAMING
/0/0 memory 64KiB BIOS
/0/22 memory 48GiB System Memory
/0/22/0 memory 8GiB DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns)
/0/22/1 memory 8GiB DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns)
/0/22/2 memory 16GiB DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns)
/0/22/3 memory 16GiB DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns)
/0/24 memory 768KiB L1 cache
/0/25 memory 4MiB L2 cache
/0/26 memory 16MiB L3 cache
/0/27 processor AMD Ryzen 7 1700X Eight-Core Processor
/0/100 bridge Family 17h (Models 00h-0fh) Root Complex
/0/100/0.2 generic Family 17h (Models 00h-0fh) I/O Memory Management Unit
/0/100/1.3 bridge Family 17h (Models 00h-0fh) PCIe GPP Bridge
/0/100/1.3/0 bus 400 Series Chipset USB 3.1 xHCI Compliant Host Controller
/0/100/1.3/0/0 usb1 bus xHCI Host Controller
/0/100/1.3/0/0/3 communication ASUS USB-BT500
/0/100/1.3/0/0/5 input ThinkPad Compact USB Keyboard with TrackPoint
/0/100/1.3/0/0/6 input MX Vertical Advanced Ergonomic Mouse
/0/100/1.3/0/1 usb2 bus xHCI Host Controller
/0/100/1.3/0.1 scsi4 storage 400 Series Chipset SATA Controller
/0/100/1.3/0.1/0 /dev/sda disk 2TB WDC WDS200T2B0A
/0/100/1.3/0.1/0/1 /dev/sda1 volume 1863GiB OS X ZFS partition or Solaris /usr partition
/0/100/1.3/0.1/0/9 /dev/sda9 volume 8191KiB reserved partition
/0/100/1.3/0.1/1 /dev/sdb disk 2TB Samsung SSD 860
/0/100/1.3/0.1/1/1 /dev/sdb1 volume 1863GiB OS X ZFS partition or Solaris /usr partition
/0/100/1.3/0.1/1/9 /dev/sdb9 volume 8191KiB reserved partition
/0/100/1.3/0.2 bridge 400 Series Chipset PCIe Bridge
/0/100/1.3/0.2/0 bridge 400 Series Chipset PCIe Port
/0/100/1.3/0.2/0/0 enp3s0 network I211 Gigabit Network Connection
/0/100/1.3/0.2/1 bridge 400 Series Chipset PCIe Port
/0/100/1.3/0.2/4 bridge 400 Series Chipset PCIe Port
/0/100/1.3/0.2/6 bridge 400 Series Chipset PCIe Port
/0/100/1.3/0.2/7 bridge 400 Series Chipset PCIe Port
/0/100/3.1 bridge Family 17h (Models 00h-0fh) PCIe GPP Bridge
/0/100/3.1/0 bridge Navi 10 XL Upstream Port of PCI Express Switch
/0/100/3.1/0/0 bridge Navi 10 XL Downstream Port of PCI Express Switch
/0/100/3.1/0/0/0 display Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
/0/100/3.1/0/0/0.1 multimedia Navi 10 HDMI Audio
/0/100/3.4 bridge Family 17h (Models 00h-0fh) PCIe GPP Bridge
/0/100/3.4/0 /dev/nvme0 storage Samsung SSD 970 EVO Plus 500GB
/0/100/3.4/0/0 hwmon0 disk NVMe disk
/0/100/3.4/0/2 /dev/ng0n1 disk NVMe disk
/0/100/3.4/0/1 /dev/nvme0n1 disk 500GB NVMe disk
/0/100/3.4/0/1/1 /dev/nvme0n1p1 volume 1023MiB Windows FAT volume
/0/100/3.4/0/1/2 /dev/nvme0n1p2 volume 364GiB EFI partition
/0/100/3.4/0/1/3 /dev/nvme0n1p3 volume 99GiB EFI partition
/0/100/7.1 bridge Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
/0/100/7.1/0 generic Zeppelin/Raven/Raven2 PCIe Dummy Function
/0/100/7.1/0.2 generic Family 17h (Models 00h-0fh) Platform Security Processor (PSP) 3.0 Device
/0/100/7.1/0.3 bus Family 17h (Models 00h-0fh) USB 3.0 Host Controller
/0/100/7.1/0.3/0 usb3 bus xHCI Host Controller
/0/100/7.1/0.3/0/1 generic SHIELD Android TV
/0/100/7.1/0.3/0/3 multimedia Blue Snowball
/0/100/7.1/0.3/1 usb4 bus xHCI Host Controller
/0/100/7.1/0.3/1/4 multimedia Logitech StreamCam
/0/100/8.1 bridge Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
/0/100/8.1/0 generic Zeppelin/Renoir PCIe Dummy Function
/0/100/8.1/0.2 scsi11 storage FCH SATA Controller [AHCI mode]
/0/100/8.1/0.2/0.0.0 /dev/sdc disk 128GB Samsung SSD 840
/0/100/8.1/0.2/0.0.0/2 /dev/sdc2 volume 119GiB EFI partition
/0/100/8.1/0.3 multimedia Family 17h (Models 00h-0fh) HD Audio Controller
/0/100/14 bus FCH SMBus Controller
/0/100/14.3 bridge FCH LPC Bridge
/0/101 bridge Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
/0/102 bridge Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
/0/103 bridge Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
/0/104 bridge Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
/0/105 bridge Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
/0/106 bridge Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
/0/107 bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
/0/108 bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
/0/109 bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
/0/10a bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
/0/10b bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
/0/10c bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
/0/10d bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
/0/10e bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
/0/1 system System Board
/0/2 system AT Real-Time Clock
/0/3 system Motherboard registers
/0/4 communication 16550A-compatible COM port
/0/5 system Motherboard registersOffline
Hi reactormonk,
Your log from the last boot is incomplete. It's only... ~18 lines long? We can't even see your kernel version!
But I'm also chiming in to note that I seem to have problems waking up from hibernation since upgrading to 6.3.5 6.3.6 on the -zen branch, seemingly appearing on a system where hibernation used to work without problems previously. But I've also had good hibernations on 6.3.5 along with failures (no succesfull hibernations on 6.3.6 so far, no problems before 6.3.5). EDIT: No problems before 6.3.6 according to at least 30 or so last boots, checked via journalctl - I had misred my logs (not all of my boots contain hibernations, but most do, and 6.3.6 fails consistently, while pre-6.3.6 hibernation worked consistently).
This is on a desktop, and the issue is that the system will either hang (fans keep running but the system is unresponsive, and does not cut power) at hibernation, or shut down but hang when waking up. In both cases these are the last lines in the logs:
kesä 08 04:58:10 ArkkiVille systemd-sleep[28321]: Entering sleep state 'hibernate'...
kesä 08 04:58:10 ArkkiVille kernel: PM: hibernation: hibernation entryIf the issue persists I will post my complete logs and more info later on here.
Cheers!
EDIT: I re-checked my logs and the problem in my case started with 6.3.6 and is consistent. I had **no failures** with 6.3.5 - I had somehow misred my logs.
Last edited by Wild Penguin (2023-06-08 12:18:47)
Offline
Weird. I downgraded from 6.3.8-zen to 6.3.5-zen, the machine didn't properly go to sleep. The fans stayed on.
Offline
Same thing is happening to me, system cannot wake up from suspend/sleep.
Here is my
journalctl -b -1 It occured last boot.
journalctl -b -1
Offline
Suspend is broken on the zen branch for me since 6.3.6. It fails consistently and always, whereas on the regular branch suspend works without issues. I've just been busy hence I have not posted here or tried to troubleshoot the issue, make a bug report etc...
It seems weird since the problems seems to have started on slightly different versions for some, and even on the vanilla branch. This doesn't mean the issues aren't related - it could be some combination(s) of circumstances, out of which zen can be a factor, while the underlying cause is the same.
Cheers! (I will post failure logs later...)
Offline
Same issue with zen branch
un 18 10:32:42 cc-desktop kernel: Linux version 6.3.8-zen1-1-zen (linux-zen@archlinux) (gcc (GCC) 13.1.1 20230429, GNU ld (GNU Binutils) 2.40>
Jun 18 10:32:42 cc-desktop kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=445d0643-92d1-44fb-9789-a2782e0ea22f rw audit=0 logle>
Jun 18 10:32:42 cc-desktop kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jun 18 10:32:42 cc-desktop kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jun 18 10:32:42 cc-desktop kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jun 18 10:32:42 cc-desktop kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Jun 18 10:32:42 cc-desktop kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Jun 18 10:32:42 cc-desktop kernel: x86/fpu: xstate_offset[9]: 832, xstate_sizes[9]: 8
Jun 18 10:32:42 cc-desktop kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format.
Jun 18 10:32:42 cc-desktop kernel: signal: max sigframe size: 3376
Jun 18 10:32:42 cc-desktop kernel: BIOS-provided physical RAM map:
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009d1efff] usable
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x0000000009d1f000-0x0000000009ffffff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x000000000a20e000-0x000000000affffff] usable
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000c327bfff] usable
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000c327c000-0x00000000c327cfff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000c327d000-0x00000000c9ff3fff] usable
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000c9ff4000-0x00000000ca3fafff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000ca3fb000-0x00000000ca5b0fff] ACPI data
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000ca5b1000-0x00000000cace2fff] ACPI NVS
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000cace3000-0x00000000cb95dfff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000cb95e000-0x00000000cb9fefff] type 20
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000cb9ff000-0x00000000ccffffff] usable
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000cd000000-0x00000000cfffffff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000fd600000-0x00000000fd7fffff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x0000000100000000-0x000000202f2fffff] usable
Jun 18 10:32:42 cc-desktop kernel: BIOS-e820: [mem 0x000000202f300000-0x000000202fffffff] reserved
Jun 18 10:32:42 cc-desktop kernel: NX (Execute Disable) protection: active
...
Jun 20 22:01:36 cc-desktop kernel: userif-2: sent link up event.
Jun 20 22:01:39 cc-desktop kernel: userif-2: sent link down event.
Jun 20 22:01:39 cc-desktop kernel: userif-2: sent link up event.
Jun 21 08:21:18 cc-desktop kernel: userif-2: sent link down event.
Jun 21 08:21:18 cc-desktop kernel: userif-2: sent link up event.
Jun 21 09:20:51 cc-desktop kernel: PM: suspend entry (deep)Last edited by beeender (2023-06-22 08:16:25)
Offline
The below commit in 6.4 may be relevant for the resume issue. Note that it came in after rc7 - so if you want to test you should build from Linus git head. Also looks like 6.4 should be released this coming Sunday and arch kernel likely soon after. Since this bug has been around for a while, it may or or may not be what you're experiencing, but sharing in case of interest or relevance.
commit e660abd551f1172e428b4e4003de887176a8a1fd (HEAD -> master, origin/master, origin/HEAD)
Merge: c74e2ac2383f 22db06337f59
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue Jun 20 15:45:34 2023 -0700
Merge tag 'acpi-6.4-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
Pull ACPI fix from Rafael Wysocki:
"Fix a kernel crash during early resume from ACPI S3 that has been
present since the 5.15 cycle when might_sleep() was added to
down_timeout(), which in some configurations of the kernel caused an
implicit preemption point to trigger at a wrong time"
* tag 'acpi-6.4-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
ACPI: sleep: Avoid breaking S3 wakeup due to might_sleep()
Offline
The below commit in 6.4 may be relevant for the resume issue. Note that it came in after rc7 - so if you want to test you should build from Linus git head. Also looks like 6.4 should be released this coming Sunday and arch kernel likely soon after. Since this bug has been around for a while, it may or or may not be what you're experiencing, but sharing in case of interest or relevance.
commit e660abd551f1172e428b4e4003de887176a8a1fd (HEAD -> master, origin/master, origin/HEAD)
Merge: c74e2ac2383f 22db06337f59
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue Jun 20 15:45:34 2023 -0700Merge tag 'acpi-6.4-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
Pull ACPI fix from Rafael Wysocki:
"Fix a kernel crash during early resume from ACPI S3 that has been
present since the 5.15 cycle when might_sleep() was added to
down_timeout(), which in some configurations of the kernel caused an
implicit preemption point to trigger at a wrong time"* tag 'acpi-6.4-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
ACPI: sleep: Avoid breaking S3 wakeup due to might_sleep()
Unfortunately, it seems this commit did not address the issue in this case in particular. Since kernel 6.4.1, I have had both a refusal to recover from sleep and a failed attempt to put the system to sleep just as with zen kernels newer than 6.3.5. Im going to try running the stock kernel rather than Zen just to make sure its specific to that patch set.
Offline
With the LTS kernel, the suspend works again. I'll try to find a few hours to bisect the issue.
Offline
I am not 100% certain but so far 6.4.7-2 zen kernel has not given me suspend issues like prior. The following 6.4.8 presented multiple issues including that suspend issue again. After I downgraded back to zen 6.4.7-2 it has been surprisingly uneventful though its possible I am just getting lucky. I have not tested 6.4.9 yet.
Either way, frequency of symptoms seems lower for me on this particular version, enough that I figured I might mention.
Offline
Pages: 1