You are not logged in.
Hello,
I have Thinkpad P43s and I'm fighting with correct power management for discrete Nvidia. After a suspend it usually cannot be reenabled again with bbswitch.
In journal I noticed that there are strange times of actions taken during suspend. It seems that some are done even after the wakeup. Is it just a wrong timestamp or can it be source of my problems with the nvidia card?
Nov 07 20:17:26 my-ntb kernel: wlp0s20f3: deauthenticating from d4:6e:0e:28:e7:ad by local choice (Reason: 3=DEAUTH_LEAVING)
Nov 07 20:17:27 my-ntb kernel: PM: suspend entry (deep)
Nov 07 20:17:27 my-ntb kernel: Filesystems sync: 0.011 seconds
Nov 07 20:17:29 my-ntb kernel: pcieport 0000:00:1d.0: Data Link Layer Link Active not set in 1000 msec
Nov 07 20:17:29 my-ntb kernel: bbswitch: enabling discrete graphics
Nov 07 20:17:29 my-ntb kernel: pci 0000:3c:00.0: Unable to change power state from D3cold to D0, device inaccessible
Nov 07 20:17:29 my-ntb kernel: pci 0000:3c:00.0: Unable to change power state from D3cold to D0, device inaccessible
Nov 07 20:17:29 my-ntb kernel: pci 0000:3c:00.0: Unable to change power state from D3cold to D0, device inaccessible
Nov 07 21:15:29 my-ntb kernel: Freezing user space processes ... (elapsed 0.003 seconds) done.
Nov 07 21:15:29 my-ntb kernel: OOM killer disabled.
Nov 07 21:15:29 my-ntb kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Nov 07 21:15:29 my-ntb kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 07 21:15:29 my-ntb kernel: e1000e: EEE TX LPI TIMER: 00000011
Nov 07 21:15:29 my-ntb kernel: ACPI: EC: interrupt blocked
Nov 07 21:15:29 my-ntb kernel: ACPI: PM: Preparing to enter system sleep state S3
Nov 07 21:15:29 my-ntb kernel: ACPI: EC: event blocked
Nov 07 21:15:29 my-ntb kernel: ACPI: EC: EC stopped
Nov 07 21:15:29 my-ntb kernel: ACPI: PM: Saving platform NVS memory
Nov 07 21:15:29 my-ntb kernel: Disabling non-boot CPUs ...
Nov 07 21:15:29 my-ntb kernel: smpboot: CPU 1 is now offline
Nov 07 21:15:29 my-ntb kernel: smpboot: CPU 2 is now offline
Nov 07 21:15:29 my-ntb kernel: smpboot: CPU 3 is now offline
Nov 07 21:15:29 my-ntb kernel: smpboot: CPU 4 is now offline
Nov 07 21:15:29 my-ntb kernel: smpboot: CPU 5 is now offline
Nov 07 21:15:29 my-ntb kernel: smpboot: CPU 6 is now offline
Nov 07 21:15:29 my-ntb kernel: smpboot: CPU 7 is now offline
Nov 07 21:15:29 my-ntb kernel: ACPI: PM: Low-level resume complete
Nov 07 21:15:29 my-ntb kernel: ACPI: EC: EC started
Nov 07 21:15:29 my-ntb kernel: ACPI: PM: Restoring platform NVS memory
Nov 07 21:15:29 my-ntb kernel: Enabling non-boot CPUs ...
Nov 07 21:15:29 my-ntb kernel: x86: Booting SMP configuration:
Nov 07 21:15:29 my-ntb kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Nov 07 21:15:29 my-ntb kernel: CPU1 is upthanks
Jan
Offline
I believe this is normal. At least, I have always seen similar things in the journal. My assumption has been that some of the logging messages are generated after the disk has been synced, so don't get written until the machine is woken back up. I'm guessing the timestamps are generated at the time the messages are written rather than the time the messages are generated.
Doubtless one of the experts will say whether this is correct or not, but sleep works well on this machine and the odd timestamps have always been there, as far as I can recall.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline