Why sometimes fedora Log out when in Sleep state and stop recognizing my second monitor?

So , i basically never turn off computer and put it to sleep during the night.
But sometimes when i wake it up in the morning it is in log out state and closed all opened apps, Its kinda annoying
Idk why sometimes this behavior happens

Also, usually when this happens, fedora stop recognizing my second monitor, so i have to reboot to it be recognize again

Using fedora Silverblue 39

Is it set up to do automatic updates.?
There are certain packages that require a reboot when updated (such as the kernel) so the automatic update does the reboot for you.

Yes, but since im in silverblue, i only saw it automatic updating flatpaks that dont require reboot, didnt know it could reboot the system

So i gonna turn it off and see if solves
thanks bro !

Hey jeff, i disabled automatic updates and it still happened today.
What can i do to may find the issue ?
its impacting my usability a lot, sometimes only 30 min sleeping cause this bug. When i woke the pc looks like i did a cold start with all apps closed and my second monitor not working, so i have to reboot it to make second monitor work again

@crazymonkey Please post your hardware config :

inxi -FGxx

I already saw the other post, so I hope @mods can bring it here. It’s just a little confusing is all.
I am going through those and will post back in a moment.

Sure, and sorry if cross the line of good manners here in the forum.

im in silverblue, so i have to layer and reboot, but i cant reboot now because of some work opened here, do you mind if i ping you later with this info ?

1 Like

soldier hammerhead, im facing the same issue of Benyamin, could be something related to Dell laptops, gonna post my results here also

Also every time these issues happens, my second monitor stop to receive video, and it is connected to hdmi port that is attached to nvdia graphics card, second to dell, so i have to reboot again to video start working on second monitor. Maybe is something with nvidia

abr 20 11:21:52 fedora systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
abr 20 11:22:03 fedora systemd[1]: Starting rpc-statd-notify.service - Notify NFS peers of a restart...
abr 20 11:22:03 fedora systemd[1]: Started rpc-statd-notify.service - Notify NFS peers of a restart.
abr 20 17:08:26 fedora NetworkManager[1317]: <info>  [1713643706.2148] device (wlp4s0): ip:dhcp4: restarting
abr 21 22:04:07 fedora systemd[2216]: org.gnome.SettingsDaemon.Keyboard.service: Scheduled restart job, restart counter is at 1.
abr 21 22:04:07 fedora systemd[2216]: org.gnome.SettingsDaemon.MediaKeys.service: Scheduled restart job, restart counter is at 1.
abr 21 22:04:07 fedora systemd[2216]: org.gnome.SettingsDaemon.Wacom.service: Scheduled restart job, restart counter is at 1.
abr 21 22:04:07 fedora systemd[2216]: org.gnome.SettingsDaemon.Power.service: Scheduled restart job, restart counter is at 1.
abr 21 22:04:07 fedora systemd[2216]: org.gnome.SettingsDaemon.Color.service: Scheduled restart job, restart counter is at 1.
abr 21 22:04:07 fedora systemd[2216]: org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, restart counter is at 1.
abr 21 22:04:07 fedora systemd[2216]: Starting gnome-session-restart-dbus.service - Restart DBus after GNOME Session shutdown...
abr 21 22:04:07 fedora systemd[2216]: Started gnome-session-restart-dbus.service - Restart DBus after GNOME Session shutdown.
abr 21 22:05:24 fedora systemd[188649]: Starting gnome-session-restart-dbus.service - Restart DBus after GNOME Session shutdown...
abr 21 22:05:24 fedora systemd[188649]: Started gnome-session-restart-dbus.service - Restart DBus after GNOME Session shutdown.

