NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

allencch · 2024-03-11 01:31:53

obap74 wrote:

I'm getting a black screen with a functional mouse cursor.

I have this issue as well. Then I found that, if I kill "picom" before suspending, then when resuming, I can see the screen properly.

seth · 2024-03-11 07:57:48

That's what the entire PreserveVideoMemoryAllocation is meant to overcome.
If the VRAM doesn't get stored or RAM it won't get refreshed during S3's and start to decay and your GL textures become black (invalid) or garbage (noise)

allencch · 2024-03-11 15:46:56

I tried with "options nvidia NVreg_PreserveVideoMemoryAllocations=1" on the module config file, switching between TTY still get the black screen with mouse, when picom is running.

seth · 2024-03-11 15:52:20

Did you also enable the relevant services?
Pot. redirect the storage destination (in case you've lots of VRAM and little free RAM/swap)?
https://wiki.archlinux.org/title/NVIDIA … er_suspend

juneidy · 2024-03-18 01:03:52

seth wrote:

That's what the entire PreserveVideoMemoryAllocation is meant to overcome.
If the VRAM doesn't get stored or RAM it won't get refreshed during S3's and start to decay and your GL textures become black (invalid) or garbage (noise)

Thanks, that solved my problem completely!

Installed
* core/linux 6.8.1.arch1-1
* extra/nvidia 550.54.14-7

this morning and I still had the same issue where lock screen would not show until I swtiched to ctrl+alt+F2 and ctrl+alt+F7 until I applied the parameter seth suggested.

I am now able to sleep and wake normally!

lorenzol36 · 2024-03-18 11:51:37

juneidy wrote:

I am now able to sleep and wake normally!

Can you suspend fine if you don't have all the PreserveVideoMemoryAllocations setup? Because some of us don't use the kernel parameter and yet are unable to suspend (while we could with previous driver versions).

EDIT: I've just gave a look to the changelog of 550.67 version and I noticed this:

Fixed a bug that caused "Flip event timeout" messages to be printed to the system log when the system is suspended without using /usr/bin/nvidia-sleep.sh when nvidia-drm is loaded with the `fbdev=1` kernel module parameter.

I was using nvidia-drm.fbdev=1 as a kernel parameter and this made me suspicious. I tried to remove it and I now can resume the system again without any problems on version 550.54.14.

Last edited by lorenzol36 (2024-03-21 01:22:21)

bertieb · 2024-04-03 17:19:44

I upgraded to Linux 6.8.2 (from 6.5.8) and nvidia 550.67-1 (from 535.113.01-6) on Apr 1st, and was able to suspend and resume 3-4 times.

However, on resume after a suspend of ~1.5h this afternoon I once again experienced the same symptoms as before and as others in the thread have had: black screens, no input from keyboard, and no response to ssh. I used the ACPI reset button to reboot.

Last boot log shows nothing after 'resuming' from the last suspend, but here it is (trying to include it in a code block caused this tab to be very laggy when responding to input): https://0x0.st/XzkO.log

lorenzol36 · 2024-04-03 18:20:59

Unfortunately I'm also experiencing problems again after some days of a functioning suspension. If I use nvidia-drm.fbdev=1 and nvidia-drm.modeset=1 kernel parameters I have the same problem as before: black screen and have to switch to tty2 first and then to tty7 to finally see the screen. If I don't use the kernel parameters sometimes I can resume, sometimes I have a black screen with no responding mouse and keyboard that forces me to use the hardware reset button. At least that's what have been happening to me while testing.

obap74 · 2024-04-03 18:32:18

bertieb wrote:

Last boot log shows nothing after 'resuming' from the last suspend

Same here every time this issue occurs.

Thanks for the feedback with 6.8.2 / 550. I'm still on 6.1 / 535 since suspend/hibernate works reliably.

As time goes by, the less likely this issue is going to be fixed.
535 will be EOL in June 2026, 6.1 will be EOL in December 2026. If it's not fixed till then, I'll have to get a new GPU or stop suspending/hibernating I guess.

verbbis · 2024-04-21 07:16:47

Gooberslot wrote:

I'm using a GTX 980 Ti and I also can't resume from suspend with anything newer than 535.

Also a GTX 980 Ti user here. Just tested with the latest kernel and nvidia packages:

core/linux 6.8.7.arch1-1
extra/nvidia 550.76-1

I've been playing around debugging kernel resume with the help of pm_trace, but I guess it's the Nvidia driver specifically which makes this even harder. My test scenario: no display manager/X11, just console, nvidia_drm.modeset=1. Force suspend with:

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && systemctl suspend"

At least resuming does not result in a hard lockup anymore as it used to e.g. networking still works. I do get just a black screen, though. These are the only lines in dmesg which look relevant:

[   61.626350] nvidia-modeset: ERROR: GPU:0: Failed to bind display engine notify surface descriptor: 0x1a (Ran out of a critical resource, other than memory [NV_ERR_INSUFFICIENT_RESOURCES])
[   61.626484] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer
[   61.626767] nvidia-modeset: ERROR: GPU:0: Failed to bind display engine notify surface descriptor: 0x1a (Ran out of a critical resource, other than memory [NV_ERR_INSUFFICIENT_RESOURCES])
[   61.627006] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer

EDIT: Interestingly, enabling Nvidia's framebuffer implementation with nvidia_drm.fbdev=1 gets rid of that error and resume succeeds. I have to run with this for a while and see how reliable it is. Gnome/X11 does crash horribly, but the errors look like something enabling NVreg_PreserveVideoMemoryAllocations might fix.

EDIT2: Enabled NVreg_PreserveVideoMemoryAllocations and the relevant systemd hooks. Not reliable with errors like these:

[ 1343.717038] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Failed to map NvKmsKapiMemory 0x00000000a2a719a1

[ 1597.364247] INFO: task nvidia-modeset/:474 blocked for more than 122 seconds.
[ 1597.364256]       Tainted: P           OE      6.8.7-arch1-1 #1
[ 1597.364261] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1597.364265] task:nvidia-modeset/ state:D stack:0     pid:474   tgid:474   ppid:2      flags:0x00004000
[ 1597.364269] Call Trace:
[ 1597.364271]  <TASK>
[ 1597.364273]  __schedule+0x3e6/0x1520
[ 1597.364282]  schedule+0x32/0xd0
[ 1597.364286]  schedule_preempt_disabled+0x15/0x30
[ 1597.364289]  rwsem_down_read_slowpath+0x2aa/0x540
[ 1597.364295]  ? __pfx__main_loop+0x10/0x10 [nvidia_modeset 3fcb72663fb07e8d23115012bbd6cac6605a279b]
[ 1597.364315]  down_read+0x48/0xb0
[ 1597.364318]  nvkms_kthread_q_callback+0x149/0x170 [nvidia_modeset 3fcb72663fb07e8d23115012bbd6cac6605a279b]
[ 1597.364336]  _main_loop+0x99/0x170 [nvidia_modeset 3fcb72663fb07e8d23115012bbd6cac6605a279b]
[ 1597.364355]  kthread+0xe8/0x120
[ 1597.364359]  ? __pfx_kthread+0x10/0x10
[ 1597.364363]  ret_from_fork+0x34/0x50
[ 1597.364366]  ? __pfx_kthread+0x10/0x10
[ 1597.364369]  ret_from_fork_asm+0x1b/0x30
[ 1597.364375]  </TASK>

Sigh. Back to disabling suspend I guess.

Last edited by verbbis (2024-04-21 15:15:49)

bertieb · 2024-05-13 09:17:05

As an additional anec-data point and update: suspend seems substantially less reliable under Linux 6.8.9.arch1-2 and 550.78-2; versus 6.8.2.arch2-1 and 550.67-3.

With the former, the more recent, since an update on 2024-05-08 I've had several overnight suspends in a row that have resulted in the familiar black screen / no response to ssh.

obap74's suggestion of an LTS kernel may be the way to go!

Edit: another short suspend resulted in a no-wake situation, this combo of kernel and drivers might be the worst yet

Last edited by bertieb (2024-05-13 16:47:01)

obap74 · 2024-05-13 17:08:50

bertieb wrote:

As an additional anec-data point and update: suspend seems substantially less reliable under Linux 6.8.9.arch1-2 and 550.78-2; versus 6.8.2.arch2-1 and 550.67-3.
With the former, the more recent, since an update on 2024-05-08 I've had several overnight suspends in a row that have resulted in the familiar black screen / no response to ssh.
Edit: another short suspend resulted in a no-wake situation, this combo of kernel and drivers might be the worst yet

Thanks for the update.

bertieb wrote:

obap74's suggestion of an LTS kernel may be the way to go!

I'm still using:

local/linux-lts61 6.1.90-1
local/linux-lts61-headers 6.1.90-1
local/nvidia-535xx-dkms 535.171.04-1
local/nvidia-535xx-utils 535.171.04-1

and suspend/resume multiple times every day without any issue.

obap74 · 2024-06-10 09:36:14

