Dell 3410 GP108M [GeForce MX230] like to restart without any explanation after sleeps, then boot and sleeps again

Hello, I’m quite confuse with my Dell 3140 from my employer that use fedora. For random time, it keep restarting randomly after sleep, but not always restarting, but often restarting and I lost some of the data while restaring without user consent.

I only got some of the logs and well it only show this in journalctl output

Apr 21 16:59:19 HLLTP005 geoclue[4242]: WiFi scan failed
Apr 21 16:59:19 HLLTP005 NetworkManager[920]: <info>  [1713693559.5809] device (wlp0s20f3): set-hw-addr: reset MAC address to D8:F8:83:E5:98:77 (unmanage)
Apr 21 16:59:19 HLLTP005 wpa_supplicant[1223]: p2p-dev-wlp0s20: CTRL-EVENT-DSCP-POLICY clear_all
Apr 21 16:59:19 HLLTP005 wpa_supplicant[1223]: p2p-dev-wlp0s20: CTRL-EVENT-DSCP-POLICY clear_all
Apr 21 16:59:19 HLLTP005 wpa_supplicant[1223]: nl80211: deinit ifname=p2p-dev-wlp0s20 disabled_11b_rates=0
Apr 21 16:59:19 HLLTP005 systemd[1]: Reached target sleep.target - Sleep.
Apr 21 16:59:19 HLLTP005 wpa_supplicant[1223]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
Apr 21 16:59:19 HLLTP005 systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
Apr 21 16:59:19 HLLTP005 suspend[44662]: nvidia-suspend.service
Apr 21 16:59:19 HLLTP005 wpa_supplicant[1223]: p2p-dev-wlp0s20: CTRL-EVENT-DSCP-POLICY clear_all
Apr 21 16:59:19 HLLTP005 wpa_supplicant[1223]: p2p-dev-wlp0s20: CTRL-EVENT-DSCP-POLICY clear_all
Apr 21 16:59:19 HLLTP005 wpa_supplicant[1223]: nl80211: deinit ifname=p2p-dev-wlp0s20 disabled_11b_rates=0
Apr 21 16:59:19 HLLTP005 systemd[1]: Reached target sleep.target - Sleep.
Apr 21 16:59:19 HLLTP005 wpa_supplicant[1223]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
Apr 21 16:59:19 HLLTP005 systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
Apr 21 16:59:19 HLLTP005 suspend[44662]: nvidia-suspend.service
Apr 21 16:59:19 HLLTP005 logger[44662]: <13>Apr 21 16:59:19 suspend: nvidia-suspend.service
Apr 21 16:59:19 HLLTP005 wpa_supplicant[1223]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
Apr 21 16:59:19 HLLTP005 wpa_supplicant[1223]: nl80211: deinit ifname=wlp0s20f3 disabled_11b_rates=0
Apr 21 16:59:19 HLLTP005 warp-svc[985]: 2024-04-21T09:59:19.631Z DEBUG warp::warp_service::network_change: Routes changed:
Apr 21 16:59:19 HLLTP005 warp-svc[985]: DelNeighbour; Destination: 224.0.0.22;
Apr 21 16:59:19 HLLTP005 kernel: rfkill: input handler enabled
Apr 21 16:59:19 HLLTP005 gsd-media-keys[4259]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Apr 21 16:59:19 HLLTP005 gsd-media-keys[4259]: Unable to get default sink
Apr 21 16:59:19 HLLTP005 gsd-media-keys[4259]: Unable to get default source
Apr 21 16:59:19 HLLTP005 systemd[1]: nvidia-suspend.service: Deactivated successfully.
Apr 21 16:59:19 HLLTP005 systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
Apr 21 16:59:19 HLLTP005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 21 16:59:19 HLLTP005 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 21 16:59:19 HLLTP005 systemd[1]: Starting systemd-suspend.service - System Suspend...
Apr 21 16:59:19 HLLTP005 systemd-sleep[44695]: Entering sleep state 'suspend'...
Apr 21 16:59:19 HLLTP005 kernel: PM: suspend entry (deep)
-- Boot 9c3dc7fab8e0480198b1212e7a2ce3d2 --
Apr 21 16:59:46 HLLTP005 kernel: Linux version 6.8.6-200.fc39.x86_64 (mockbuild@123c7438b1ed42b3b926d06cfeba7397) (gcc (GCC) 13.2.1 20240316 (Red Hat 13.2.1-7), GNU ld version 2.40-14.fc39) #1 SMP PREEMPT_DYNAM>
Apr 21 16:59:46 HLLTP005 kernel: Command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.8.6-200.fc39.x86_64 root=UUID=7ef5a715-99b7-4fbf-81ad-0ee01a2eb25a ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.bl>
Apr 21 16:59:46 HLLTP005 kernel: BIOS-provided physical RAM map:
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000072f3afff] usable
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x0000000072f3b000-0x0000000072f3bfff] ACPI NVS
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x0000000072f3c000-0x0000000072f3cfff] reserved
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x0000000072f3d000-0x0000000084725fff] usable
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x0000000084726000-0x00000000877b4fff] reserved
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x00000000877b5000-0x0000000087e24fff] ACPI NVS
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x0000000087e25000-0x0000000087efefff] ACPI data
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x0000000087eff000-0x0000000087efffff] usable
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x0000000087f00000-0x000000008f7fffff] reserved
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Apr 21 16:59:46 HLLTP005 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000086c7fffff] usable