[    2.603441] nouveau 0000:01:00.0: NVIDIA TU117 (167000a1)
[   19.878048] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input26
[   19.878170] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input27
[   19.878257] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input28
[   19.878342] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input29
[    0.756658] pcieport 0000:00:1d.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    0.757019] pcieport 0000:00:1d.5: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    0.757351] pcieport 0000:00:1d.6: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    1.155028] RAS: Correctable Errors collector initialized.
[   20.126965] pcieport 0000:00:1d.6: AER: Multiple Correctable error message received from 0000:00:1d.6
[   20.126989] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   20.126992] pcieport 0000:00:1d.6:   device [8086:a336] error status/mask=00000081/00002000
[   20.126999] pcieport 0000:00:1d.6: AER:   Error of this Agent is reported first
[   20.127008] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Transmitter ID)
[   20.127010] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00001181/00006000
[   20.127044] pcieport 0000:00:1d.6: AER: Multiple Correctable error message received from 0000:00:1d.6
[   20.127057] pcieport 0000:00:1d.6: AER: found no error details for 0000:00:1d.6
[   20.127059] pcieport 0000:00:1d.6: AER: Multiple Correctable error message received from 0000:00:1d.6
[   20.127074] pcieport 0000:00:1d.6: AER: found no error details for 0000:00:1d.6
[   20.157190] pcieport 0000:00:1d.6: AER: Multiple Correctable error message received from 0000:00:1d.6
[   20.157214] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   20.157217] pcieport 0000:00:1d.6:   device [8086:a336] error status/mask=00000001/00002000
[   20.157222] pcieport 0000:00:1d.6: AER:   Error of this Agent is reported first
[   20.157228] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Transmitter ID)
[   20.157230] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00001001/00006000
[   20.157251] pcieport 0000:00:1d.6: AER: Multiple Correctable error message received from 0000:00:1d.6
[   20.157266] pcieport 0000:00:1d.6: AER: found no error details for 0000:00:1d.6
[   23.653699] pcieport 0000:00:1d.6: AER: Multiple Correctable error message received from 0000:00:1d.6
[   23.653734] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   23.653741] pcieport 0000:00:1d.6:   device [8086:a336] error status/mask=00000081/00002000
[   23.653761] pcieport 0000:00:1d.6: AER:   Error of this Agent is reported first
[   23.653773] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Transmitter ID)
[   23.653779] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00001101/00006000
[   23.653827] pcieport 0000:00:1d.6: AER: Multiple Correctable error message received from 0000:04:00.0
[   23.684620] pcieport 0000:00:1d.6: AER: Multiple Correctable error message received from 0000:00:1d.6
[   23.684687] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   23.684695] pcieport 0000:00:1d.6:   device [8086:a336] error status/mask=00000001/00002000
[   23.684710] pcieport 0000:00:1d.6: AER:   Error of this Agent is reported first
[   23.684723] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Transmitter ID)
[   23.684729] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00001101/00006000
[   23.996368] pcieport 0000:00:1d.6: AER: Multiple Correctable error message received from 0000:00:1d.6
[   23.996405] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   23.996412] pcieport 0000:00:1d.6:   device [8086:a336] error status/mask=00000001/00002000
[   23.996427] pcieport 0000:00:1d.6: AER:   Error of this Agent is reported first
[   23.996440] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Transmitter ID)
[   23.996446] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00001081/00006000
[   24.028070] pcieport 0000:00:1d.6: AER: Multiple Correctable error message received from 0000:00:1d.6
[   24.028115] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[   24.028123] pcieport 0000:00:1d.6:   device [8086:a336] error status/mask=00000041/00002000
[   24.028143] pcieport 0000:00:1d.6: AER:   Error of this Agent is reported first
[   24.028155] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Transmitter ID)
[   24.028161] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00001101/00006000
[31398.631541] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[31398.631618] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[31398.631626] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[36628.915949] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[36628.915977] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[36628.915986] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[36840.883314] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[36840.883343] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[36840.883352] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[37347.748508] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[37347.748597] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[37347.748605] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[39433.639710] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[39433.639979] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[39433.639988] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[40964.917067] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[40964.917184] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[40964.917187] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[43551.301014] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[43551.301162] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[43551.301172] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[44401.651684] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[44401.651699] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[44401.651701] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[47185.144652] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[47185.144771] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[47185.144774] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[47927.451334] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe B (start=595556 end=595557) time 140 us, min 1071, max 1079, scanline start 1068, end 1080
[48450.044961] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe B (start=634746 end=634747) time 189 us, min 1071, max 1079, scanline start 1066, end 1082
[49928.141862] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[49928.141890] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[49928.141898] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[52170.807490] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe B (start=913771 end=913772) time 146 us, min 1071, max 1079, scanline start 1069, end 1081
[58068.134727] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[58068.134855] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[58068.134864] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[63138.278993] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[63138.279121] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[63138.279130] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[67369.128996] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[67369.129025] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[67369.129033] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000
[69391.635947] pcieport 0000:00:1d.6: AER: Correctable error message received from 0000:04:00.0
[69391.635975] ath10k_pci 0000:04:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)
[69391.635983] ath10k_pci 0000:04:00.0:   device [168c:0042] error status/mask=00000080/00006000