Still working consistently with 535.183.01

local/linux-lts61 6.1.90-1
local/linux-lts61-headers 6.1.90-1
local/nvidia-535xx-dkms 535.183.01-1
local/nvidia-535xx-utils 535.183.01-1

I guess nobody bothered trying 555 beta?

bertieb · 2024-06-22 11:20:24

obap74 wrote:

I guess nobody bothered trying 555 beta?

Nope, but I may have to try...

obap74 wrote:

Still working consistently with 535.183.01

local/linux-lts61 6.1.90-1
local/linux-lts61-headers 6.1.90-1
local/nvidia-535xx-dkms 535.183.01-1
local/nvidia-535xx-utils 535.183.01-1

Also running on the 6.1 LTS kernel with 535 driver.

Since a couple of days ago I've been having a different, reproducible suspend problem.

When trying to suspend with 'systemctl suspend', the graphical interface locks up. No mouse input, seemingly no keyboard input, can't toggle numlock/capslock. I say 'seemingly' as sysrq commands still go through. In this case, the system is responsive to network and accepts ssh logins.Trying to shut down from ssh in that case doesn't work, a message to the effect of "There is a suspend in progress, ignoring shutdown".

Example from trying to suspend just after booting and logging into graphical session:

$ sudo journalctl -b -1
[...]
Jun 22 11:53:22 zeus systemd-logind[873]: The system will suspend now!
Jun 22 11:53:22 zeus polkitd[1126]: Unregistered Authentication Agent for unix-process:17196:21691 (system bus name>
Jun 22 11:53:22 zeus systemd[1]: Reached target Sleep.
Jun 22 11:53:22 zeus systemd[1]: Starting System Suspend...
Jun 22 11:53:22 zeus systemd-sleep[17204]: Successfully froze unit 'user.slice'.
Jun 22 11:53:22 zeus systemd-sleep[17204]: Performing sleep operation 'suspend'...
Jun 22 11:53:22 zeus kernel: PM: suspend entry (deep)
Jun 22 11:53:22 zeus kernel: Filesystems sync: 0.011 seconds
Jun 22 11:53:33 zeus kernel: sysrq: This sysrq operation is disabled.
Jun 22 11:53:33 zeus kernel: sysrq: This sysrq operation is disabled.
Jun 22 11:53:34 zeus kernel: sysrq: This sysrq operation is disabled.
Jun 22 11:53:34 zeus kernel: sysrq: Emergency Sync

You can see me hammering the REIS (UB) sequence at the end.

Packages:

$ pacman -Q | grep linux
archlinux-keyring 20240609-1
lib32-util-linux 2.40.1-1
linux 6.8.2.arch2-1
linux-api-headers 6.8-1
linux-firmware 20240610.9c10a208-1
linux-firmware-whence 20240610.9c10a208-1
linux-headers 6.9.5.arch1-1
linux-lts61 6.1.91-1
linux-lts61-headers 6.1.91-1
syslinux 6.04.pre2.r11.gbf6db5b4-4
ttf-linux-libertine 5.3.0-9
ttf-linux-libertine-g 20120116-7
util-linux 2.40.1-1
util-linux-libs 2.40.1-1

$ pacman -Q | grep nvidia
libva-nvidia-driver 0.0.12-1
nvidia-535xx-dkms 535.179-1
nvidia-535xx-utils 535.179-1
opencl-nvidia 550.90.07-2

I know I don't need the mainline kernel if I'm booting from the LTS but I haven't yet removed it.

Has anyone else seen this behaviour? Is there a way I should approach troubleshooting this? Happy to start a new thread if this is likely unrelated

Cheers

obap74 · 2024-06-22 13:43:58

@bertieb

Not sure but the issue you're describing might be related to systemd 256 update, see this recent reddit post from r/archlinux.
You could try the workarounds mentioned or downgrade to 255.7 for now.
I'm lucky since I'm not affected, I can suspend/resume as usual.

bertieb · 2024-06-22 14:19:53

obap74 wrote:

@bertieb
Not sure but the issue you're describing might be related to systemd 256 update, see this recent reddit post from r/archlinux.
You could try the workarounds mentioned or downgrade to 255.7 for now.
I'm lucky since I'm not affected, I can suspend/resume as usual.

Crivvens, what a bug!

That was an excellent find, since applying the workaround seems to have worked:

bennyb0i wrote:

In /usr/lib/systemd/system/systemd-suspend.service.d/nvidia.conf add:
[Service]
Environment=SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false
And in /usr/lib/systemd/system/systemd-homed.service.d/nvidia.conf add:
[Service]
Environment=SYSTEMD_HOME_LOCK_FREEZE_SESSION=false
Don't forget to sudo systemctl daemon-reload after you've made the changes.

I had to create the containing directories and files, but I could suspend thereafter:

mkdir /usr/lib/systemd/system/systemd-suspend.service.d/
echo -e "[Service]\nEnvironment=SYSTEMD_HOME_LOCK_FREEZE_SESSION=false" >> /usr/lib/systemd/system/systemd-suspend.service.d/nvidia.conf
mkdir /usr/lib/systemd/system/systemd-homed.service.d/
echo -e "[Service]\nEnvironment=SYSTEMD_HOME_LOCK_FREEZE_SESSION=false" >> /usr/lib/systemd/system/systemd-homed.service.d/nvidia.conf
systemctl daemon-reload

Cheers obap74!

d.ALT · 2024-06-24 17:45:38

Me too:

[  178.915518] PM: suspend entry (deep)
[  195.846172] Filesystems sync: 16.930 seconds
[  195.960331] Freezing user space processes
[  195.962008] Freezing user space processes completed (elapsed 0.001 seconds)
[  195.962013] OOM killer disabled.
[  195.962014] Freezing remaining freezable tasks
[  195.963136] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[  195.963160] printk: Suspending console(s) (use no_console_suspend to debug)
[  195.998053] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  195.998054] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[  195.998081] sd 10:0:0:0: [sdd] Synchronizing SCSI cache
[  195.998099] sd 4:0:0:0: [sdc] Synchronizing SCSI cache
[  195.998545] ata5.00: Entering standby power mode
[  196.000264] ata2.00: Entering standby power mode
[  196.000835] ata1.00: Entering standby power mode
[  196.415987] ACPI: PM: Preparing to enter system sleep state S3
[  196.728871] ACPI: PM: Saving platform NVS memory
[  196.728947] Disabling non-boot CPUs ...
[  196.730812] smpboot: CPU 1 is now offline
[  196.733351] smpboot: CPU 2 is now offline
[  196.735931] smpboot: CPU 3 is now offline
[  196.738550] smpboot: CPU 4 is now offline
[  196.740744] smpboot: CPU 5 is now offline
[  196.742912] smpboot: CPU 6 is now offline
[  196.745046] smpboot: CPU 7 is now offline
[  196.747223] smpboot: CPU 8 is now offline
[  196.749757] smpboot: CPU 9 is now offline
[  196.752291] smpboot: CPU 10 is now offline
[  196.754940] smpboot: CPU 11 is now offline
[  196.756999] smpboot: CPU 12 is now offline
[  196.759380] smpboot: CPU 13 is now offline
[  196.761806] smpboot: CPU 14 is now offline
[  196.764244] smpboot: CPU 15 is now offline
[  196.765230] ACPI: PM: Low-level resume complete
[  196.765263] ACPI: PM: Restoring platform NVS memory
[  196.765364] AMD-Vi: Virtual APIC enabled
[  196.765404] AMD-Vi: Virtual APIC enabled
[  196.765830] Enabling non-boot CPUs ...
[  196.765883] smpboot: Booting Node 0 Processor 1 APIC 0x2
[  196.766337] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.766342] ACPI: \_PR_.C002: Found 2 idle states
[  196.766541] CPU1 is up
[  196.766564] smpboot: Booting Node 0 Processor 2 APIC 0x4
[  196.767012] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.767017] ACPI: \_PR_.C004: Found 2 idle states
[  196.767232] CPU2 is up
[  196.767256] smpboot: Booting Node 0 Processor 3 APIC 0x6
[  196.767702] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.767706] ACPI: \_PR_.C006: Found 2 idle states
[  196.767927] CPU3 is up
[  196.767948] smpboot: Booting Node 0 Processor 4 APIC 0x8
[  196.768582] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.768588] ACPI: \_PR_.C008: Found 2 idle states
[  196.768842] CPU4 is up
[  196.768880] smpboot: Booting Node 0 Processor 5 APIC 0xa
[  196.769440] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.769444] ACPI: \_PR_.C00A: Found 2 idle states
[  196.769699] CPU5 is up
[  196.769722] smpboot: Booting Node 0 Processor 6 APIC 0xc
[  196.770226] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.770230] ACPI: \_PR_.C00C: Found 2 idle states
[  196.770501] CPU6 is up
[  196.770527] smpboot: Booting Node 0 Processor 7 APIC 0xe
[  196.771028] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.771033] ACPI: \_PR_.C00E: Found 2 idle states
[  196.771324] CPU7 is up
[  196.771345] smpboot: Booting Node 0 Processor 8 APIC 0x1
[  196.771807] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.771812] ACPI: \_PR_.C001: Found 2 idle states
[  196.772211] CPU8 is up
[  196.772241] smpboot: Booting Node 0 Processor 9 APIC 0x3
[  196.772700] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.772705] ACPI: \_PR_.C003: Found 2 idle states
[  196.773014] CPU9 is up
[  196.773045] smpboot: Booting Node 0 Processor 10 APIC 0x5
[  196.773479] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.773484] ACPI: \_PR_.C005: Found 2 idle states
[  196.773806] CPU10 is up
[  196.773836] smpboot: Booting Node 0 Processor 11 APIC 0x7
[  196.774298] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.774303] ACPI: \_PR_.C007: Found 2 idle states
[  196.774640] CPU11 is up
[  196.774676] smpboot: Booting Node 0 Processor 12 APIC 0x9
[  196.775179] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.775184] ACPI: \_PR_.C009: Found 2 idle states
[  196.775573] CPU12 is up
[  196.775619] smpboot: Booting Node 0 Processor 13 APIC 0xb
[  196.776094] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.776098] ACPI: \_PR_.C00B: Found 2 idle states
[  196.776493] CPU13 is up
[  196.776525] smpboot: Booting Node 0 Processor 14 APIC 0xd
[  196.777003] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.777007] ACPI: \_PR_.C00D: Found 2 idle states
[  196.777413] CPU14 is up
[  196.777440] smpboot: Booting Node 0 Processor 15 APIC 0xf
[  196.777913] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[  196.777917] ACPI: \_PR_.C00F: Found 2 idle states
[  196.778329] CPU15 is up
[  196.780322] ACPI: PM: Waking up from system sleep state S3
[  196.783886] xhci_hcd 0000:02:00.0: xHC error in resume, USBSTS 0x401, Reinit
[  196.783890] usb usb1: root hub lost power or was reset
[  196.783892] usb usb2: root hub lost power or was reset
[  196.794315] xhci_hcd 0000:0a:00.2: xHC error in resume, USBSTS 0x401, Reinit
[  196.794318] usb usb5: root hub lost power or was reset
[  196.794319] usb usb6: root hub lost power or was reset
[  196.896190] nvme nvme0: 8/0/0 default/read/poll queues
[  196.898165] nvme nvme0: Ignoring bogus Namespace Identifiers
[  197.099765] ata3: SATA link down (SStatus 0 SControl 300)
[  197.099766] ata9: SATA link down (SStatus 0 SControl 300)
[  197.099801] ata4: SATA link down (SStatus 0 SControl 300)
[  197.099824] ata6: SATA link down (SStatus 0 SControl 300)
[  197.099851] ata8: SATA link down (SStatus 0 SControl 300)
[  197.099870] ata7: SATA link down (SStatus 0 SControl 300)
[  197.125757] usb 1-13: reset full-speed USB device number 2 using xhci_hcd
[  197.255869] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  197.255898] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  197.256120] ata1.00: supports DRM functions and may not be fully accessible
[  197.256583] ata2.00: supports DRM functions and may not be fully accessible
[  197.257300] sd 1:0:0:0: [sdb] Starting disk
[  197.257397] ata2.00: supports DRM functions and may not be fully accessible
[  197.258073] ata2.00: configured for UDMA/133
[  197.258986] sd 0:0:0:0: [sda] Starting disk
[  197.259258] ata1.00: supports DRM functions and may not be fully accessible
[  197.261616] ata1.00: configured for UDMA/133
[  197.268537] ahci 0000:02:00.1: port does not support device sleep
[  197.272050] ahci 0000:02:00.1: port does not support device sleep
[  197.379029] OOM killer enabled.
[  197.379032] Restarting tasks ... done.
[  197.380046] random: crng reseeded on system resumption
[  197.380059] PM: suspend exit
[  197.381758] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[  197.386322] Bluetooth: hci0: Device revision is 1
[  197.386327] Bluetooth: hci0: Secure boot is enabled
[  197.386328] Bluetooth: hci0: OTP lock is enabled
[  197.386330] Bluetooth: hci0: API lock is enabled
[  197.386331] Bluetooth: hci0: Debug lock is disabled
[  197.386332] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[  197.386880] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[  197.386896] Bluetooth: hci0: Boot Address: 0x24800
[  197.386898] Bluetooth: hci0: Firmware Version: 132-3.24
[  197.833691] NVRM: GPU at PCI:0000:0a:00: GPU-e742497b-03c4-19ce-062d-a5e95dcd5b5c
[  197.833697] NVRM: Xid (PCI:0000:0a:00): 62, pid='<unknown>', name=<unknown>, 0004e710 0004e66a 0002762e 00027578 000275d9 000445d3 00000011 00000000
[  197.840498] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000050
[  197.847110] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000056
[  197.853107] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000057
[  197.859016] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000058
[  197.863723] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000059
[  197.868276] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 0000005a
[  197.872900] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 0000005b
[  197.877510] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 0000005c
[  197.882039] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 0000005d
[  197.886645] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 0000005e
[  197.891244] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 0000005f
[  197.895762] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000060
[  197.901400] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000061
[  197.907002] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000062
[  197.912680] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000063
[  197.918313] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000064
[  197.923989] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000065
[  197.929686] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000066
[  197.935430] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000067
[  197.941174] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000068
[  197.946790] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 00000069
[  197.952393] NVRM: Xid (PCI:0000:0a:00): 45, pid=3049, name=hitman3.exe, Ch 0000006a
[  199.488849] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  199.519970] sd 4:0:0:0: [sdc] Starting disk
[  199.521340] ata5.00: configured for UDMA/133
[  200.016115] igb 0000:08:00.0 enp8s0: igb: enp8s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[  200.626706] Bluetooth: hci0: Waiting for firmware download to complete
[  200.627690] Bluetooth: hci0: Firmware loaded in 3164826 usecs
[  200.627738] Bluetooth: hci0: Waiting for device to boot
[  200.644692] Bluetooth: hci0: Device booted in 16600 usecs
[  200.644698] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[  200.647348] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[  200.655703] Bluetooth: hci0: Applying Intel DDC parameters completed
[  200.660707] Bluetooth: hci0: Firmware revision 0.3 build 132 week 3 2024
[  200.670738] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
[  200.939901] Bluetooth: MGMT ver 1.22
[  201.771815] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  201.771830] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  201.771834] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  201.771839] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  202.002813] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  202.002827] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  202.002831] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  202.002835] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  326.117095] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  326.117110] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  326.117114] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  326.117119] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  329.362140] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  329.362150] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  329.362153] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  329.362155] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  330.968144] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  330.968157] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  330.968161] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  330.968166] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  333.938175] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  333.938189] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  333.938193] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  333.938198] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  334.158180] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  334.158192] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  334.158196] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  334.158201] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  336.325198] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  336.325211] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  336.325215] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  336.325220] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  336.578212] pcieport 0000:00:01.3: AER: Multiple Correctable error message received from 0000:03:06.0
[  336.578295] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  336.578298] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000041/00002000
[  336.578301] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  336.578303] pcieport 0000:03:06.0:    [ 6] BadTLP                
[  337.975238] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  337.975250] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  337.975254] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  337.975259] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  364.122512] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  364.122527] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  364.122530] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  364.122535] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  366.366512] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  366.366526] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  366.366530] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  366.366534] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  368.055741] INFO: task nvidia-modeset/:250 blocked for more than 124 seconds.
[  368.055754]       Tainted: P           OE      6.9.6-arch1-1 #1
[  368.055759] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  368.055763] task:nvidia-modeset/ state:D stack:0     pid:250   tgid:250   ppid:2      flags:0x00004000
[  368.055769] Call Trace:
[  368.055770]  <TASK>
[  368.055773]  __schedule+0x3c7/0x1510
[  368.055782]  schedule+0x27/0xf0
[  368.055788]  schedule_preempt_disabled+0x15/0x30
[  368.055792]  rwsem_down_read_slowpath+0x26f/0x4e0
[  368.055797]  ? __pfx__main_loop+0x10/0x10 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  368.055842]  down_read+0x48/0xa0
[  368.055844]  nvkms_kthread_q_callback+0x140/0x160 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  368.055887]  _main_loop+0x95/0x150 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  368.055930]  kthread+0xcf/0x100
[  368.055935]  ? __pfx_kthread+0x10/0x10
[  368.055938]  ret_from_fork+0x31/0x50
[  368.055943]  ? __pfx_kthread+0x10/0x10
[  368.055946]  ret_from_fork_asm+0x1a/0x30
[  368.055951]  </TASK>
[  377.916630] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  377.916645] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  377.916648] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  377.916653] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  379.368641] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  379.368651] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  379.368653] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  379.368656] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  390.401763] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  390.401777] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  390.401780] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  390.401785] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  394.713826] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  394.713840] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  394.713844] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  394.713848] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  397.188830] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  397.188843] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  397.188847] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  397.188852] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  416.923032] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  416.923047] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  416.923051] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  416.923056] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  419.167078] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  419.167094] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  419.167097] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  419.167102] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  426.746133] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  426.746148] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  426.746152] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  426.746157] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  428.616174] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  428.616187] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  428.616191] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  428.616195] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  457.271451] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  457.271467] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  457.271470] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  457.271475] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  478.622664] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  478.622674] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  478.622676] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  478.622678] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  478.853672] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  478.853687] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  478.853692] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  478.853698] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  488.731774] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  488.731788] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  488.731792] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  488.731797] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  489.523805] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  489.523818] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  489.523822] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  489.523827] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  490.958105] INFO: task nvidia-modeset/:250 blocked for more than 247 seconds.
[  490.958113]       Tainted: P           OE      6.9.6-arch1-1 #1
[  490.958116] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  490.958119] task:nvidia-modeset/ state:D stack:0     pid:250   tgid:250   ppid:2      flags:0x00004000
[  490.958123] Call Trace:
[  490.958124]  <TASK>
[  490.958127]  __schedule+0x3c7/0x1510
[  490.958134]  schedule+0x27/0xf0
[  490.958138]  schedule_preempt_disabled+0x15/0x30
[  490.958141]  rwsem_down_read_slowpath+0x26f/0x4e0
[  490.958145]  ? __pfx__main_loop+0x10/0x10 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  490.958170]  down_read+0x48/0xa0
[  490.958173]  nvkms_kthread_q_callback+0x140/0x160 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  490.958205]  _main_loop+0x95/0x150 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  490.958244]  kthread+0xcf/0x100
[  490.958249]  ? __pfx_kthread+0x10/0x10
[  490.958252]  ret_from_fork+0x31/0x50
[  490.958255]  ? __pfx_kthread+0x10/0x10
[  490.958257]  ret_from_fork_asm+0x1a/0x30
[  490.958261]  </TASK>
[  495.045860] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  495.045873] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  495.045877] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  495.045902] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  511.810037] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  511.810051] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  511.810055] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  511.810060] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  513.196026] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  513.196040] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  513.196044] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  513.196049] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  526.770165] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  526.770180] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  526.770184] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  526.770189] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  580.791749] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  580.791764] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  580.791768] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  580.791773] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  613.849796] INFO: task nvidia-modeset/:250 blocked for more than 370 seconds.
[  613.849810]       Tainted: P           OE      6.9.6-arch1-1 #1
[  613.849814] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  613.849818] task:nvidia-modeset/ state:D stack:0     pid:250   tgid:250   ppid:2      flags:0x00004000
[  613.849825] Call Trace:
[  613.849826]  <TASK>
[  613.849830]  __schedule+0x3c7/0x1510
[  613.849840]  schedule+0x27/0xf0
[  613.849846]  schedule_preempt_disabled+0x15/0x30
[  613.849849]  rwsem_down_read_slowpath+0x26f/0x4e0
[  613.849854]  ? __pfx__main_loop+0x10/0x10 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  613.849885]  down_read+0x48/0xa0
[  613.849887]  nvkms_kthread_q_callback+0x140/0x160 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  613.849916]  _main_loop+0x95/0x150 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  613.849946]  kthread+0xcf/0x100
[  613.849950]  ? __pfx_kthread+0x10/0x10
[  613.849953]  ret_from_fork+0x31/0x50
[  613.849957]  ? __pfx_kthread+0x10/0x10
[  613.849960]  ret_from_fork_asm+0x1a/0x30
[  613.849964]  </TASK>
[  651.407361] igb 0000:08:00.0 enp8s0: igb: enp8s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[  655.043980] igb 0000:08:00.0 enp8s0: igb: enp8s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[  736.723582] INFO: task nvidia-modeset/:250 blocked for more than 493 seconds.
[  736.723593]       Tainted: P           OE      6.9.6-arch1-1 #1
[  736.723598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  736.723602] task:nvidia-modeset/ state:D stack:0     pid:250   tgid:250   ppid:2      flags:0x00004000
[  736.723607] Call Trace:
[  736.723609]  <TASK>
[  736.723613]  __schedule+0x3c7/0x1510
[  736.723622]  schedule+0x27/0xf0
[  736.723628]  schedule_preempt_disabled+0x15/0x30
[  736.723632]  rwsem_down_read_slowpath+0x26f/0x4e0
[  736.723638]  ? __pfx__main_loop+0x10/0x10 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  736.723682]  down_read+0x48/0xa0
[  736.723685]  nvkms_kthread_q_callback+0x140/0x160 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  736.723727]  _main_loop+0x95/0x150 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  736.723770]  kthread+0xcf/0x100
[  736.723774]  ? __pfx_kthread+0x10/0x10
[  736.723778]  ret_from_fork+0x31/0x50
[  736.723782]  ? __pfx_kthread+0x10/0x10
[  736.723785]  ret_from_fork_asm+0x1a/0x30
[  736.723790]  </TASK>
[  755.044521] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  755.044531] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  755.044533] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  755.044536] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  757.541570] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  757.541582] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  757.541586] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  757.541591] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  759.345574] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  759.345582] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  759.345584] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  759.345587] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  759.972577] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  759.972589] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  759.972593] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  759.972598] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  767.001645] pcieport 0000:00:01.3: AER: Multiple Correctable error message received from 0000:03:06.0
[  767.001732] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  767.001736] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  767.001741] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  767.001745] pcieport 0000:03:06.0: AER:   Error of this Agent is reported first
[  767.001758] igb 0000:08:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
[  767.001761] igb 0000:08:00.0:   device [8086:1539] error status/mask=00001000/00002000
[  767.001764] igb 0000:08:00.0:    [12] Timeout               
[  779.585772] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  779.585782] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  779.585784] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  779.585787] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  813.972156] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  813.972171] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  813.972175] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  813.972180] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  821.760237] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  821.760252] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  821.760256] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  821.760261] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  833.728378] pcieport 0000:00:01.3: AER: Multiple Correctable error message received from 0000:03:06.0
[  833.728467] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  833.728470] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000041/00002000
[  833.728475] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  833.728479] pcieport 0000:03:06.0:    [ 6] BadTLP                
[  835.466377] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  835.466391] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  835.466395] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  835.466399] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  840.284407] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  840.284422] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  840.284426] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  840.284431] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  842.330422] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  842.330435] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  842.330437] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  842.330441] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  854.133547] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  854.133562] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  854.133566] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  854.133570] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  859.599219] INFO: task nvidia-modeset/:250 blocked for more than 616 seconds.
[  859.599228]       Tainted: P           OE      6.9.6-arch1-1 #1
[  859.599233] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  859.599237] task:nvidia-modeset/ state:D stack:0     pid:250   tgid:250   ppid:2      flags:0x00004000
[  859.599242] Call Trace:
[  859.599244]  <TASK>
[  859.599247]  __schedule+0x3c7/0x1510
[  859.599256]  schedule+0x27/0xf0
[  859.599262]  schedule_preempt_disabled+0x15/0x30
[  859.599266]  rwsem_down_read_slowpath+0x26f/0x4e0
[  859.599272]  ? __pfx__main_loop+0x10/0x10 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  859.599316]  down_read+0x48/0xa0
[  859.599319]  nvkms_kthread_q_callback+0x140/0x160 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  859.599362]  _main_loop+0x95/0x150 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  859.599405]  kthread+0xcf/0x100
[  859.599409]  ? __pfx_kthread+0x10/0x10
[  859.599413]  ret_from_fork+0x31/0x50
[  859.599417]  ? __pfx_kthread+0x10/0x10
[  859.599420]  ret_from_fork_asm+0x1a/0x30
[  859.599425]  </TASK>
[  859.599495] INFO: task nvidia-sleep.sh:3802 blocked for more than 122 seconds.
[  859.599499]       Tainted: P           OE      6.9.6-arch1-1 #1
[  859.599503] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  859.599507] task:nvidia-sleep.sh state:D stack:0     pid:3802  tgid:3802  ppid:1      flags:0x00000002
[  859.599511] Call Trace:
[  859.599512]  <TASK>
[  859.599514]  __schedule+0x3c7/0x1510
[  859.599518]  ? inode_permission+0x39/0x190
[  859.599522]  ? __d_lookup+0x7e/0xc0
[  859.599525]  ? mntput_no_expire+0x4a/0x260
[  859.599530]  schedule+0x27/0xf0
[  859.599534]  schedule_timeout+0x12f/0x160
[  859.599538]  __down_common+0x11f/0x260
[  859.599542]  down+0x47/0x60
[  859.599545]  nv_set_system_power_state+0x47/0x470 [nvidia 1902e767e02db36174b11b490338706a77323218]
[  859.600119]  nv_procfs_write_suspend+0xe1/0x160 [nvidia 1902e767e02db36174b11b490338706a77323218]
[  859.600693]  proc_reg_write+0x5a/0xa0
[  859.600697]  vfs_write+0xf5/0x460
[  859.600702]  ksys_write+0x6d/0xf0
[  859.600705]  do_syscall_64+0x83/0x190
[  859.600709]  ? __alloc_pages+0x182/0x350
[  859.600714]  ? alloc_pages_mpol+0xd7/0x1c0
[  859.600718]  ? __pte_offset_map+0x1b/0x180
[  859.600722]  ? __mod_memcg_lruvec_state+0x94/0x110
[  859.600725]  ? __lruvec_stat_mod_folio+0x68/0xa0
[  859.600729]  ? set_ptes.isra.0+0x28/0x90
[  859.600733]  ? do_anonymous_page+0x3d2/0x710
[  859.600736]  ? __handle_mm_fault+0xc5d/0xe00
[  859.600740]  ? __count_memcg_events+0x4d/0xb0
[  859.600744]  ? count_memcg_events.constprop.0+0x1a/0x30
[  859.600747]  ? handle_mm_fault+0x1f0/0x300
[  859.600751]  ? do_user_addr_fault+0x34e/0x620
[  859.600755]  ? exc_page_fault+0x81/0x190
[  859.600758]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[  859.600763] RIP: 0033:0x77034726a504
[  859.600792] RSP: 002b:00007fff7e2edef8 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
[  859.600796] RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 000077034726a504
[  859.600798] RDX: 0000000000000007 RSI: 00005a32df6d2d50 RDI: 0000000000000001
[  859.600800] RBP: 00007fff7e2edf20 R08: 0000000000000410 R09: 0000000000000001
[  859.600802] R10: 0000000000000004 R11: 0000000000000202 R12: 0000000000000007
[  859.600803] R13: 00005a32df6d2d50 R14: 00007703473445c0 R15: 0000770347341f00
[  859.600807]  </TASK>
[  862.504636] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  862.504650] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  862.504654] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  862.504659] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  863.626664] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  863.626676] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  863.626680] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  863.626685] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  864.165651] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  864.165663] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  864.165667] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  864.165671] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  865.221681] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  865.221693] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  865.221697] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  865.221702] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  865.606681] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  865.606696] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  865.606701] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  865.606706] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  881.908832] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  881.908847] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  881.908851] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  881.908856] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  882.502862] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  882.502875] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  882.502879] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  882.502884] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  889.179905] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  889.179916] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  889.179918] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  889.179921] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  891.258950] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  891.258963] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  891.258967] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  891.258972] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  898.167003] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  898.167017] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  898.167021] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  898.167026] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  899.190010] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  899.190022] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  899.190026] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  899.190031] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  900.818040] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  900.818051] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  900.818054] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  900.818057] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  907.880124] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  907.880139] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  907.880142] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  907.880147] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  912.808175] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  912.808190] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  912.808194] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  912.808199] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  919.408244] pcieport 0000:00:01.3: AER: Multiple Correctable error message received from 0000:03:06.0
[  919.408332] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  919.408336] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000041/00002000
[  919.408341] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  919.408345] pcieport 0000:03:06.0:    [ 6] BadTLP                
[  921.850269] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  921.850285] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  921.850289] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  921.850294] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  922.499274] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  922.499287] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  922.499291] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  922.499296] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  923.885268] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  923.885281] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  923.885285] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  923.885289] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  928.681319] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  928.681334] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  928.681338] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  928.681343] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  929.924348] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  929.924361] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  929.924365] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  929.924369] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  933.081360] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[  933.081374] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  933.081378] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[  933.081383] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[  982.470843] INFO: task nvidia-modeset/:250 blocked for more than 738 seconds.
[  982.470853]       Tainted: P           OE      6.9.6-arch1-1 #1
[  982.470857] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  982.470862] task:nvidia-modeset/ state:D stack:0     pid:250   tgid:250   ppid:2      flags:0x00004000
[  982.470868] Call Trace:
[  982.470869]  <TASK>
[  982.470873]  __schedule+0x3c7/0x1510
[  982.470882]  schedule+0x27/0xf0
[  982.470888]  schedule_preempt_disabled+0x15/0x30
[  982.470892]  rwsem_down_read_slowpath+0x26f/0x4e0
[  982.470898]  ? __pfx__main_loop+0x10/0x10 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  982.470942]  down_read+0x48/0xa0
[  982.470945]  nvkms_kthread_q_callback+0x140/0x160 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  982.470988]  _main_loop+0x95/0x150 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[  982.471031]  kthread+0xcf/0x100
[  982.471035]  ? __pfx_kthread+0x10/0x10
[  982.471039]  ret_from_fork+0x31/0x50
[  982.471043]  ? __pfx_kthread+0x10/0x10
[  982.471046]  ret_from_fork_asm+0x1a/0x30
[  982.471052]  </TASK>
[  982.471123] INFO: task nvidia-sleep.sh:3802 blocked for more than 245 seconds.
[  982.471128]       Tainted: P           OE      6.9.6-arch1-1 #1
[  982.471131] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  982.471135] task:nvidia-sleep.sh state:D stack:0     pid:3802  tgid:3802  ppid:1      flags:0x00000002
[  982.471139] Call Trace:
[  982.471140]  <TASK>
[  982.471142]  __schedule+0x3c7/0x1510
[  982.471146]  ? inode_permission+0x39/0x190
[  982.471150]  ? __d_lookup+0x7e/0xc0
[  982.471153]  ? mntput_no_expire+0x4a/0x260
[  982.471158]  schedule+0x27/0xf0
[  982.471162]  schedule_timeout+0x12f/0x160
[  982.471166]  __down_common+0x11f/0x260
[  982.471170]  down+0x47/0x60
[  982.471173]  nv_set_system_power_state+0x47/0x470 [nvidia 1902e767e02db36174b11b490338706a77323218]
[  982.471748]  nv_procfs_write_suspend+0xe1/0x160 [nvidia 1902e767e02db36174b11b490338706a77323218]
[  982.472323]  proc_reg_write+0x5a/0xa0
[  982.472327]  vfs_write+0xf5/0x460
[  982.472332]  ksys_write+0x6d/0xf0
[  982.472335]  do_syscall_64+0x83/0x190
[  982.472340]  ? __alloc_pages+0x182/0x350
[  982.472345]  ? alloc_pages_mpol+0xd7/0x1c0
[  982.472349]  ? __pte_offset_map+0x1b/0x180
[  982.472353]  ? __mod_memcg_lruvec_state+0x94/0x110
[  982.472357]  ? __lruvec_stat_mod_folio+0x68/0xa0
[  982.472361]  ? set_ptes.isra.0+0x28/0x90
[  982.472365]  ? do_anonymous_page+0x3d2/0x710
[  982.472369]  ? __handle_mm_fault+0xc5d/0xe00
[  982.472373]  ? __count_memcg_events+0x4d/0xb0
[  982.472376]  ? count_memcg_events.constprop.0+0x1a/0x30
[  982.472380]  ? handle_mm_fault+0x1f0/0x300
[  982.472383]  ? do_user_addr_fault+0x34e/0x620
[  982.472387]  ? exc_page_fault+0x81/0x190
[  982.472390]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[  982.472395] RIP: 0033:0x77034726a504
[  982.472422] RSP: 002b:00007fff7e2edef8 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
[  982.472426] RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 000077034726a504
[  982.472429] RDX: 0000000000000007 RSI: 00005a32df6d2d50 RDI: 0000000000000001
[  982.472431] RBP: 00007fff7e2edf20 R08: 0000000000000410 R09: 0000000000000001
[  982.472432] R10: 0000000000000004 R11: 0000000000000202 R12: 0000000000000007
[  982.472434] R13: 00005a32df6d2d50 R14: 00007703473445c0 R15: 0000770347341f00
[  982.472438]  </TASK>
[ 1015.318233] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1015.318250] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1015.318254] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1015.318259] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1017.122231] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1017.122244] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1017.122248] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1017.122253] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1051.079577] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1051.079588] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1051.079590] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1051.079593] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1057.261667] pcieport 0000:00:01.3: AER: Multiple Correctable error message received from 0000:03:06.0
[ 1057.261756] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1057.261760] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1057.261765] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1057.261768] pcieport 0000:03:06.0: AER:   Error of this Agent is reported first
[ 1057.261786] igb 0000:08:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
[ 1057.261789] igb 0000:08:00.0:   device [8086:1539] error status/mask=00001000/00002000
[ 1057.261793] igb 0000:08:00.0:    [12] Timeout               
[ 1086.752951] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1086.752966] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1086.752970] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1086.752975] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1087.610955] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1087.610967] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1087.610971] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1087.610976] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1088.842965] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1088.842975] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1088.842977] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1088.842980] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1096.587072] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1096.587086] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1096.587091] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1096.587095] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1098.556079] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1098.556089] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1098.556091] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1098.556094] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1100.206088] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1100.206101] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1100.206105] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1100.206110] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1101.372119] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1101.372132] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1101.372136] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1101.372141] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1102.890136] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1102.890149] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1102.890153] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1102.890158] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1103.737116] pcieport 0000:00:01.3: AER: Multiple Correctable error message received from 0000:03:06.0
[ 1103.737197] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1103.737199] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1103.737201] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1103.737203] pcieport 0000:03:06.0: AER:   Error of this Agent is reported first
[ 1103.737216] igb 0000:08:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
[ 1103.737217] igb 0000:08:00.0:   device [8086:1539] error status/mask=00001000/00002000
[ 1103.737219] igb 0000:08:00.0:    [12] Timeout               
[ 1105.342370] INFO: task nvidia-modeset/:250 blocked for more than 861 seconds.
[ 1105.342380]       Tainted: P           OE      6.9.6-arch1-1 #1
[ 1105.342385] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1105.342390] task:nvidia-modeset/ state:D stack:0     pid:250   tgid:250   ppid:2      flags:0x00004000
[ 1105.342396] Call Trace:
[ 1105.342397]  <TASK>
[ 1105.342401]  __schedule+0x3c7/0x1510
[ 1105.342410]  schedule+0x27/0xf0
[ 1105.342416]  schedule_preempt_disabled+0x15/0x30
[ 1105.342420]  rwsem_down_read_slowpath+0x26f/0x4e0
[ 1105.342426]  ? __pfx__main_loop+0x10/0x10 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[ 1105.342470]  down_read+0x48/0xa0
[ 1105.342473]  nvkms_kthread_q_callback+0x140/0x160 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[ 1105.342516]  _main_loop+0x95/0x150 [nvidia_modeset 8311054b3353fe914596dfb30979ad09ed860151]
[ 1105.342558]  kthread+0xcf/0x100
[ 1105.342563]  ? __pfx_kthread+0x10/0x10
[ 1105.342566]  ret_from_fork+0x31/0x50
[ 1105.342571]  ? __pfx_kthread+0x10/0x10
[ 1105.342574]  ret_from_fork_asm+0x1a/0x30
[ 1105.342579]  </TASK>
[ 1105.342653] INFO: task nvidia-sleep.sh:3802 blocked for more than 368 seconds.
[ 1105.342658]       Tainted: P           OE      6.9.6-arch1-1 #1
[ 1105.342662] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1105.342665] task:nvidia-sleep.sh state:D stack:0     pid:3802  tgid:3802  ppid:1      flags:0x00000002
[ 1105.342670] Call Trace:
[ 1105.342671]  <TASK>
[ 1105.342673]  __schedule+0x3c7/0x1510
[ 1105.342676]  ? inode_permission+0x39/0x190
[ 1105.342680]  ? __d_lookup+0x7e/0xc0
[ 1105.342683]  ? mntput_no_expire+0x4a/0x260
[ 1105.342689]  schedule+0x27/0xf0
[ 1105.342693]  schedule_timeout+0x12f/0x160
[ 1105.342697]  __down_common+0x11f/0x260
[ 1105.342701]  down+0x47/0x60
[ 1105.342704]  nv_set_system_power_state+0x47/0x470 [nvidia 1902e767e02db36174b11b490338706a77323218]
[ 1105.343280]  nv_procfs_write_suspend+0xe1/0x160 [nvidia 1902e767e02db36174b11b490338706a77323218]
[ 1105.343853]  proc_reg_write+0x5a/0xa0
[ 1105.343857]  vfs_write+0xf5/0x460
[ 1105.343861]  ksys_write+0x6d/0xf0
[ 1105.343864]  do_syscall_64+0x83/0x190
[ 1105.343869]  ? __alloc_pages+0x182/0x350
[ 1105.343874]  ? alloc_pages_mpol+0xd7/0x1c0
[ 1105.343878]  ? __pte_offset_map+0x1b/0x180
[ 1105.343882]  ? __mod_memcg_lruvec_state+0x94/0x110
[ 1105.343886]  ? __lruvec_stat_mod_folio+0x68/0xa0
[ 1105.343889]  ? set_ptes.isra.0+0x28/0x90
[ 1105.343893]  ? do_anonymous_page+0x3d2/0x710
[ 1105.343897]  ? __handle_mm_fault+0xc5d/0xe00
[ 1105.343901]  ? __count_memcg_events+0x4d/0xb0
[ 1105.343905]  ? count_memcg_events.constprop.0+0x1a/0x30
[ 1105.343908]  ? handle_mm_fault+0x1f0/0x300
[ 1105.343911]  ? do_user_addr_fault+0x34e/0x620
[ 1105.343915]  ? exc_page_fault+0x81/0x190
[ 1105.343918]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 1105.343923] RIP: 0033:0x77034726a504
[ 1105.343951] RSP: 002b:00007fff7e2edef8 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
[ 1105.343955] RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 000077034726a504
[ 1105.343957] RDX: 0000000000000007 RSI: 00005a32df6d2d50 RDI: 0000000000000001
[ 1105.343959] RBP: 00007fff7e2edf20 R08: 0000000000000410 R09: 0000000000000001
[ 1105.343961] R10: 0000000000000004 R11: 0000000000000202 R12: 0000000000000007
[ 1105.343963] R13: 00005a32df6d2d50 R14: 00007703473445c0 R15: 0000770347341f00
[ 1105.343966]  </TASK>
[ 1105.343967] Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings
[ 1117.630289] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1117.630304] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1117.630308] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1117.630313] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1120.138288] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1120.138297] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1120.138300] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1120.138303] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1125.264340] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1125.264350] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1125.264352] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1125.264354] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1128.124374] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1128.124390] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1128.124394] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1128.124399] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1148.254584] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1148.254600] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1148.254604] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1148.254609] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1151.554638] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1151.554653] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1151.554657] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1151.554662] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1152.808624] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1152.808635] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1152.808638] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1152.808641] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1154.656649] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1154.656664] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1154.656668] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1154.656673] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1155.129652] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1155.129666] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1155.129670] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1155.129675] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1155.690655] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1155.690665] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1155.690667] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1155.690671] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1157.824684] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1157.824698] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1157.824702] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1157.824707] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1160.981737] pcieport 0000:00:01.3: AER: Multiple Correctable error message received from 0000:03:06.0
[ 1160.981827] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1160.981847] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1160.981852] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1160.981856] pcieport 0000:03:06.0: AER:   Error of this Agent is reported first
[ 1160.981873] igb 0000:08:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
[ 1160.981876] igb 0000:08:00.0:   device [8086:1539] error status/mask=00001000/00002000
[ 1160.981880] igb 0000:08:00.0:    [12] Timeout               
[ 1160.992713] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1169.187822] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1169.187838] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1169.187842] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1169.187847] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1170.265832] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1170.265845] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1170.265849] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1170.265854] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1178.174891] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1178.174907] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1178.174911] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1178.174916] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1181.969942] pcieport 0000:00:01.3: AER: Multiple Correctable error message received from 0000:03:06.0
[ 1181.970028] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1181.970030] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1181.970033] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1181.970035] pcieport 0000:03:06.0: AER:   Error of this Agent is reported first
[ 1181.970050] igb 0000:08:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
[ 1181.970051] igb 0000:08:00.0:   device [8086:1539] error status/mask=00001000/00002000
[ 1181.970053] igb 0000:08:00.0:    [12] Timeout               
[ 1702.627307] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1702.627324] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1702.627327] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1702.627332] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1731.502601] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1731.502617] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1731.502621] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1731.502627] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1734.890661] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1734.890677] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1734.890681] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1734.890686] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)
[ 1736.782680] pcieport 0000:00:01.3: AER: Correctable error message received from 0000:03:06.0
[ 1736.782695] pcieport 0000:03:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 1736.782699] pcieport 0000:03:06.0:   device [1022:43b4] error status/mask=00000001/00002000
[ 1736.782704] pcieport 0000:03:06.0:    [ 0] RxErr                  (First)