and It happen multiple times

Apr 20 19:05:28 HLLTP005 dbeaver-ce.desktop[7450]: 2024-04-20 19:05:28.596 - Invalidate datasource 'UAT Space' connections...
Apr 20 19:05:28 HLLTP005 dbeaver-ce.desktop[7450]: 2024-04-20 19:05:28.596 - Invalidate datasource 'UAT Space' (mysql8-18ef5cdd87e-409e3be9b4cbeb76)
Apr 20 19:05:28 HLLTP005 dbeaver-ce.desktop[7450]: 2024-04-20 19:05:28.596 -         Invalidate context 'Main' for mysql8-18ef5cdd87e-409e3be9b4cbeb76
Apr 20 19:05:28 HLLTP005 dbeaver-ce.desktop[7450]: 2024-04-20 19:05:28.598 -         Failed: Communications link failure
Apr 20 19:05:28 HLLTP005 dbeaver-ce.desktop[7450]: The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
Apr 20 19:05:28 HLLTP005 dbeaver-ce.desktop[7450]: 2024-04-20 19:05:28.598 -         Invalidate context 'Metadata' for mysql8-18ef5cdd87e-409e3be9b4cbeb76
Apr 20 19:05:28 HLLTP005 dbeaver-ce.desktop[7450]: 2024-04-20 19:05:28.600 -         Failed: Communications link failure
Apr 20 19:05:28 HLLTP005 dbeaver-ce.desktop[7450]: The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
Apr 20 19:05:28 HLLTP005 dbeaver-ce.desktop[7450]: 2024-04-20 19:05:28.600 -         Invalidate context 'SQLEditor <Script-5.sql>' for mysql8-18ef5cdd87e-409e3be9b4cbeb76
Apr 20 19:05:28 HLLTP005 dbeaver-ce.desktop[7450]: 2024-04-20 19:05:28.602 -         Failed: Communications link failure
Apr 20 19:05:28 HLLTP005 dbeaver-ce.desktop[7450]: The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
Apr 20 19:05:28 HLLTP005 kernel: PM: suspend entry (deep)
Apr 20 19:05:28 HLLTP005 systemd-sleep[33679]: Entering sleep state 'suspend'...
-- Boot b4cf24b3a2c34e35a9321b8267f38088 --
Apr 20 19:05:55 HLLTP005 kernel: Linux version 6.8.6-200.fc39.x86_64 (mockbuild@123c7438b1ed42b3b926d06cfeba7397) (gcc (GCC) 13.2.1 20240316 (Red Hat 13.2.1-7), GNU ld version 2.40-14.fc39) #1 SMP PREEMPT_DYNAM>
Apr 20 19:05:55 HLLTP005 kernel: Command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.8.6-200.fc39.x86_64 root=UUID=7ef5a715-99b7-4fbf-81ad-0ee01a2eb25a ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.bl>
Apr 20 19:05:55 HLLTP005 kernel: BIOS-provided physical RAM map:

I don’t even press the power button and others as I’m not touching the laptop, and I don’t use s0ix but using S3 sleeps…

I attach the whole logs of journalctl at the attachment. If there anyone know to debug it further, please do help. I never encounter this problem on other laptop or other Fedora installation.

Thank you
random-restart.log.tar.gz