mar 19 10:57:55 fedora pipewire[2635]: pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink-49) suspended -> error (Start error: Invalid argument)
mar 19 10:58:00 fedora pipewire[2635]: pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink-49) suspended -> error (Start error: Invalid argument)
mar 19 10:58:05 fedora pipewire[2635]: pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink-49) suspended -> error (Start error: Invalid argument)
mar 19 10:58:10 fedora pipewire[2635]: pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink-49) suspended -> error (Start error: Invalid argument)
mar 19 10:58:15 fedora pipewire[2635]: pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink-49) suspended -> error (Start error: Invalid argument)
mar 19 10:58:20 fedora pipewire[2635]: pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink-49) suspended -> error (Start error: Invalid argument)
mar 19 10:59:13 fedora kernel: Low-power S0 idle used by default for system suspend
mar 19 10:59:13 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
mar 19 20:49:45 fedora kernel: Low-power S0 idle used by default for system suspend
mar 19 20:49:45 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
mar 27 21:54:45 fedora kernel: Low-power S0 idle used by default for system suspend
mar 27 21:54:46 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
mar 27 22:03:09 fedora kernel: Low-power S0 idle used by default for system suspend
mar 27 22:03:10 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
mar 27 22:09:31 fedora kernel: Low-power S0 idle used by default for system suspend
mar 27 22:09:31 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
mar 29 13:40:42 fedora kernel: Low-power S0 idle used by default for system suspend
mar 29 13:40:42 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
abr 08 13:04:17 fedora kernel: Low-power S0 idle used by default for system suspend
abr 08 13:04:18 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
abr 11 17:06:13 fedora flatpak[353734]:     <suspend-to-mem enabled="no"/>
abr 11 17:06:13 fedora flatpak[353734]:     <suspend-to-disk enabled="no"/>
abr 11 18:55:02 fedora kernel: Low-power S0 idle used by default for system suspend
abr 11 18:55:02 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
abr 11 19:02:50 fedora kernel: Low-power S0 idle used by default for system suspend
abr 11 19:02:50 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
abr 11 19:15:06 fedora kernel: Low-power S0 idle used by default for system suspend
abr 11 19:15:06 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
abr 14 06:07:50 fedora kernel:  nouveau_do_suspend+0xf5/0x280 [nouveau]
abr 14 06:07:50 fedora kernel:  nouveau_pmops_runtime_suspend+0x3e/0xb0 [nouveau]
abr 14 06:07:50 fedora kernel:  pci_pm_runtime_suspend+0x67/0x1e0
abr 14 06:07:50 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 14 06:07:50 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 14 06:07:50 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 14 06:07:50 fedora kernel:  rpm_suspend+0x120/0x6a0
abr 14 06:07:50 fedora kernel:  nouveau_do_suspend+0xf5/0x280 [nouveau]
abr 14 06:07:50 fedora kernel:  nouveau_pmops_runtime_suspend+0x3e/0xb0 [nouveau]
abr 14 06:07:50 fedora kernel:  pci_pm_runtime_suspend+0x67/0x1e0
abr 14 06:07:50 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 14 06:07:50 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 14 06:07:50 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 14 06:07:50 fedora kernel:  rpm_suspend+0x120/0x6a0
abr 14 06:07:50 fedora kernel: nouveau 0000:01:00.0: gsp: suspend failed, -12
abr 14 06:07:50 fedora kernel: nouveau: DRM-master:00000000:00000080: suspend failed with -12
abr 14 06:07:50 fedora kernel: nouveau 0000:01:00.0: can't suspend (nouveau_pmops_runtime_suspend [nouveau] returned -12)
abr 14 06:25:04 fedora systemd-logind[1169]: The system will suspend now!
abr 14 06:25:04 fedora ModemManager[1257]: <info>  [sleep-monitor-systemd] system is about to suspend
abr 14 06:25:05 fedora systemd[1]: Starting systemd-suspend.service - System Suspend...
abr 14 06:25:05 fedora systemd-sleep[239048]: Entering sleep state 'suspend'...
abr 14 06:25:05 fedora kernel: PM: suspend entry (s2idle)
abr 14 10:21:43 fedora kernel: printk: Suspending console(s) (use no_console_suspend to debug)
abr 14 10:21:43 fedora kernel: PM: suspend devices took 0.120 seconds
abr 14 10:21:43 fedora kernel: PM: suspend exit
abr 14 10:21:43 fedora systemd[1]: systemd-suspend.service: Deactivated successfully.
abr 14 10:21:43 fedora systemd[1]: Finished systemd-suspend.service - System Suspend.
abr 14 10:21:43 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
abr 14 10:21:43 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
abr 14 10:21:43 fedora systemd[1]: Reached target suspend.target - Suspend.
abr 14 10:21:43 fedora systemd[1]: Stopped target suspend.target - Suspend.
abr 14 10:35:11 fedora kernel: Low-power S0 idle used by default for system suspend
abr 14 10:35:11 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
abr 20 06:00:27 fedora kernel:  nouveau_do_suspend+0xf5/0x280 [nouveau]
abr 20 06:00:27 fedora kernel:  nouveau_pmops_runtime_suspend+0x3e/0xb0 [nouveau]
abr 20 06:00:27 fedora kernel:  pci_pm_runtime_suspend+0x67/0x1e0
abr 20 06:00:27 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 20 06:00:27 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 20 06:00:27 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 20 06:00:27 fedora kernel:  rpm_suspend+0x120/0x6a0
abr 20 06:00:27 fedora kernel:  nouveau_do_suspend+0xf5/0x280 [nouveau]
abr 20 06:00:27 fedora kernel:  nouveau_pmops_runtime_suspend+0x3e/0xb0 [nouveau]
abr 20 06:00:27 fedora kernel:  pci_pm_runtime_suspend+0x67/0x1e0
abr 20 06:00:27 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 20 06:00:27 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 20 06:00:27 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 20 06:00:27 fedora kernel:  rpm_suspend+0x120/0x6a0
abr 20 06:00:27 fedora kernel: nouveau 0000:01:00.0: gsp: suspend failed, -12
abr 20 06:00:27 fedora kernel: nouveau: DRM-master:00000000:00000080: suspend failed with -12
abr 20 06:00:27 fedora kernel: nouveau 0000:01:00.0: can't suspend (nouveau_pmops_runtime_suspend [nouveau] returned -12)
abr 20 06:28:00 fedora systemd-logind[1234]: The system will suspend now!
abr 20 06:28:00 fedora ModemManager[1323]: <info>  [sleep-monitor-systemd] system is about to suspend
abr 20 06:28:01 fedora systemd[1]: Starting systemd-suspend.service - System Suspend...
abr 20 06:28:01 fedora systemd-sleep[628818]: Entering sleep state 'suspend'...
abr 20 06:28:01 fedora kernel: PM: suspend entry (s2idle)
abr 20 10:07:49 fedora kernel: printk: Suspending console(s) (use no_console_suspend to debug)
abr 20 10:07:49 fedora kernel: PM: suspend devices took 0.130 seconds
abr 20 10:07:49 fedora kernel: PM: suspend exit
abr 20 10:07:49 fedora systemd[1]: systemd-suspend.service: Deactivated successfully.
abr 20 10:07:49 fedora systemd[1]: Finished systemd-suspend.service - System Suspend.
abr 20 10:07:49 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
abr 20 10:07:49 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
abr 20 10:07:49 fedora systemd[1]: Reached target suspend.target - Suspend.
abr 20 10:07:49 fedora systemd[1]: Stopped target suspend.target - Suspend.
abr 20 11:21:22 fedora kernel: Low-power S0 idle used by default for system suspend
abr 20 11:21:22 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
abr 21 21:59:13 fedora kernel:  nouveau_do_suspend+0xf5/0x280 [nouveau]
abr 21 21:59:13 fedora kernel:  nouveau_pmops_runtime_suspend+0x3e/0xb0 [nouveau]
abr 21 21:59:13 fedora kernel:  pci_pm_runtime_suspend+0x67/0x1e0
abr 21 21:59:13 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 21 21:59:13 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 21 21:59:13 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 21 21:59:13 fedora kernel:  rpm_suspend+0x120/0x6a0
abr 21 21:59:13 fedora kernel:  nouveau_do_suspend+0xf5/0x280 [nouveau]
abr 21 21:59:13 fedora kernel:  nouveau_pmops_runtime_suspend+0x3e/0xb0 [nouveau]
abr 21 21:59:13 fedora kernel:  pci_pm_runtime_suspend+0x67/0x1e0
abr 21 21:59:13 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 21 21:59:13 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 21 21:59:13 fedora kernel:  ? __pfx_pci_pm_runtime_suspend+0x10/0x10
abr 21 21:59:13 fedora kernel:  rpm_suspend+0x120/0x6a0
abr 21 21:59:13 fedora kernel: nouveau 0000:01:00.0: gsp: suspend failed, -12
abr 21 21:59:13 fedora kernel: nouveau: DRM-master:00000000:00000080: suspend failed with -12
abr 21 21:59:13 fedora kernel: nouveau 0000:01:00.0: can't suspend (nouveau_pmops_runtime_suspend [nouveau] returned -12)
abr 21 22:06:16 fedora kernel: Low-power S0 idle used by default for system suspend
abr 21 22:06:16 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
abr 21 22:06:16 fedora kernel: Low-power S0 idle used by default for system suspend
abr 21 22:06:16 fedora kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend

From your :

dmesg | grep -i error

[ 20.126989] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID): The PCIe Bus Error is identified as having a severity level of Correctable, with the type being Physical Layer.

and :

[ 47927.451334] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe B (start=595556 end=595557) time 140 us, min 1071, max 1079, scanline start 1068, end 1080: This line indicates an error related to the i915 driver, which is responsible for Intel integrated graphics. Maybe why yuo are having issues with the monitor. . .

From your :

journalctl | grep -i suspend

mar 19 10:57:55 fedora pipewire[2635]: pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink-49) suspended -> error (Start error: Invalid argument)
mar 19 10:58:00 fedora pipewire[2635]: pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink-49) suspended -> error (Start error: Invalid argument)
mar 19 10:58:05 fedora pipewire[2635]: pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink-49) suspended -> error (Start error: Invalid argument)
mar 19 10:58:10 fedora pipewire[2635]: pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink-49) suspended -> error (Start error: Invalid argument)
mar 19 10:58:15 fedora pipewire[2635]: pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink-49) suspended -> error (Start error: Invalid argument)
mar 19 10:58:20 fedora pipewire[2635]: pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink-49) suspended -> error (Start error: Invalid argument)

It seems like there are issues with system suspends and errors related to audio and GPU . The logs show errors like “Start error: Invalid argument” and failures during suspend operations. These errors involve Pipewire, and Nouveau.