0a:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4]
        Flags: bus master, fast devsel, latency 0, IRQ 45, IOMMU group 15
        Memory at f5000000 (32-bit, non-prefetchable) [size=16M]
        Memory at 7fe0000000 (64-bit, prefetchable) [size=256M]
        Memory at 7ff0000000 (64-bit, prefetchable) [size=32M]
        I/O ports at d000 [size=128]
        Expansion ROM at f6000000 [virtual] [disabled] [size=512K]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express Legacy Endpoint, IntMsgNum 0
        Capabilities: [100] Virtual Channel
        Capabilities: [258] L1 PM Substates
        Capabilities: [128] Power Budgeting <?>
        Capabilities: [420] Advanced Error Reporting
        Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
        Capabilities: [900] Secondary PCI Express
        Capabilities: [bb0] Physical Resizable BAR
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia

$ sudo systemctl status nvidia-suspend.service 
○ nvidia-suspend.service - NVIDIA system suspend actions
     Loaded: loaded (/usr/lib/systemd/system/nvidia-suspend.service; enabled; preset: disabled)
     Active: inactive (dead) since Mon 2024-06-24 13:44:50 CEST; 5h 41min ago
 Invocation: 6e7cce48e3ed421eac20c49ead0f0f21
    Process: 3559 ExecStart=/usr/bin/logger -t suspend -s nvidia-suspend.service (code=exited, status=0/SUCCESS)
    Process: 3561 ExecStart=/usr/bin/nvidia-sleep.sh suspend (code=exited, status=0/SUCCESS)
   Main PID: 3561 (code=exited, status=0/SUCCESS)