EDIT: I also look into this Why sometimes fedora Log out when in Sleep state and stop recognizing my second monitor?, But I’m not sure of this, so I will try to disable it first, but as the other poster said that it also still rebooting even after disabling it.

EDIT 2: I check the docs, and I don’t see any dnf-automatic.timer on the services Automatic Updates :: Fedora Docs
Is there any other config to auto update?

Bro i write this post, disable automatic updates didnt change anything

Also, my notebook is a Dell (Dell 3590)

Gonna ping fedora veteran soldiers in this community , maybe they know something to help us identify the cause

@computersavvy
@jakfrost
@hamrheadcorvette

Yeah, I mention it here as I seen you also facing the same problem and I check I don’t have automatic update. So I just think it isn’t for my case, but mentioning sometimes worth for other in the future if they are facing the same problem.

rest assure, the guys mentioned above fix everything about fedora in here

Hello @benlimanto ,
Does this laptop come pre-installed with Fedora? Or does your employer install Fedora for you? Possibly with inxi, something like inxi -v 3 in the commandline should give good details about your system to help you figure out the issue. Please try the command and post results here. It is a good place to start. Also, if you don’t already have it installed, it will need to be installed with sudo dnf install inxi

1 Like

Stephen, im facing the same issue but with silverblue, if i install the package through toolbox the results would be reliable to identify the cause or need to layer it ?

I had a “similar” problem with a Dell Vostro laptop.
It was a thermal event.
After cleaning up the blower, everything went fine.

1 Like

Anything in Toolbox is/will be container influenced, it just isn’t a complete OS stack. And it won’t report reliable results from inxi about the host system.

Layering, I’m not sure what needs to be layered in this case as it is a power management related problem, and …
like @ycollet is noting, this issue could be related to thermal management. I have read posts here about some modes causing excessive fan speed, or no fan operation, depending on the case and the powersave mode settings.

If @benlimanto has this system as an atomic version (or you want to use inxi on Silverblue) then the command for inxi install would be rpm-ostree install inxi.

No, it come preinstalled with Ubuntu, I install fedora myself as it’s fine to switch between distro for now

ben@HLLTP005 ~$ inxi -v 3
System:
  Host: HLLTP005 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 Distro: Fedora Linux 39 (Workstation Edition)
Machine:
  Type: Laptop System: Dell product: Latitude 3410 v: N/A
    serial: <superuser required>
  Mobo: Dell model: 03C8WJ v: A03 serial: <superuser required> UEFI: Dell
    v: 1.28.0 date: 03/07/2024
Battery:
  ID-1: BAT0 charge: 32.0 Wh (100.0%) condition: 32.0/39.8 Wh (80.4%)
    volts: 12.5 min: 11.2 model: BYD DELL CF5RH0B status: full
CPU:
  Info: quad core model: Intel Core i5-10210U bits: 64 type: MT MCP
    arch: Comet/Whiskey Lake note: check rev: C cache: L1: 256 KiB L2: 1024 KiB
    L3: 6 MiB
  Speed (MHz): avg: 650 high: 800 min/max: 400/4200 cores: 1: 800 2: 800
    3: 400 4: 400 5: 800 6: 800 7: 800 8: 400 bogomips: 33599
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: Dell driver: i915
    v: kernel arch: Gen-9.5 bus-ID: 00:02.0
  Device-2: NVIDIA GP108M [GeForce MX230] vendor: Dell driver: nvidia
    v: 550.67 arch: Pascal bus-ID: 01:00.0
  Device-3: Sunplus Innovation Integrated_Webcam_HD driver: uvcvideo
    type: USB bus-ID: 1-6:3
  Display: wayland server: X.Org v: 23.2.4 with: Xwayland v: 23.2.4
    compositor: gnome-shell driver: X: loaded: modesetting,nvidia
    unloaded: fbdev,nouveau,vesa dri: iris gpu: i915
    resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 vendor: intel mesa v: 23.3.6 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