Check Device Drivers: Ensure that your audio and GPU drivers are up to date

Check the status of Pipewire service:

systemctl status pipewire

Also check GPU :

lspci -k | grep -EA3 'VGA|3D|Display'

You were asked to show the output of inxi -Fzxx which we have not seen yet. That will give us a lot of info about devices and drivers and may be critical to solving this issue.

Also note that fedora has, for several releases now, enabled auto-suspend after 15 minutes idle and this may also be related. We need the info requested to be able to assist in analyzing the events as they occur.

1 Like
System:
  Kernel: 6.8.6-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.40-14.fc39
  Desktop: GNOME v: 45.5 tk: GTK v: 3.24.41 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 39.20240421.0 (Silverblue)
Machine:
  Type: Laptop System: Dell product: G3 3590 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Dell model: 0GDFK2 v: A00 serial: <superuser required> part-nu: 0949
    UEFI: Dell v: 1.21.0 date: 04/10/2023
Battery:
  ID-1: BAT0 charge: 34.3 Wh (100.0%) condition: 34.3/51.0 Wh (67.2%)
    volts: 12.3 min: 11.4 model: LGC-LGC4.474 DELL 415CG01 serial: <filter>
    status: full
CPU:
  Info: quad core model: Intel Core i5-9300H bits: 64 type: MT MCP
    arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 900 min/max: 800/4100 cores: 1: 900 2: 900 3: 900 4: 900
    5: 900 6: 900 7: 900 8: 900 bogomips: 38400
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Dell
    driver: i915 v: kernel arch: Gen-9.5 ports: active: DP-1 off: eDP-1
    empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:3e9b
  Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: Dell
    driver: nouveau v: kernel arch: Turing pcie: speed: 2.5 GT/s lanes: 8 ports:
    active: HDMI-A-2 empty: none bus-ID: 01:00.0 chip-ID: 10de:1f91
  Device-3: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-5:8 chip-ID: 0c45:671f
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.4
    compositor: gnome-shell driver: gpu: i915,nouveau display-ID: 0
  Monitor-1: DP-1 model: LG (GoldStar) ULTRAWIDE res: 2560x1080 dpi: 81
    diag: 869mm (34.2")
  Monitor-2: HDMI-A-2 model: AOC 27B1G5 res: 1920x1080 dpi: 82
    diag: 686mm (27")
  Monitor-3: eDP-1 model: BOE Display 0x0819 res: 1920x1080 dpi: 142
    diag: 395mm (15.5")
  API: OpenGL v: 4.6 vendor: intel mesa v: 23.3.6 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
    device-ID: 8086:3e9b display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Dell
    driver: sof-audio-pci-intel-cnl bus-ID: 00:1f.3 chip-ID: 8086:a348
  Device-2: NVIDIA vendor: Dell driver: snd_hda_intel v: kernel pcie:
    speed: 2.5 GT/s lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:10fa
  API: ALSA v: k6.8.6-200.fc39.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Dell driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
    vendor: Dell driver: ath10k_pci v: kernel pcie: speed: 2.5 GT/s lanes: 1
    bus-ID: 04:00.0 chip-ID: 168c:0042
  IF: wlp4s0 state: up mac: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 1-14:9 chip-ID: 0cf3:e009
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
    lmp-v: 8
Drives:
  Local Storage: total: 1.83 TiB used: 649.32 GiB (34.6%)
  ID-1: /dev/nvme0n1 vendor: A-Data model: IM2P33F3 NVMe 512GB
    size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 38.9 C
  ID-2: /dev/sda vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
    speed: 6.0 Gb/s serial: <filter>
  ID-3: /dev/sdb vendor: Western Digital model: WD10SDRW-11A0XS0
    size: 931.48 GiB type: USB rev: 2.1 spd: 480 Mb/s lanes: 1 serial: <filter>
Partition:
  ID-1: /boot size: 973.4 MiB used: 281 MiB (28.9%) fs: ext4 dev: /dev/sda2
  ID-2: /boot/efi size: 598.8 MiB used: 11.6 MiB (1.9%) fs: vfat
    dev: /dev/sda1
  ID-3: /var size: 464.16 GiB used: 65.3 GiB (14.1%) fs: btrfs
    dev: /dev/dm-0 mapped: luks-a79c02a1-318c-4e9b-9cff-ff6637c3e224
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 66.0 C pch: 60.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB available: 15.46 GiB used: 3.7 GiB (23.9%)
  Processes: 390 Power: uptime: 1m wakeups: 0 Init: systemd v: 254
    target: graphical (5) default: graphical
  Packages: pm: flatpak pkgs: 60 Compilers: N/A Shell: Bash v: 5.2.26
    running-in: gnome-terminal inxi: 3.3.33

idk why pipewire.service didnt appear though

Unit pipewire.service could not be found.
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630]
	DeviceName: Onboard - Video
	Subsystem: Dell Device 0949
	Kernel driver in use: i915
--
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1)
	Subsystem: Dell Device 0949
	Kernel driver in use: nouveau
	Kernel modules: nouveau

1 Like

that information is not true, its 29 , but gnome say 34

I turn off auto-suspend months ago

So what we know so far is you don’t have the Nvidia driver & Pipewaire are not working properly. . . Coincides with the logs you provided. Did you intend on not using The Nvidia Driver ? Also, do you recall removing Pipewire?

About Nvidia Driver:

Before installing fedora i searched in forums about which nvidia driver use, i saw some folks recommending nouveau, thats why im using (i think the proprietary had some bugs with wayland) but i dont have anything against the proprietary

About Pipewire:

rpm-ostree status

● fedora:fedora/39/x86_64/silverblue
                  Version: 39.20240421.0 (2024-04-21T00:40:03Z)
               BaseCommit: f94f3bb414bdde995d1f9328613b7d20b3fdad0e9a84b41d9de9661ea9440a6b
             GPGSignature: Valid signature by E8F23996F23218640CB44CBE75CF5AC418B8E74C
      RemovedBasePackages: firefox firefox-langpacks 125.0-1.fc39
          LayeredPackages: inxi openssl

As you see, i didnt removed pipewire (only firefox because i use the flatpak version)

more informations:

systemctl status

fedora
    State: degraded
    Units: 567 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 1 units
    Since: Mon 2024-04-22 21:54:54 -03; 12h ago
  systemd: 254.10-1.fc39
   CGroup: /
           ├─init.scope
           │ └─1 /usr/lib/systemd/systemd --switched-root --system --deserialize=40 rhgb
           ├─system.slice
           │ ├─ModemManager.service
           │ │ └─1324 /usr/sbin/ModemManager
           │ ├─NetworkManager.service
           │ │ ├─1336 /usr/sbin/NetworkManager --no-daemon
           │ │ └─1564 /usr/sbin/dnsmasq --conf-file=/dev/null --no-hosts --keep-in-foreground --bind-interfaces --except-interface=lo --clear-on>
           │ ├─accounts-daemon.service
           │ │ └─1234 /usr/libexec/accounts-daemon
           │ ├─auditd.service
           │ │ └─1136 /sbin/auditd
           │ ├─avahi-daemon.service
           │ │ ├─1206 "avahi-daemon: running [fedora.local]"
           │ │ └─1251 "avahi-daemon: chroot helper"
           │ ├─bluetooth.service
           │ │ └─1207 /usr/libexec/bluetooth/bluetoothd
           │ ├─chronyd.service
           │ │ └─1222 /usr/sbin/chronyd -F 2
           │ ├─colord.service
           │ │ └─1432 /usr/libexec/colord
           │ ├─cups.service
           │ │ └─1416 /usr/sbin/cupsd -l
           │ ├─dbus-broker.service
           │ │ ├─1204 /usr/bin/dbus-broker-launch --scope system --audit
           │ │ └─1205 dbus-broker --log 4 --controller 9 --machine-id 7eb2ef2f96cc4ba1bfa75f81f8058376 --max-bytes 536870912 --max-fds 4096 --ma>
           │ ├─firewalld.service
           │ │ └─1326 /usr/bin/python3 -sP /usr/sbin/firewalld --nofork --nopid
lines 1-36

ps -e | grep pipewire

   2409 ?        00:00:00 pipewire
   3211 ?        00:00:00 pipewire-pulse

Well, let’s get you squared away with that. There are several ways to do this, but the more supported way here on the forums is the RPMFusion. I think you can just go ahead and enable the repo in the Software Center.

https://rpmfusion.org/Howto/NVIDIA#OSTree_.28Silverblue.2FKinoite.2Fetc.29

Do you have SecureBoot enabled? If so you will need to sign the driver and there are plenty of instructions/help here for that. @computersavvy can jump in and help.

1 Like