giu 24 13:44:48 ARCH-RYZEN systemd[1]: Starting NVIDIA system suspend actions...
giu 24 13:44:48 ARCH-RYZEN suspend[3559]: nvidia-suspend.service
giu 24 13:44:48 ARCH-RYZEN logger[3559]: <13>Jun 24 13:44:48 suspend: nvidia-suspend.service
giu 24 13:44:50 ARCH-RYZEN systemd[1]: nvidia-suspend.service: Deactivated successfully.
giu 24 13:44:50 ARCH-RYZEN systemd[1]: Finished NVIDIA system suspend actions.

$ sudo systemctl status nvidia-resume.service 
● nvidia-resume.service - NVIDIA system resume actions
     Loaded: loaded (/usr/lib/systemd/system/nvidia-resume.service; enabled; preset: disabled)
     Active: activating (start) since Mon 2024-06-24 19:22:13 CEST; 4min 23s ago
 Invocation: bff8c46a3a704f11a7bca97d63ec5344
    Process: 3800 ExecStart=/usr/bin/logger -t suspend -s nvidia-resume.service (code=exited, status=0/SUCCESS)
   Main PID: 3802 (nvidia-sleep.sh)
      Tasks: 1 (limit: 18938)
     Memory: 384K (peak: 1.8M)
        CPU: 14ms
     CGroup: /system.slice/nvidia-resume.service
             └─3802 /bin/bash /usr/bin/nvidia-sleep.sh resume