Network:
  Device-1: Intel Comet Lake PCH-LP CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3
  IF: wlp0s20f3 state: up mac: d8:f8:83:e5:98:77
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 02:00.0
  IF: eno1 state: down mac: b0:7b:25:6e:b5:88
  IF-ID-1: virbr0 state: up speed: 10000 Mbps duplex: unknown
    mac: 52:54:00:dc:b1:7c
  IF-ID-2: vnet3 state: unknown speed: 10000 Mbps duplex: full
    mac: fe:54:00:84:44:24
  IF-ID-3: ztcfw3iqyy state: unknown speed: 10000 Mbps duplex: full
    mac: 16:08:bc:8f:ca:a7
  IF-ID-4: ztr2quahsp state: unknown speed: 10000 Mbps duplex: full
    mac: ba:19:f6:75:86:19
Drives:
  Local Storage: total: 297.95 GiB used: 124.89 GiB (41.9%)
Info:
  Memory: total: 32 GiB note: est. available: 31.11 GiB
    used: 12.68 GiB (40.8%)
  Processes: 423 Uptime: 7h 52m Init: systemd target: graphical (5)
  Packages: N/A Compilers: gcc: 13.2.1 Shell: Bash v: 5.2.26 inxi: 3.3.33

I think it’s not as I just clean up the clog, and the CPU run fine in 40-45 *C, and I think rarely peak nowdays as I only do code review…

Hi there :

Can you provide some info for us to look through?

journalctl -b -1 | grep -i restart | This will help you identify any kernel messages related to the unexpected reboots.

dmesg | grep -i nvidia | This might reveal any errors or warnings related to the NVIDIA driver during suspend.

journalctl | grep -i suspend | all journal entries containing “suspend”

dmesg | grep -i error

If you need to break these up into 2 comments please do so. Hopefully we can try some things after wee see any errors.

1 Like

@crazymonkey Just seen this, I can’t move threads to another thread, so I’ll let the mods do that.

I will post a reply on your thread as you have a slightly different machine and what appears to be a slightly different problem.

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

1 Like

This is the output from my laptop that just restart