giu 24 19:22:13 ARCH-RYZEN systemd[1]: Starting NVIDIA system resume actions...
giu 24 19:22:13 ARCH-RYZEN suspend[3800]: nvidia-resume.service
giu 24 19:22:13 ARCH-RYZEN logger[3800]: <13>Jun 24 19:22:13 suspend: nvidia-resume.service

$ cat /proc/cmdline 
root=UUID=09d75b07-d5bc-4888-aef2-ca3c7c2d5daa rw iommu=memaper module_blacklist=ntfs,ntfs3,sp5100-tco usb-storage.quirks=0bda:9210:u sysrq_always_enabled=1 nvidia.NVreg_TemporaryFilePath="/var/tmp" nvidia.NVreg_EnableGpuFirmware=1 nvidia.NVreg_UsePageAttributeTable=1 nvidia.NVreg_PreserveVideoMemoryAllocations=1 nvidia_drm.fbdev=1 nvidia_drm.modeset=1 zswap.enabled=0 mitigations=off nowatchdog nmi_watchdog=0 tsc=reliable clocksource=tsc initrd=\boot\initramfs-linux.img

$ cat /etc/modprobe.d/*nvidia*
options nvidia NVreg_EnableGpuFirmware=1 NVreg_UsePageAttributeTable=1 NVreg_TemporaryFilePath="/var/tmp" NVreg_PreserveVideoMemoryAllocations=1
options nvidia_drm fbdev=1 modeset=1

Here's the journalctl while machine is still running (taken from remote ssh 'cause NO video output)

Also, I cannot reboot:

# LC_ALL=C systemctl reboot 
Call to Reboot failed: Transaction for reboot.target/start is destructive (nvidia-resume.service has 'start' job queued, but 'stop' is included in transaction).
Failed to start reboot.target: Transaction for reboot.target/start is destructive (nvidia-resume.service has 'start' job queued, but 'stop' is included in transaction).
See system logs and 'systemctl status reboot.target' for details.

Last edited by d.ALT (2024-06-24 17:46:59)

d.ALT · 2024-06-25 22:21:41

OK, solved (for me).
Removing any nvidia related configuration \ customization made suspension works fine again: till now, so far so good.

No need (again, for me) to explicitly declare nvidia_drm.fbdev=1 and nvidia_drm.modeset=1 as Kernel Parameters nor via .conf files into /etc/modprobe/.

$ cat /proc/cmdline 
root=UUID=09d75b07-d5bc-4888-aef2-ca3c7c2d5daa rw module_blacklist=ntfs,ntfs3,sp5100-tco usb-storage.quirks=0bda:9210:u sysrq_always_enabled=1 zswap.enabled=0 mitigations=off nowatchdog nmi_watchdog=0 tsc=reliable clocksource=tsc initrd=\boot\initramfs-linux.img

.

$ grep \#MODULE /etc/mkinitcpio.conf
#MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

.

$ sudo systemctl list-unit-files --type=service --all --no-pager | grep -i nvidia
nvidia-hibernate.service                     disabled        disabled
nvidia-persistenced.service                  disabled        disabled
nvidia-powerd.service                        disabled        disabled
nvidia-resume.service                        disabled        disabled
nvidia-suspend.service                       disabled        disabled

.

$ cat /proc/driver/nvidia/gpus/0000\:0a\:00.0/information
Model:           NVIDIA GeForce GTX 1660 SUPER
IRQ:             111
GPU UUID:        GPU-e742497b-03c4-19ce-062d-a5e95dcd5b5c
Video BIOS:      90.16.4d.00.32
Bus Type:        PCIe
DMA Size:        47 bits
DMA Mask:        0x7fffffffffff
Bus Location:    0000:0a:00.0
Device Minor:    0
GPU Excluded:    No

.

$ cat /proc/driver/nvidia/gpus/0000\:0a\:00.0/power
Runtime D3 status:          Disabled by default
Video Memory:               Active

GPU Hardware Support:
 Video Memory Self Refresh: Not Supported
 Video Memory Off:          Supported

.

$ cat /proc/driver/nvidia/gpus/0000\:0a\:00.0/registry
Binary: ""

Last edited by d.ALT (2024-06-25 22:22:11)

obap74 · 2024-08-28 10:56:22

(GTX 970) Still broken for me with linux 6.10.6.arch1-1 + nvidia 560.35.03-1 (black screen / machine completely unresponsive after first resume from suspend).
Same with linux-lts 6.6.47-1 + nvidia-lts 560.35.03-1 but I could resume one time. It broke the second time.

Anyone else tried 560?

juneidy · 2024-08-28 22:14:12

Looks like my problem is back again.

GTX 970; linux 6.10.6-arch1-1; nvidia 560.35.03-1

Tried to remove NVreg_PreserveVideoMemoryAllocations=1 kernel parameter that I had before also no luck. The TTY2 and TTY7 swapping trick also doesn't work anymore.

Edit: This is probably obvious, but just adding more info that my other machine with RTX 3070Ti is fine.

Last edited by juneidy (2024-08-28 22:16:51)

seth · 2024-08-29 06:39:53

535xx still fine?
Have you tried to play around w/ nvidia-drm.fbdev=1|0 ?

obap74 · 2024-08-29 19:16:40

seth wrote:

535xx still fine?

Yes, still no issue whatshoever with 6.1+535 (also on my Gentoo install). Currently using

local/linux-lts61 6.1.106-1
local/linux-lts61-headers 6.1.106-1
local/lib32-nvidia-535xx-utils 535.183.01-1
local/nvidia-535xx-dkms 535.183.01-2
local/nvidia-535xx-utils 535.183.01-2

seth wrote:

Have you tried to play around w/ nvidia-drm.fbdev=1|0 ?

Unfortunately, I haven't when trying 560. I will try when I have some time to tinker and report back. Thanks for the suggestion.

obap74 · 2024-09-21 11:37:53

Another batch of tests with linux 6.10.10.arch1-1 + nvidia 560.35.03-6

nvidia_drm.modeset=1 nvidia_drm.fbdev=1 nvidia.NVreg_PreserveVideoMemoryAllocations=1 - When triggering suspend, the screen locks but the system doesn't enter suspend state. After unlocking my session, I'm back to the desktop. The system doesn't suspend. I switched PreserveVideoMemoryAllocations back to 0 for the other combinations because I never had luck with it being enabled (see OP).

nvidia_drm.modeset=1 nvidia_drm.fbdev=1 nvidia.NVreg_PreserveVideoMemoryAllocations=0 - The system enters suspend state just fine. When resuming, all I get is a TTY with what seems to be dmesg output continuously printing. I cannot switch to any other TTY. I think I can still enter my user password at this point but I keep coming back to "login:" prompt. It seems that X won't start anymore.

[*}nvidia_drm.modeset=0 nvidia_drm.fbdev=1 nvidia.NVreg_PreserveVideoMemoryAllocations=0 - The system enters suspend state just fine. When resuming: black screen, cannot switch to any TTY, forced to reboot. Same with linux-lts 6.6.52-1 + nvidia-lts 1:560.35.03-7.

nvidia_drm.modeset=0 nvidia_drm.fbdev=0 nvidia.NVreg_PreserveVideoMemoryAllocations=0 - The system enters suspend state just fine. When resuming: black screen, cannot switch to any TTY, forced to reboot.

nvidia_drm.modeset=1 nvidia_drm.fbdev=0 nvidia.NVreg_PreserveVideoMemoryAllocations=0 - The system enters suspend state just fine. When resuming: black screen, cannot switch to any TTY, forced to reboot.

Also tried a few combinations with nvidia-{hibernate,resume,suspend}.service units disabled, same results.

Testing the different combinations takes quite a lot of time unfortunately. I haven't bothered trying other combinations with 6.6 kernel after seeing identical behavior with nvidia_drm.modeset=0 nvidia_drm.fbdev=1 nvidia.NVreg_PreserveVideoMemoryAllocations=0.

Back to 6.1 + 535.

bWpdZW8n · 2024-09-23 17:57:44

Hi guys, I think I found a workaround!

I'm using `systemd 256.6-1`, `nvidia 560.35.03-6`, `nvidia-utils 560.35.03-3`,
`linux 6.10.10.arch1-1`, `linux-firmware 20240909.552ed9b8-1`, `gdm 47.0-1 (gnome)`.
GPU is GTX 960.

Also, I'm using Wayland, so I followed the instructions on the [wiki](https://wiki.archlinux.org/title/GDM#Wa … DIA_driver).
This is how my `/etc/modprobe.d/nvidia.conf` looks like:

```
options nvidia_drm modeset=1 fbdev=1
options nvidia NVreg_PreserveVideoMemoryAllocations=1 NVreg_TemporaryFilePath=/var/tmp
```

`nvidia-utils 560.35.03-3` comes with two drop-in configuration files.
Their locations and contents are as follows:

1. `/usr/lib/systemd/system/systemd-suspend.service.d/10-nvidia-no-freeze-session.conf`

```
[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"
```

2. `/usr/lib/systemd/system/systemd-homed.service.d/10-nvidia-no-freeze-session.conf`

```
[Service]
Environment="SYSTEMD_HOME_LOCK_FREEZE_SESSION=false"
```

Those two files are meant to fix the problem mentioned in [this post #115](https://bbs.archlinux.org/viewtopic.php … 2#p2179302)
or [this Debian bug report](https://www.mail-archive.com/debian-bug … 74582.html).

That was a few months ago. The community came up with this solution and I guess nvidia developers adopted it.

But now this solution is backfiring.

For the latest packages you should remain these two variables to their default values which are `true`.
([systemd docs: ENVIRONMENT](https://github.com/systemd/systemd/blob … ONMENT.md))

You can remove these two drop-in files, but they will be re-added after updating the `nvidia-utils` packages.

I know this because a few days ago, I upgraded `nvidia-utils` from `560.35.03-2` to `560.35.03-3`.
Before the upgrade, I removed both drop-in files, and the resume worked fine.
After the upgrade, the resume was broken. (Black screen, no display output.)

So a better approach is to add two override drop-in files under `/etc/`.
(They have higher priority compared to files in `/usr/`. [SYSTEMD-SYSTEM.CONF(5)](https://manpages.debian.org/testing/sys … 5.en.html))

Here is my solution. I added two files (or use `systemctl edit`), they are:

1. `/etc/systemd/system/systemd-suspend.service.d/enable-freeze-session.conf`

```
[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=true"
```

2. `/etc/systemd/system/systemd-homed.service.d/enable-freeze-session.conf`

```
[Service]
Environment="SYSTEMD_HOME_LOCK_FREEZE_SESSION=true"
```

And `systemctl daemon-reload`.

I think this is a temporary solution, things come and go.

(After setting `NVreg_PreserveVideoMemoryAllocations=1`, suspend and resume take longer to complete.)
(This is a solution for suspend, I'm not using hibernate.)

bertieb · 2024-09-25 11:04:21

bWpdZW8n wrote:

Hi guys, I think I found a workaround!
I'm using `systemd 256.6-1`, `nvidia 560.35.03-6`, `nvidia-utils 560.35.03-3`,
`linux 6.10.10.arch1-1`, `linux-firmware 20240909.552ed9b8-1`, `gdm 47.0-1 (gnome)`.
GPU is GTX 960.

tl;dr- this seems to work? (with one caveat, see appended edit)

I tried the process outlined by @bWpdZW8n -- switched from LTS 6.1 to 6.10.10, nvidia 535 to 560.35.03.

I created the override directories and files as outlined. At that point I ran into a problem: "systemctl suspend" asked for authentication, and then failed with:

journal wrote:

Sep 25 11:46:12 zeus kernel: NVRM: GPU 0000:08:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
Sep 25 11:46:12 zeus kernel: nvidia 0000:08:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5
Sep 25 11:46:12 zeus kernel: nvidia 0000:08:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5
Sep 25 11:46:12 zeus kernel: nvidia 0000:08:00.0: PM: failed to suspend async: error -5
Sep 25 11:46:12 zeus kernel: PM: Some devices failed to suspend, or early wake event detected
Sep 25 11:46:12 zeus kernel: serial 00:04: activated
Sep 25 11:46:12 zeus kernel: nvme nvme0: 8/0/0 default/read/poll queues
Sep 25 11:46:12 zeus kernel: nvme nvme1: D3 entry latency set to 10 seconds
Sep 25 11:46:12 zeus kernel: nvme nvme1: 16/0/0 default/read/poll queues
Sep 25 11:46:12 zeus kernel: r8169 0000:07:00.0 enp7s0: Link is Down
Sep 25 11:46:12 zeus kernel: OOM killer enabled.
Sep 25 11:46:12 zeus kernel: Restarting tasks ... done.
Sep 25 11:46:12 zeus kernel: random: crng reseeded on system resumption
Sep 25 11:46:12 zeus kernel: PM: suspend exit
Sep 25 11:46:12 zeus systemd-sleep[26712]: Failed to put system to sleep. System resumed again: Input/output error

I had to enable some units:

$ systemctl list-unit-files | grep nvidia
nvidia-hibernate.service                     enabled         disabled
nvidia-persistenced.service                  enabled         disabled
nvidia-powerd.service                        enabled         disabled
nvidia-resume.service                        enabled         disabled
nvidia-suspend.service                       enabled         disabled

All were disabled initially. The 'hibernate' one probably isn't needed as I suspend instead, but to test all were enabled.

I suspended and resumed three times in a row without issue. I'll edit this post or reply if a problem develops.

Time to engage 'cautious optimism' mode?

Edit: forgot to mention one issue- on startup I log in at a console then start a graphical session manually via startx; however the console display now freezes at 'Finished Rebuild Dynamic Linker Cache':

journal wrote:

Sep 25 12:50:12 zeus systemd[1]: Starting Record System Boot/Shutdown in UTMP...
Sep 25 12:50:12 zeus systemd[1]: Finished Record System Boot/Shutdown in UTMP.
Sep 25 12:50:12 zeus systemd[1]: Finished Rebuild Journal Catalog.
Sep 25 12:50:12 zeus systemd[1]: Finished Rebuild Dynamic Linker Cache.
Sep 25 12:50:12 zeus systemd[1]: Starting Update is Completed...
Sep 25 12:50:12 zeus kernel: logitech-djreceiver 0003:046D:C534.0004: hiddev97,hidraw3: USB HID v1.11 Mouse [Logite>
Sep 25 12:50:12 zeus kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:08:00.0 on minor 1

I assume it 'freezes' display because nvidia-drm / modeset kicks in, though I don't understand that process well enough to be sure. In any case, the system itself is responsive- I can log in and start a session 'blindly' by typing username/password combo followed by startx as usual.

Last edited by bertieb (2024-09-25 11:58:27)

Arch Linux

#101 2024-03-11 01:31:53

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#102 2024-03-11 07:57:48

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#103 2024-03-11 15:46:56

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#104 2024-03-11 15:52:20

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#105 2024-03-18 01:03:52

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#106 2024-03-18 11:51:37

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#107 2024-04-03 17:19:44

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#108 2024-04-03 18:20:59

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#109 2024-04-03 18:32:18

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#110 2024-04-21 07:16:47

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#111 2024-05-13 09:17:05

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#112 2024-05-13 17:08:50

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#113 2024-06-10 09:36:14

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#114 2024-06-22 11:20:24

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#115 2024-06-22 13:43:58

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#116 2024-06-22 14:19:53

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#117 2024-06-24 17:45:38

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#118 2024-06-25 22:21:41

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#119 2024-08-28 10:56:22

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#120 2024-08-28 22:14:12

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#121 2024-08-29 06:39:53

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#122 2024-08-29 19:16:40

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#123 2024-09-21 11:37:53

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#124 2024-09-23 17:57:44

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

#125 2024-09-25 11:04:21

Re: NVIDIA - cannot resume from suspend with PreserveVideoMemoryAllocation

Board footer