ben@HLLTP005 ~$ journalctl -b -1 | grep -i restart
Apr 24 15:26:17 HLLTP005 systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
Apr 24 15:26:26 HLLTP005 systemd[1]: Starting rpc-statd-notify.service - Notify NFS peers of a restart...
Apr 24 15:26:26 HLLTP005 systemd[1]: Started rpc-statd-notify.service - Notify NFS peers of a restart.
Apr 24 15:28:49 HLLTP005 systemd[2218]: warp-desktop-svc.service: Scheduled restart job, restart counter is at 1.
Apr 25 08:51:59 HLLTP005 kernel: Restarting tasks ... done.
Apr 25 12:55:52 HLLTP005 kernel: Restarting tasks ... done.
Apr 25 16:24:34 HLLTP005 kernel: Restarting tasks ... done.
Apr 26 09:01:11 HLLTP005 kernel: Restarting tasks ... done.
ben@HLLTP005 ~$ sudo dmesg | grep -i nvidia
[sudo] password for ben: 
[    9.883260] nvidia: loading out-of-tree module taints kernel.
[    9.883272] nvidia: module license 'NVIDIA' taints kernel.
[    9.883278] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    9.883279] nvidia: module license taints kernel.
[   10.261516] nvidia-nvlink: Nvlink Core is being initialized, major device number 511
[   10.262970] nvidia 0000:01:00.0: enabling device (0000 -> 0003)
[   10.466470] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  550.67  Tue Mar 12 23:54:15 UTC 2024
[   10.690419] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
[   10.880605] nvidia-uvm: Loaded the UVM driver, major device number 509.
[   11.013175] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  550.67  Tue Mar 12 23:29:25 UTC 2024
[   11.425419] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[   11.537286] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
[   11.537293] nvidia 0000:01:00.0: [drm] No compatible format found
[   11.537295] nvidia 0000:01:00.0: [drm] Cannot find any crtc or sizes
ben@HLLTP005 ~$ journalctl --since=yesterday | grep -i suspend
Apr 25 08:29:42 HLLTP005 systemd-logind[1000]: Suspending...
Apr 25 08:29:42 HLLTP005 ModemManager[1058]: <info>  [sleep-monitor-systemd] system is about to suspend
Apr 25 08:29:42 HLLTP005 systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
Apr 25 08:29:42 HLLTP005 suspend[180157]: nvidia-suspend.service
Apr 25 08:29:42 HLLTP005 logger[180157]: <13>Apr 25 08:29:42 suspend: nvidia-suspend.service
Apr 25 08:29:42 HLLTP005 systemd[1]: nvidia-suspend.service: Deactivated successfully.
Apr 25 08:29:42 HLLTP005 systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
Apr 25 08:29:42 HLLTP005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 08:29:42 HLLTP005 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 08:29:42 HLLTP005 systemd[1]: Starting systemd-suspend.service - System Suspend...
Apr 25 08:29:42 HLLTP005 systemd-sleep[180191]: Entering sleep state 'suspend'...
Apr 25 08:29:42 HLLTP005 kernel: PM: suspend entry (deep)
Apr 25 08:51:59 HLLTP005 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 25 08:51:59 HLLTP005 kernel: PM: suspend devices took 0.287 seconds
Apr 25 08:51:59 HLLTP005 dbeaver-ce.desktop[78597]: 2024-04-25 08:51:59.043 - System suspend detected! Reinitialize all remote connections.
Apr 25 08:51:59 HLLTP005 kernel: PM: suspend exit
Apr 25 08:51:59 HLLTP005 systemd[1]: systemd-suspend.service: Deactivated successfully.
Apr 25 08:51:59 HLLTP005 systemd[1]: Finished systemd-suspend.service - System Suspend.
Apr 25 08:51:59 HLLTP005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 08:51:59 HLLTP005 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 08:51:59 HLLTP005 systemd[1]: Reached target suspend.target - Suspend.
Apr 25 08:51:59 HLLTP005 logger[180357]: <13>Apr 25 08:51:59 suspend: nvidia-resume.service
Apr 25 08:51:59 HLLTP005 suspend[180357]: nvidia-resume.service
Apr 25 08:51:59 HLLTP005 systemd[1]: Stopped target suspend.target - Suspend.
Apr 25 12:07:54 HLLTP005 systemd-logind[1000]: Suspending...
Apr 25 12:07:54 HLLTP005 ModemManager[1058]: <info>  [sleep-monitor-systemd] system is about to suspend
Apr 25 12:07:57 HLLTP005 systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
Apr 25 12:07:57 HLLTP005 suspend[233054]: nvidia-suspend.service
Apr 25 12:07:57 HLLTP005 logger[233054]: <13>Apr 25 12:07:57 suspend: nvidia-suspend.service
Apr 25 12:07:57 HLLTP005 systemd[1]: nvidia-suspend.service: Deactivated successfully.
Apr 25 12:07:57 HLLTP005 systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
Apr 25 12:07:57 HLLTP005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 12:07:57 HLLTP005 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 12:07:57 HLLTP005 systemd[1]: Starting systemd-suspend.service - System Suspend...
Apr 25 12:07:57 HLLTP005 systemd-sleep[233084]: Entering sleep state 'suspend'...
Apr 25 12:07:57 HLLTP005 kernel: PM: suspend entry (deep)
Apr 25 12:55:52 HLLTP005 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 25 12:55:52 HLLTP005 kernel: PM: suspend devices took 0.097 seconds
Apr 25 12:55:52 HLLTP005 kernel: PM: suspend exit
Apr 25 12:55:52 HLLTP005 systemd[1]: systemd-suspend.service: Deactivated successfully.
Apr 25 12:55:52 HLLTP005 systemd[1]: Finished systemd-suspend.service - System Suspend.
Apr 25 12:55:52 HLLTP005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 12:55:52 HLLTP005 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 12:55:52 HLLTP005 systemd[1]: Reached target suspend.target - Suspend.
Apr 25 12:55:52 HLLTP005 systemd[1]: Stopped target suspend.target - Suspend.
Apr 25 12:55:52 HLLTP005 suspend[233236]: nvidia-resume.service
Apr 25 12:55:52 HLLTP005 logger[233236]: <13>Apr 25 12:55:52 suspend: nvidia-resume.service
Apr 25 12:55:53 HLLTP005 dbeaver-ce.desktop[78597]: 2024-04-25 12:55:53.717 - System suspend detected! Reinitialize all remote connections.
Apr 25 16:10:33 HLLTP005 systemd-logind[1000]: The system will suspend now!
Apr 25 16:10:33 HLLTP005 ModemManager[1058]: <info>  [sleep-monitor-systemd] system is about to suspend
Apr 25 16:10:34 HLLTP005 systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
Apr 25 16:10:34 HLLTP005 suspend[279171]: nvidia-suspend.service
Apr 25 16:10:34 HLLTP005 logger[279171]: <13>Apr 25 16:10:34 suspend: nvidia-suspend.service
Apr 25 16:10:34 HLLTP005 systemd[1]: nvidia-suspend.service: Deactivated successfully.
Apr 25 16:10:34 HLLTP005 systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
Apr 25 16:10:34 HLLTP005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 16:10:34 HLLTP005 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 16:10:34 HLLTP005 systemd[1]: Starting systemd-suspend.service - System Suspend...
Apr 25 16:10:34 HLLTP005 systemd-sleep[279199]: Entering sleep state 'suspend'...
Apr 25 16:10:34 HLLTP005 kernel: PM: suspend entry (deep)
Apr 25 16:24:34 HLLTP005 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 25 16:24:34 HLLTP005 kernel: PM: suspend devices took 0.090 seconds
Apr 25 16:24:34 HLLTP005 dbeaver-ce.desktop[78597]: 2024-04-25 16:24:34.076 - System suspend detected! Reinitialize all remote connections.
Apr 25 16:24:34 HLLTP005 kernel: PM: suspend exit
Apr 25 16:24:34 HLLTP005 systemd[1]: systemd-suspend.service: Deactivated successfully.
Apr 25 16:24:34 HLLTP005 systemd[1]: Finished systemd-suspend.service - System Suspend.
Apr 25 16:24:34 HLLTP005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 16:24:34 HLLTP005 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 16:24:34 HLLTP005 systemd[1]: Reached target suspend.target - Suspend.
Apr 25 16:24:34 HLLTP005 systemd[1]: Stopped target suspend.target - Suspend.
Apr 25 16:24:34 HLLTP005 suspend[279350]: nvidia-resume.service
Apr 25 16:24:34 HLLTP005 logger[279350]: <13>Apr 25 16:24:34 suspend: nvidia-resume.service
Apr 25 18:37:14 HLLTP005 systemd-logind[1000]: Suspending...
Apr 25 18:37:14 HLLTP005 ModemManager[1058]: <info>  [sleep-monitor-systemd] system is about to suspend
Apr 25 18:37:16 HLLTP005 systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
Apr 25 18:37:16 HLLTP005 suspend[313766]: nvidia-suspend.service
Apr 25 18:37:16 HLLTP005 logger[313766]: <13>Apr 25 18:37:16 suspend: nvidia-suspend.service
Apr 25 18:37:16 HLLTP005 systemd[1]: nvidia-suspend.service: Deactivated successfully.
Apr 25 18:37:16 HLLTP005 systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
Apr 25 18:37:16 HLLTP005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 18:37:16 HLLTP005 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 25 18:37:16 HLLTP005 systemd[1]: Starting systemd-suspend.service - System Suspend...
Apr 25 18:37:16 HLLTP005 systemd-sleep[313801]: Entering sleep state 'suspend'...
Apr 25 18:37:16 HLLTP005 kernel: PM: suspend entry (deep)
Apr 26 09:01:11 HLLTP005 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 26 09:01:11 HLLTP005 kernel: PM: suspend devices took 0.090 seconds
Apr 26 09:01:11 HLLTP005 dbeaver-ce.desktop[78597]: 2024-04-26 09:01:11.050 - System suspend detected! Reinitialize all remote connections.
Apr 26 09:01:11 HLLTP005 kernel: PM: suspend exit
Apr 26 09:01:11 HLLTP005 systemd[1]: systemd-suspend.service: Deactivated successfully.
Apr 26 09:01:11 HLLTP005 systemd[1]: Finished systemd-suspend.service - System Suspend.
Apr 26 09:01:11 HLLTP005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 09:01:11 HLLTP005 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 09:01:11 HLLTP005 systemd[1]: Reached target suspend.target - Suspend.
Apr 26 09:01:11 HLLTP005 systemd[1]: Stopped target suspend.target - Suspend.
Apr 26 09:01:11 HLLTP005 suspend[313978]: nvidia-resume.service
Apr 26 09:01:11 HLLTP005 logger[313978]: <13>Apr 26 09:01:11 suspend: nvidia-resume.service
Apr 26 15:10:19 HLLTP005 systemd-logind[1000]: Suspending...
Apr 26 15:10:19 HLLTP005 ModemManager[1058]: <info>  [sleep-monitor-systemd] system is about to suspend
Apr 26 15:10:22 HLLTP005 systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
Apr 26 15:10:22 HLLTP005 suspend[400809]: nvidia-suspend.service
Apr 26 15:10:22 HLLTP005 logger[400809]: <13>Apr 26 15:10:22 suspend: nvidia-suspend.service
Apr 26 15:10:22 HLLTP005 systemd[1]: nvidia-suspend.service: Deactivated successfully.
Apr 26 15:10:22 HLLTP005 systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
Apr 26 15:10:22 HLLTP005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 15:10:22 HLLTP005 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 15:10:22 HLLTP005 systemd[1]: Starting systemd-suspend.service - System Suspend...
Apr 26 15:10:22 HLLTP005 systemd-sleep[400837]: Entering sleep state 'suspend'...
Apr 26 15:10:22 HLLTP005 kernel: PM: suspend entry (deep)
Apr 26 15:26:09 HLLTP005 systemd-logind[970]: The system will suspend now!
Apr 26 15:26:09 HLLTP005 ModemManager[1084]: <info>  [sleep-monitor-systemd] system is about to suspend
Apr 26 15:26:10 HLLTP005 systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
Apr 26 15:26:10 HLLTP005 suspend[3835]: nvidia-suspend.service
Apr 26 15:26:10 HLLTP005 logger[3835]: <13>Apr 26 15:26:10 suspend: nvidia-suspend.service
Apr 26 15:26:10 HLLTP005 systemd[1]: nvidia-suspend.service: Deactivated successfully.
Apr 26 15:26:10 HLLTP005 systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
Apr 26 15:26:10 HLLTP005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 15:26:10 HLLTP005 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 15:26:10 HLLTP005 systemd[1]: Starting systemd-suspend.service - System Suspend...
Apr 26 15:26:10 HLLTP005 systemd-sleep[3871]: Entering sleep state 'suspend'...
Apr 26 15:26:10 HLLTP005 kernel: PM: suspend entry (deep)
Apr 26 16:38:06 HLLTP005 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 26 16:38:06 HLLTP005 kernel: PM: suspend devices took 0.287 seconds
Apr 26 16:38:06 HLLTP005 kernel: PM: suspend exit
Apr 26 16:38:06 HLLTP005 systemd[1]: systemd-suspend.service: Deactivated successfully.
Apr 26 16:38:06 HLLTP005 systemd[1]: Finished systemd-suspend.service - System Suspend.
Apr 26 16:38:06 HLLTP005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 16:38:06 HLLTP005 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 16:38:06 HLLTP005 systemd[1]: Reached target suspend.target - Suspend.
Apr 26 16:38:06 HLLTP005 systemd[1]: Stopped target suspend.target - Suspend.
Apr 26 16:38:06 HLLTP005 suspend[4009]: nvidia-resume.service
Apr 26 16:38:06 HLLTP005 logger[4009]: <13>Apr 26 16:38:06 suspend: nvidia-resume.service
ben@HLLTP005 ~$ sudo dmesg | grep -i error
[    0.721875] pcieport 0000:00:1c.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    0.722094] pcieport 0000:00:1c.7: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    1.012015] RAS: Correctable Errors collector initialized.
[    5.760115] Bluetooth: hci0: FW download error recovery failed (-19)
[    5.760154] Bluetooth: hci0: Error reading debug features

which nvdia driver are you using ? proprietary or nouveau ?

Please use the correct model number in the title and add Nvidia “GP108M [GeForce MX230]” so people with similar Nvidia issues will find it.

There are other recent reports of issues with Nvidia powerd (use advanced search for reports since 2023-01-01), but some appear to be for desktops where powerd shouldn’t be needed.

Can you try removing powerd?

I use nouveau most of the time. The RPMFusion Howto has a section on switching between Nvidia and nouveau – you can leave Nvidia installed but use nouveau until you really need Nvidia.

do you recommend nouveau instead of proprietary ? im having some nvdia problems and i use nouveau, people here recommended me the opposite, hence the question

Nouveau is fine for command-line processing, simple 2-D plots, emails, web browsing of forums and documentation, and supports Wayland on older Nvidia hardware. Heavy graphics and games benefit from Nvidia, but Wayland support seems to be work in progress.

I do install Nvidia drivers and can switch to them when needed – often troubleshooting issues with some 3rd party image processing apps.

I have the Nvidia driver but my cards are currently still supported ( GTX 970 & RTX 350ti ).