Arch Linux

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Hello! I've just finished my first arch install yesterday and everything has been going well and easy so far. but the disk activity light on my pcs case and my ssd is consistently glowing. I cant find a reason as to why its always glowing tho. I stay on often but flickers sometimes. i checked iotop a fair bit and the only activity that was happening was firefox and jb2 but it was happening periodically.

I am using Kde and have disabled the file indexing in the settings but it seems to be of no help. Im also dual booting with windows installed.
I am still not very experienced with linux yet so im unable to pinpoint the specific thing thats causing the issue

Edit 1:

My initial issue as been fixed mentioned in post #16 but my issue with sleep not working has still not been fixed so far

Last edited by Reyyanfr (2024-09-07 20:45:35)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,060

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Im also dual booting with windows installed.

https://wiki.archlinux.org/title/Dual_boot_with_Windows
Pay special attention to section 1.4 and disable fast startup & hibernation from inside windows .

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

https://wiki.archlinux.org/title/Dual_boot_with_Windows
Pay special attention to section 1.4 and disable fast startup & hibernation from inside windows .

i have disabled fast startup and hibernation in my windows install. while i was investigating this i also found out sleep mode does not work. It leads me to a black screen but nothing appears to load up. Could that be a reason?

Last edited by Reyyanfr (2024-08-16 13:33:15)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,060

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

I know little about sleep/suspend , maybe https://wiki.archlinux.org/title/Power_ … _hibernate helps ?

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,813

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Please post

cat /sys/power/mem_sleep # for the sleep
grep . /sys/class/scsi_host/host*/link_power_management_policy # for your drive - https://wiki.archlinux.org/title/Power_management#SATA_Active_Link_Power_Management

and a system journal *after* attempting to sleep

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Can you

sudo hdparm -C /dev/sda
sudo hdparm -Y /dev/sda
sudo hdparm -C /dev/sda

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Please post

cat /sys/power/mem_sleep # for the sleep

This is what i got:

$ cat /sys/power/mem_sleep
s2idle [deep]

And for this

grep . /sys/class/scsi_host/host*/link_power_management_policy # for your drive - https://wiki.archlinux.org/title/Power_management#SATA_Active_Link_Power_Management

I got this:

$ grep . /sys/class/scsi_host/host*/link_power_management_policy
/sys/class/scsi_host/host0/link_power_management_policy:med_power_with_dipm
/sys/class/scsi_host/host1/link_power_management_policy:med_power_with_dipm
/sys/class/scsi_host/host2/link_power_management_policy:med_power_with_dipm
/sys/class/scsi_host/host3/link_power_management_policy:med_power_with_dipm
/sys/class/scsi_host/host4/link_power_management_policy:med_power_with_dipm
/sys/class/scsi_host/host5/link_power_management_policy:med_power_with_dipm

and a system journal *after* attempting to sleep

sudo journalctl -b | curl -F 'file=@-' 0x0.st

heres the journal: http://0x0.st/X4Uw.txt

Can you

sudo hdparm -C /dev/sda
sudo hdparm -Y /dev/sda
sudo hdparm -C /dev/sda

i did this with the only drive thats mounted right now which is nvme0n1

$ sudo hdparm -C /dev/nvme0n1

/dev/nvme0n1:
 drive state is:  unknown
$ sudo hdparm -Y /dev/nvme0n1

/dev/nvme0n1:
 issuing sleep command
 HDIO_DRIVE_CMD(sleep) failed: Inappropriate ioctl for device
$ sudo hdparm -C /dev/nvme0n1

/dev/nvme0n1:
 drive state is:  unknown

I tried this command with sda

$ sudo hdparm -C /dev/sda

/dev/sda:
SG_IO: bad/missing sense data, sb[]:  f0 00 01 00 50 40 ff 0a 00 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 drive state is:  unknown

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,813

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

The journal doesn't cover an S3 cycle/attempt?
Next to the nvme, there's a western digital spinner on sdb and a samsung SSD on sda and a dvd drive.
Are any of those mouted?
Can you boot/run the system w/o mounting anything on those drives (and what'S the impact on your LED)?
Or even w/o powering them (so we can narrow down on what's driving the IO LED) - esp. the DVD drive?

sudo hdparm -C /dev/sdb # this will likely work for the WD drive, but nb. that the sda/sdb enumeration isn't determinisitic and might change w/ a reboot

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

The journal doesn't cover an S3 cycle/attempt?
Next to the nvme, there's a western digital spinner on sdb and a samsung SSD on sda and a dvd drive.
Are any of those mouted?

None of them are mounted to anything to my knowledge. The entire filesystem is on the nvme drive

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p4
UUID=d01e6fc9-5871-4a77-b083-d49e7178b943       /               ext4            rw,relatime     0 1

# /dev/nvme0n1p7
UUID=0e5d822b-d472-4295-bac1-6b03a6ebc3e9       /home           ext4            rw,relatime     0 2

# /dev/nvme0n1p1
UUID=FE59-5BEB          /efi            vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro   0 2

# /dev/nvme0n1p6
UUID=4e88964b-0a5c-4910-8b29-5064f4755664       none            swap            defaults        0 0

Can you boot/run the system w/o mounting anything on those drives (and what'S the impact on your LED)?
Or even w/o powering them (so we can narrow down on what's driving the IO LED) - esp. the DVD drive?

i will unplug the sata connectors on them and see if any of them make a difference. will let you know

sudo hdparm -C /dev/sdb # this will likely work for the WD drive, but nb. that the sda/sdb enumeration isn't determinisitic and might change w/ a reboot

i ran this command

$ sudo hdparm -C /dev/sdb

/dev/sdb:
SG_IO: bad/missing sense data, sb[]:  f0 00 01 00 50 40 ff 0a 00 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 drive state is:  unknown

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Can you boot/run the system w/o mounting anything on those drives (and what'S the impact on your LED)?
Or even w/o powering them (so we can narrow down on what's driving the IO LED) - esp. the DVD drive?

I have taken all the drives off the system. First the DVD drive which appeared to not make any difference.
Next up i took the sata and power cables off the western digital drive and samsung drive. but they didnt make any difference either. The led is still very lit on both my pc and nvme

Last edited by Reyyanfr (2024-08-18 07:27:03)

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

plugged it all back and nothing has changed. the led indicator remains the same

Last edited by Reyyanfr (2024-08-18 07:36:32)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,813

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Did sda and sdb swap order in #8 (ie. did you test the same drive as before? Try to query both at the same time)

Either way, seems the nvme is generating the IO - if anything.
The lights don't show up in windows (ie. this isn't just the board powering the wrong LED for no reason)?
Did you disable fast-start just now or longer ago?
Because
1. at least anecdotally you've to restart windows at least twice to convince the ACPI it's not hibernating after disabling that feature
2. windows frequently re-enables this with updates, so just because you disabled it a month ago doesn't mean it still is

If it's not the dualboot situation and there's no iotop activity, see https://wiki.archlinux.org/title/Solid_ … ing_(APST)
How does the system btw. behave when booting the install iso from usb and not mouting the nvme?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Hello sorry for the late response ive been somewhat busy

Did sda and sdb swap order in #8 (ie. did you test the same drive as before? Try to query both at the same time)

They did not swap order as far as im seeing

Either way, seems the nvme is generating the IO - if anything.
The lights don't show up in windows (ie. this isn't just the board powering the wrong LED for no reason)?
Did you disable fast-start just now or longer ago?
Because
1. at least anecdotally you've to restart windows at least twice to convince the ACPI it's not hibernating after disabling that feature
2. windows frequently re-enables this with updates, so just because you disabled it a month ago doesn't mean it still is

The lights do not stay always on in windows so yes i dont think its the board powering the led for no reason
I disabled fast startup before the installation of arch because when i was using linux mint i could not access the files cause it was read only

1. I have restarted windows multiple times and i dont believe its hibernating
2. I have completely disabled windows updates

If it's not the dualboot situation and there's no iotop activity, see https://wiki.archlinux.org/title/Solid_ … ing_(APST)
How does the system btw. behave when booting the install iso from usb and not mouting the nvme?

Will check this out

Im not sure about the usb as i didnt pay attention to that but i will check to see if the case is the same
I also noticed that the led stay on like that even in grub. What does that indicate?

Last edited by Reyyanfr (2024-08-24 10:22:02)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,813

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

grub boots from the nvme, right?

So it'll certainly activate and in doubt wait for the OS to power it down.
Does powertop indicate power draw from the nvme?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

grub boots from the nvme, right?

So it'll certainly activate and in doubt wait for the OS to power it down.

i see

Does powertop indicate power draw from the nvme?

It seems like it does. When i go to device stats i can see the nvme controller using 100% power

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,813

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

smartctl -c /dev/nvme0

and see https://wiki.archlinux.org/title/Solid_ … ST_support again, try to set a latency that will allow the nvme to power down  (unless the values there look completely whacko)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

smartctl -c /dev/nvme0

and see https://wiki.archlinux.org/title/Solid_ … ST_support again, try to set a latency that will allow the nvme to power down  (unless the values there look completely whacko)

ive decided to disable apst with the kernal parameter nvme_core.default_ps_max_latency_us=0 and it seems to not always stay on anymore so i think that may have fixed the issue.

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Hello. After a while of not wanting to do anything i have tried again to fix the issues. The hdd io light appears to be working as normal now that ive used it for a while. but unfortunately i still am having no luck with trying to fix both sleep and hibernate. i have try a few things tho

1. I have switched to the lts kernal but it seems to be the same
2. I tried using s2idle which does not turn the pc off but when i press the power button my devices light up but still no display.
3. Hibernation appears to find the hibernation image and spits alot of text on my screen and after a while nothing happens but when i to tty2 using ctrl + alt + f2 the system appears to freeze up completely when before that i would show the cursor blinking ie. the desktop doesnt load

i have noticed sometimes i get a black screen and sometimes i get no output at all. Im not sure if this is due to me fiddling around or not but it is to be mentioned

Last edited by Reyyanfr (2024-09-07 20:53:43)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,813

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Can you suspend/hibernate & resume from
1. the multi-user.target only (2nd link below)
2. the multi-user.target along "nomodeset"?

And/or

but when i to tty2 using ctrl + alt + f2 the system appears to freeze up completely

Can you try to ssh into the system instead?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Can you suspend/hibernate & resume from
1. the multi-user.target only (2nd link below)
2. the multi-user.target along "nomodeset"?

And/or

but when i to tty2 using ctrl + alt + f2 the system appears to freeze up completely

Can you try to ssh into the system instead?

1. When i suspend from multi-user.target i am able to suspend but unable to resume
2. Its the same with both multi-user.target and "nomodeset" kernal parameter

I am able to ssh into the system after powering it on

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,813

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

I am able to ssh into the system after powering it on

Ok, but also after resuming?
We want to get access to the system to see whether it's only the graphics stack and ideally extract some data from it.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

I am able to ssh into the system after powering it on

Ok, but also after resuming?
We want to get access to the system to see whether it's only the graphics stack and ideally extract some data from it.

Yes i am able to access ssh after resuming and it seems to be constant. i am able to go back to sleep aswell using systemctl suspend

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,813

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Spledid.
Please post your complete system journal for the boot after a "failed" resume:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Spledid.
Please post your complete system journal for the boot after a "failed" resume:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

http://0x0.st/Xxrt.txt

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,813

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Sep 09 04:37:32 reyyanarch kernel: ------------[ cut here ]------------
Sep 09 04:37:32 reyyanarch kernel: WARNING: CPU: 3 PID: 4324 at /build/nvidia-lts/src/nvidia/560.35.03/build/nvidia/nv.c:4310 nv_restore_user_channels+0x4e/0x1d0 [nvidia]
Sep 09 04:37:32 reyyanarch kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device intel_rapl_msr intel_rapl_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_soc_avs snd_soc_hda_codec snd_hda_ext_core irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 psmouse sha256_ssse3 vfat sha1_ssse3 fat serio_raw aesni_intel atkbd libps2 crypto_simd eeepc_wmi snd_soc_core snd_hda_codec_realtek iTCO_wdt asus_wmi vivaldi_fmap intel_pmc_bxt sparse_keymap cryptd snd_hda_codec_generic platform_profile mei_pxp mei_hdcp ee1004 iTCO_vendor_support ledtrig_audio snd_compress ac97_bus snd_pcm_dmaengine rapl snd_hda_codec_hdmi nvidia_drm(POE) i8042 mei_me snd_hda_intel uinput intel_cstate nvidia_modeset(POE) snd_intel_dspcfg i2c_i801 serio snd_intel_sdw_acpi intel_uncore rfkill wmi_bmof pcspkr e1000e i2c_smbus snd_hda_codec mei nvidia_uvm(POE) snd_hda_core cdc_acm snd_hwdep acpi_pad mousedev joydev mac_hid nvidia(POE) snd_aloop snd_pcm
Sep 09 04:37:32 reyyanarch kernel:  snd_timer snd soundcore i2c_dev crypto_user fuse loop dm_mod nfnetlink bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid i915 i2c_algo_bit drm_buddy mxm_wmi ttm intel_gtt crc32c_intel nvme drm_display_helper nvme_core xhci_pci nvme_common cec sr_mod xhci_pci_renesas cdrom video wmi
Sep 09 04:37:32 reyyanarch kernel: CPU: 3 PID: 4324 Comm: nvidia-sleep.sh Tainted: P          IOE      6.6.49-1-lts #1 219753d0980ba446fc22332bc8c42ed6852afe6e
Sep 09 04:37:32 reyyanarch kernel: Hardware name: System manufacturer System Product Name/H170 PRO GAMING, BIOS 0224 07/17/2015
Sep 09 04:37:32 reyyanarch kernel: RIP: 0010:nv_restore_user_channels+0x4e/0x1d0 [nvidia]
Sep 09 04:37:32 reyyanarch kernel: Code: 24 d0 05 00 00 4c 89 ef e8 bf d3 fb e6 f6 43 10 01 74 73 48 89 de 31 ff e8 1f a4 bc 00 41 89 c6 85 c0 0f 84 3a 01 00 00 31 ed <0f> 0b 49 81 c4 f8 06 00 00 4c 89 e7 e8 91 d3 fb e6 be 01 00 00 00
Sep 09 04:37:32 reyyanarch kernel: RSP: 0018:ffffc90002623d40 EFLAGS: 00010206
Sep 09 04:37:32 reyyanarch kernel: RAX: 0000000000000003 RBX: ffff888119c54000 RCX: ffffc90002623cc0
Sep 09 04:37:32 reyyanarch kernel: RDX: ffffc9000272fe40 RSI: 0000000000000246 RDI: ffffc90002623c70
Sep 09 04:37:32 reyyanarch kernel: RBP: ffff8881dbdf0000 R08: 0000000000000000 R09: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: R10: 00000000000390c0 R11: 0000000000000001 R12: ffff888119c54000
Sep 09 04:37:32 reyyanarch kernel: R13: ffff888119c545d0 R14: 0000000000000003 R15: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: FS:  000070410e61cb80(0000) GS:ffff88846ed80000(0000) knlGS:0000000000000000
Sep 09 04:37:32 reyyanarch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 09 04:37:32 reyyanarch kernel: CR2: 000063c37c5305f8 CR3: 0000000104e52001 CR4: 00000000003706e0
Sep 09 04:37:32 reyyanarch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 09 04:37:32 reyyanarch kernel: Call Trace:
Sep 09 04:37:32 reyyanarch kernel:  <TASK>
Sep 09 04:37:32 reyyanarch kernel:  ? nv_restore_user_channels+0x4e/0x1d0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  ? __warn+0x81/0x140
Sep 09 04:37:32 reyyanarch kernel:  ? nv_restore_user_channels+0x4e/0x1d0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  ? report_bug+0x16f/0x1a0
Sep 09 04:37:32 reyyanarch kernel:  ? handle_bug+0x3c/0x80
Sep 09 04:37:32 reyyanarch kernel:  ? exc_invalid_op+0x17/0x70
Sep 09 04:37:32 reyyanarch kernel:  ? asm_exc_invalid_op+0x1a/0x20
Sep 09 04:37:32 reyyanarch kernel:  ? nv_restore_user_channels+0x4e/0x1d0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  nv_set_system_power_state+0xe9/0x470 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  nv_procfs_write_suspend+0xef/0x170 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  proc_reg_write+0x5d/0xa0
Sep 09 04:37:32 reyyanarch kernel:  vfs_write+0xf2/0x410
Sep 09 04:37:32 reyyanarch kernel:  ksys_write+0x6d/0xf0
Sep 09 04:37:32 reyyanarch kernel:  do_syscall_64+0x5a/0x80
Sep 09 04:37:32 reyyanarch kernel:  ? do_dup2+0x91/0xe0
Sep 09 04:37:32 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:32 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:32 reyyanarch kernel:  ? exc_page_fault+0x7f/0x180
Sep 09 04:37:32 reyyanarch kernel:  entry_SYSCALL_64_after_hwframe+0x78/0xe2
Sep 09 04:37:32 reyyanarch kernel: RIP: 0033:0x70410e7997a4
Sep 09 04:37:32 reyyanarch kernel: Code: c7 00 16 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 80 3d c5 28 0e 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 55 48 89 e5 48 83 ec 20 48 89
Sep 09 04:37:32 reyyanarch kernel: RSP: 002b:00007fffb1008178 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Sep 09 04:37:32 reyyanarch kernel: RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 000070410e7997a4
Sep 09 04:37:32 reyyanarch kernel: RDX: 0000000000000007 RSI: 000063c388a87830 RDI: 0000000000000001
Sep 09 04:37:32 reyyanarch kernel: RBP: 00007fffb10081a0 R08: 0000000000000410 R09: 0000000000000001
Sep 09 04:37:32 reyyanarch kernel: R10: 0000000000000004 R11: 0000000000000202 R12: 0000000000000007
Sep 09 04:37:32 reyyanarch kernel: R13: 000063c388a87830 R14: 000070410e8755c0 R15: 000070410e872ea0
Sep 09 04:37:32 reyyanarch kernel:  </TASK>
Sep 09 04:37:32 reyyanarch kernel: ---[ end trace 0000000000000000 ]---
Sep 09 04:37:32 reyyanarch kernel: ------------[ cut here ]------------
Sep 09 04:37:32 reyyanarch kernel: WARNING: CPU: 3 PID: 4324 at /build/nvidia-lts/src/nvidia/560.35.03/build/nvidia/nv.c:4540 nv_set_system_power_state+0x2d7/0x470 [nvidia]
Sep 09 04:37:32 reyyanarch kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device intel_rapl_msr intel_rapl_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_soc_avs snd_soc_hda_codec snd_hda_ext_core irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 psmouse sha256_ssse3 vfat sha1_ssse3 fat serio_raw aesni_intel atkbd libps2 crypto_simd eeepc_wmi snd_soc_core snd_hda_codec_realtek iTCO_wdt asus_wmi vivaldi_fmap intel_pmc_bxt sparse_keymap cryptd snd_hda_codec_generic platform_profile mei_pxp mei_hdcp ee1004 iTCO_vendor_support ledtrig_audio snd_compress ac97_bus snd_pcm_dmaengine rapl snd_hda_codec_hdmi nvidia_drm(POE) i8042 mei_me snd_hda_intel uinput intel_cstate nvidia_modeset(POE) snd_intel_dspcfg i2c_i801 serio snd_intel_sdw_acpi intel_uncore rfkill wmi_bmof pcspkr e1000e i2c_smbus snd_hda_codec mei nvidia_uvm(POE) snd_hda_core cdc_acm snd_hwdep acpi_pad mousedev joydev mac_hid nvidia(POE) snd_aloop snd_pcm
Sep 09 04:37:32 reyyanarch kernel:  snd_timer snd soundcore i2c_dev crypto_user fuse loop dm_mod nfnetlink bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid i915 i2c_algo_bit drm_buddy mxm_wmi ttm intel_gtt crc32c_intel nvme drm_display_helper nvme_core xhci_pci nvme_common cec sr_mod xhci_pci_renesas cdrom video wmi
Sep 09 04:37:32 reyyanarch kernel: CPU: 3 PID: 4324 Comm: nvidia-sleep.sh Tainted: P        W IOE      6.6.49-1-lts #1 219753d0980ba446fc22332bc8c42ed6852afe6e
Sep 09 04:37:32 reyyanarch kernel: Hardware name: System manufacturer System Product Name/H170 PRO GAMING, BIOS 0224 07/17/2015
Sep 09 04:37:32 reyyanarch kernel: RIP: 0010:nv_set_system_power_state+0x2d7/0x470 [nvidia]
Sep 09 04:37:32 reyyanarch kernel: Code: 02 00 00 00 48 8b 70 78 48 8b 78 60 e8 82 cb ff ff 85 c0 0f 85 dd 00 00 00 48 8b ad f8 05 00 00 48 85 ed 75 d3 e9 d9 fd ff ff <0f> 0b e9 13 fe ff ff 48 8b 3d 43 b1 db 00 4c 89 f6 e8 c3 14 59 e6
Sep 09 04:37:32 reyyanarch kernel: RSP: 0018:ffffc90002623d70 EFLAGS: 00010206
Sep 09 04:37:32 reyyanarch kernel: RAX: 0000000000000003 RBX: 0000000000000002 RCX: 0000000000e65a03
Sep 09 04:37:32 reyyanarch kernel: RDX: 0000000000e65803 RSI: ffff8881dbdf3000 RDI: 0000000000e65803
Sep 09 04:37:32 reyyanarch kernel: RBP: ffff888119c54000 R08: 0000000000000000 R09: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: R10: 0000607b91016210 R11: 0000000000000001 R12: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: R13: ffff888117cf5c00 R14: ffffc90002623e98 R15: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: FS:  000070410e61cb80(0000) GS:ffff88846ed80000(0000) knlGS:0000000000000000
Sep 09 04:37:32 reyyanarch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 09 04:37:32 reyyanarch kernel: CR2: 000063c37c5305f8 CR3: 0000000104e52001 CR4: 00000000003706e0
Sep 09 04:37:32 reyyanarch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 09 04:37:32 reyyanarch kernel: Call Trace:
Sep 09 04:37:32 reyyanarch kernel:  <TASK>
Sep 09 04:37:32 reyyanarch kernel:  ? nv_set_system_power_state+0x2d7/0x470 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  ? __warn+0x81/0x140
Sep 09 04:37:32 reyyanarch kernel:  ? nv_set_system_power_state+0x2d7/0x470 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  ? report_bug+0x16f/0x1a0
Sep 09 04:37:32 reyyanarch kernel:  ? handle_bug+0x3c/0x80
Sep 09 04:37:32 reyyanarch kernel:  ? exc_invalid_op+0x17/0x70
Sep 09 04:37:32 reyyanarch kernel:  ? asm_exc_invalid_op+0x1a/0x20
Sep 09 04:37:32 reyyanarch kernel:  ? nv_set_system_power_state+0x2d7/0x470 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  nv_procfs_write_suspend+0xef/0x170 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  proc_reg_write+0x5d/0xa0
Sep 09 04:37:32 reyyanarch kernel:  vfs_write+0xf2/0x410
Sep 09 04:37:32 reyyanarch kernel:  ksys_write+0x6d/0xf0
Sep 09 04:37:32 reyyanarch kernel:  do_syscall_64+0x5a/0x80
Sep 09 04:37:32 reyyanarch kernel:  ? do_dup2+0x91/0xe0
Sep 09 04:37:32 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:32 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:32 reyyanarch kernel:  ? exc_page_fault+0x7f/0x180
Sep 09 04:37:32 reyyanarch kernel:  entry_SYSCALL_64_after_hwframe+0x78/0xe2
Sep 09 04:37:32 reyyanarch kernel: RIP: 0033:0x70410e7997a4
Sep 09 04:37:32 reyyanarch kernel: Code: c7 00 16 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 80 3d c5 28 0e 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 55 48 89 e5 48 83 ec 20 48 89
Sep 09 04:37:32 reyyanarch kernel: RSP: 002b:00007fffb1008178 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Sep 09 04:37:32 reyyanarch kernel: RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 000070410e7997a4
Sep 09 04:37:32 reyyanarch kernel: RDX: 0000000000000007 RSI: 000063c388a87830 RDI: 0000000000000001
Sep 09 04:37:32 reyyanarch kernel: RBP: 00007fffb10081a0 R08: 0000000000000410 R09: 0000000000000001
Sep 09 04:37:32 reyyanarch kernel: R10: 0000000000000004 R11: 0000000000000202 R12: 0000000000000007
Sep 09 04:37:32 reyyanarch kernel: R13: 000063c388a87830 R14: 000070410e8755c0 R15: 000070410e872ea0
Sep 09 04:37:32 reyyanarch kernel:  </TASK>
Sep 09 04:37:32 reyyanarch kernel: ---[ end trace 0000000000000000 ]---
Sep 09 04:37:32 reyyanarch kernel: 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])
Sep 09 04:37:32 reyyanarch kernel: nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer
Sep 09 04:37:32 reyyanarch kernel: 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])
Sep 09 04:37:32 reyyanarch kernel: nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer
Sep 09 04:37:33 reyyanarch systemd[1]: systemd-suspend.service: Deactivated successfully.
Sep 09 04:37:33 reyyanarch wireplumber[941]: spa.bluez5: BlueZ system service is not available
Sep 09 04:37:33 reyyanarch kernel: BUG: unable to handle page fault for address: ffffc90006f8ec04
Sep 09 04:37:33 reyyanarch kernel: #PF: supervisor read access in kernel mode
Sep 09 04:37:33 reyyanarch kernel: #PF: error_code(0x0000) - not-present page
Sep 09 04:37:33 reyyanarch kernel: PGD 100000067 P4D 100000067 PUD 1001fa067 PMD 0 
Sep 09 04:37:33 reyyanarch kernel: Oops: 0000 [#1] PREEMPT SMP PTI
Sep 09 04:37:33 reyyanarch kernel: CPU: 3 PID: 753 Comm: Xorg Tainted: P        W IOE      6.6.49-1-lts #1 219753d0980ba446fc22332bc8c42ed6852afe6e
Sep 09 04:37:33 reyyanarch kernel: Hardware name: System manufacturer System Product Name/H170 PRO GAMING, BIOS 0224 07/17/2015
Sep 09 04:37:33 reyyanarch kernel: RIP: 0010:_nv012662rm+0xbd/0x130 [nvidia]
Sep 09 04:37:33 reyyanarch kernel: Code: 8b 45 20 41 bf 01 00 00 00 41 89 54 24 20 41 89 44 24 24 4c 89 e6 4c 89 ef e8 bf 2f 6b 00 49 89 c4 48 85 c0 74 5f 49 8b 0c 24 <8b> 41 04 0f ae e8 41 39 44 24 20 74 dc 8b 41 08 0f b7 d8 25 00 00
Sep 09 04:37:33 reyyanarch kernel: RSP: 0018:ffffc900026cf698 EFLAGS: 00010282
Sep 09 04:37:33 reyyanarch kernel: RAX: ffff888156faf298 RBX: 0000000000000001 RCX: ffffc90006f8ec00
Sep 09 04:37:33 reyyanarch kernel: RDX: fffffffffffffff0 RSI: ffff888117e19008 RDI: ffff888117e19900
Sep 09 04:37:33 reyyanarch kernel: RBP: ffff8881dbdf2940 R08: 0000000000000000 R09: 0000000000000020
Sep 09 04:37:33 reyyanarch kernel: R10: ffff8881dbdf2984 R11: ffffffffc0d4f6a0 R12: ffff888156faf298
Sep 09 04:37:33 reyyanarch kernel: R13: ffff888117e19900 R14: ffff888117e19008 R15: 0000000000000000
Sep 09 04:37:33 reyyanarch kernel: FS:  00007484b2e8e9c0(0000) GS:ffff88846ed80000(0000) knlGS:0000000000000000
Sep 09 04:37:33 reyyanarch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 09 04:37:33 reyyanarch kernel: CR2: ffffc90006f8ec04 CR3: 0000000102b98006 CR4: 00000000003706e0
Sep 09 04:37:33 reyyanarch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 09 04:37:33 reyyanarch kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 09 04:37:33 reyyanarch kernel: Call Trace:
Sep 09 04:37:33 reyyanarch kernel:  <TASK>
Sep 09 04:37:33 reyyanarch kernel:  ? __die+0x23/0x70
Sep 09 04:37:33 reyyanarch kernel:  ? page_fault_oops+0x174/0x530
Sep 09 04:37:33 reyyanarch kernel:  ? _nv012662rm+0xbd/0x130 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  ? search_module_extables+0x19/0x60
Sep 09 04:37:33 reyyanarch kernel:  ? search_bpf_extables+0x5f/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? exc_page_fault+0x175/0x180
Sep 09 04:37:33 reyyanarch kernel:  ? asm_exc_page_fault+0x26/0x30
Sep 09 04:37:33 reyyanarch kernel:  ? _nv012663rm+0x1f0/0x1f0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  ? _nv012662rm+0xbd/0x130 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  ? _nv012662rm+0x42/0x130 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv036737rm+0x19e/0x2f0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv031308rm+0x24/0xc0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv022578rm+0x295/0x3c4 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv033274rm+0x63/0xc0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv012814rm+0x276/0x3d0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv033282rm+0x11e/0x370 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv028164rm+0x8f/0xb0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv043395rm+0x2e4/0x440 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv043402rm+0x4e/0x560 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv043314rm+0x107/0x610 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv043308rm+0x192/0x1c0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv021485rm+0x1bf/0x310 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv023350rm+0xc0/0xe6 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv047909rm+0x1a1/0x1b0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv022972rm+0xd9/0x160 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv049933rm+0x3ff/0x500 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv014741rm+0x3f1/0x690 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv048059rm+0x69/0xd0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv013137rm+0x86/0xa0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv000598rm+0x5e/0x70 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  rm_kernel_rmapi_op+0x127/0x213 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  nvkms_call_rm+0x4d/0x80 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  _nv002849kms+0x42/0x50 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? _nv002872kms+0x69/0xe0 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? _nv002437kms+0x434/0x450 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? __check_object_size+0x1ec/0x2c0
Sep 09 04:37:33 reyyanarch kernel:  ? _nv000424kms+0x80/0x80 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? nvKmsIoctl+0xf9/0x270 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? nvkms_unlocked_ioctl+0x110/0x180 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? __x64_sys_ioctl+0x97/0xd0
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x5a/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? _nv000722kms+0xb0/0xb0 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? nvKmsIoctl+0x169/0x270 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? _nv000722kms+0xb0/0xb0 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? up+0x16/0x60
Sep 09 04:37:33 reyyanarch kernel:  ? nvkms_unlocked_ioctl+0x130/0x180 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? __x64_sys_ioctl+0xaf/0xd0
Sep 09 04:37:33 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? up+0x16/0x60
Sep 09 04:37:33 reyyanarch kernel:  ? nvkms_unlocked_ioctl+0x130/0x180 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? __x64_sys_ioctl+0xaf/0xd0
Sep 09 04:37:33 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? nvKmsIoctl+0x169/0x270 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? up+0x16/0x60
Sep 09 04:37:33 reyyanarch kernel:  ? nvkms_unlocked_ioctl+0x130/0x180 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? __x64_sys_ioctl+0xaf/0xd0
Sep 09 04:37:33 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? exc_page_fault+0x7f/0x180
Sep 09 04:37:33 reyyanarch kernel:  ? entry_SYSCALL_64_after_hwframe+0x78/0xe2
Sep 09 04:37:33 reyyanarch kernel:  </TASK>
Sep 09 04:37:33 reyyanarch kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device intel_rapl_msr intel_rapl_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_soc_avs snd_soc_hda_codec snd_hda_ext_core irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 psmouse sha256_ssse3 vfat sha1_ssse3 fat serio_raw aesni_intel atkbd libps2 crypto_simd eeepc_wmi snd_soc_core snd_hda_codec_realtek iTCO_wdt asus_wmi vivaldi_fmap intel_pmc_bxt sparse_keymap cryptd snd_hda_codec_generic platform_profile mei_pxp mei_hdcp ee1004 iTCO_vendor_support ledtrig_audio snd_compress ac97_bus snd_pcm_dmaengine rapl snd_hda_codec_hdmi nvidia_drm(POE) i8042 mei_me snd_hda_intel uinput intel_cstate nvidia_modeset(POE) snd_intel_dspcfg i2c_i801 serio snd_intel_sdw_acpi intel_uncore rfkill wmi_bmof pcspkr e1000e i2c_smbus snd_hda_codec mei nvidia_uvm(POE) snd_hda_core cdc_acm snd_hwdep acpi_pad mousedev joydev mac_hid nvidia(POE) snd_aloop snd_pcm
Sep 09 04:37:33 reyyanarch kernel:  snd_timer snd soundcore i2c_dev crypto_user fuse loop dm_mod nfnetlink bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid i915 i2c_algo_bit drm_buddy mxm_wmi ttm intel_gtt crc32c_intel nvme drm_display_helper nvme_core xhci_pci nvme_common cec sr_mod xhci_pci_renesas cdrom video wmi
Sep 09 04:37:33 reyyanarch kernel: CR2: ffffc90006f8ec04
Sep 09 04:37:33 reyyanarch kernel: ---[ end trace 0000000000000000 ]---
Sep 09 04:37:33 reyyanarch kernel: RIP: 0010:_nv012662rm+0xbd/0x130 [nvidia]
Sep 09 04:37:33 reyyanarch kernel: Code: 8b 45 20 41 bf 01 00 00 00 41 89 54 24 20 41 89 44 24 24 4c 89 e6 4c 89 ef e8 bf 2f 6b 00 49 89 c4 48 85 c0 74 5f 49 8b 0c 24 <8b> 41 04 0f ae e8 41 39 44 24 20 74 dc 8b 41 08 0f b7 d8 25 00 00
Sep 09 04:37:33 reyyanarch kernel: RSP: 0018:ffffc900026cf698 EFLAGS: 00010282
Sep 09 04:37:33 reyyanarch kernel: RAX: ffff888156faf298 RBX: 0000000000000001 RCX: ffffc90006f8ec00
Sep 09 04:37:33 reyyanarch kernel: RDX: fffffffffffffff0 RSI: ffff888117e19008 RDI: ffff888117e19900
Sep 09 04:37:33 reyyanarch kernel: RBP: ffff8881dbdf2940 R08: 0000000000000000 R09: 0000000000000020
Sep 09 04:37:33 reyyanarch kernel: R10: ffff8881dbdf2984 R11: ffffffffc0d4f6a0 R12: ffff888156faf298
Sep 09 04:37:33 reyyanarch kernel: R13: ffff888117e19900 R14: ffff888117e19008 R15: 0000000000000000
Sep 09 04:37:33 reyyanarch kernel: FS:  00007484b2e8e9c0(0000) GS:ffff88846ed80000(0000) knlGS:0000000000000000
Sep 09 04:37:33 reyyanarch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 09 04:37:33 reyyanarch kernel: CR2: ffffc90006f8ec04 CR3: 0000000102b98006 CR4: 00000000003706e0
Sep 09 04:37:33 reyyanarch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 09 04:37:33 reyyanarch kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 09 04:37:33 reyyanarch kernel: note: Xorg[753] exited with irqs disabled

Sep 09 04:27:48 reyyanarch systemd-udevd[329]: libkmod: kmod_config_parse: /etc/modprobe.d/nvidiafb.conf line 4: ignoring bad line starting with 'NVreg_PreserveVideoMemoryAllocations=1'
Sep 09 04:27:48 reyyanarch modprobe[356]: libkmod: kmod_config_parse: /etc/modprobe.d/nvidiafb.conf line 4: ignoring bad line starting with 'NVreg_PreserveVideoMemoryAllocations=1'
Sep 09 04:27:48 reyyanarch modprobe[359]: libkmod: kmod_config_parse: /etc/modprobe.d/nvidiafb.conf line 4: ignoring bad line starting with 'NVreg_PreserveVideoMemoryAllocations=1'

Sep 09 04:37:10 reyyanarch suspend[4249]: nvidia-suspend.service
Sep 09 04:37:10 reyyanarch logger[4249]: <13>Sep  9 04:37:10 suspend: nvidia-suspend.service
Sep 09 04:37:10 reyyanarch systemd[1]: nvidia-suspend.service: Deactivated successfully.
Sep 09 04:37:33 reyyanarch suspend[4359]: nvidia-resume.service
Sep 09 04:37:33 reyyanarch logger[4359]: <13>Sep  9 04:37:33 suspend: nvidia-resume.service
Sep 09 04:37:33 reyyanarch systemd[1]: nvidia-resume.service: Deactivated successfully.

Sep 09 04:37:32 reyyanarch kernel: WARNING: CPU: 3 PID: 4324 at /build/nvidia-lts/src/nvidia/560.35.03/build/nvidia/nv.c:4310 nv_restore_user_channels+0x4e/0x1d0 [nvidia]
Sep 09 04:37:32 reyyanarch kernel: CPU: 3 PID: 4324 Comm: nvidia-sleep.sh Tainted: P          IOE      6.6.49-1-lts #1 219753d0980ba446fc22332bc8c42ed6852afe6e
Sep 09 04:37:32 reyyanarch kernel: WARNING: CPU: 3 PID: 4324 at /build/nvidia-lts/src/nvidia/560.35.03/build/nvidia/nv.c:4540 nv_set_system_power_state+0x2d7/0x470 [nvidia]
Sep 09 04:37:32 reyyanarch kernel: CPU: 3 PID: 4324 Comm: nvidia-sleep.sh Tainted: P        W IOE      6.6.49-1-lts #1 219753d0980ba446fc22332bc8c42ed6852afe6e
Sep 09 04:37:33 reyyanarch kernel: CPU: 3 PID: 753 Comm: Xorg Tainted: P        W IOE      6.6.49-1-lts #1 219753d0980ba446fc22332bc8c42ed6852afe6e

Your configuration for the memory preservation seems broken, post /etc/modprobe.d/nvidiafb.conf

In doubt also try https://aur.archlinux.org/packages/nvidia-535xx-dkms - https://bbs.archlinux.org/viewtopic.php?id=298941

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Reyyanfr

Member

Registered: 2024-08-15

Posts: 22

Re: Sleep and hibernation not working ([SOLVED] HDD IO led always on)

Sep 09 04:37:32 reyyanarch kernel: ------------[ cut here ]------------
Sep 09 04:37:32 reyyanarch kernel: WARNING: CPU: 3 PID: 4324 at /build/nvidia-lts/src/nvidia/560.35.03/build/nvidia/nv.c:4310 nv_restore_user_channels+0x4e/0x1d0 [nvidia]
Sep 09 04:37:32 reyyanarch kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device intel_rapl_msr intel_rapl_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_soc_avs snd_soc_hda_codec snd_hda_ext_core irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 psmouse sha256_ssse3 vfat sha1_ssse3 fat serio_raw aesni_intel atkbd libps2 crypto_simd eeepc_wmi snd_soc_core snd_hda_codec_realtek iTCO_wdt asus_wmi vivaldi_fmap intel_pmc_bxt sparse_keymap cryptd snd_hda_codec_generic platform_profile mei_pxp mei_hdcp ee1004 iTCO_vendor_support ledtrig_audio snd_compress ac97_bus snd_pcm_dmaengine rapl snd_hda_codec_hdmi nvidia_drm(POE) i8042 mei_me snd_hda_intel uinput intel_cstate nvidia_modeset(POE) snd_intel_dspcfg i2c_i801 serio snd_intel_sdw_acpi intel_uncore rfkill wmi_bmof pcspkr e1000e i2c_smbus snd_hda_codec mei nvidia_uvm(POE) snd_hda_core cdc_acm snd_hwdep acpi_pad mousedev joydev mac_hid nvidia(POE) snd_aloop snd_pcm
Sep 09 04:37:32 reyyanarch kernel:  snd_timer snd soundcore i2c_dev crypto_user fuse loop dm_mod nfnetlink bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid i915 i2c_algo_bit drm_buddy mxm_wmi ttm intel_gtt crc32c_intel nvme drm_display_helper nvme_core xhci_pci nvme_common cec sr_mod xhci_pci_renesas cdrom video wmi
Sep 09 04:37:32 reyyanarch kernel: CPU: 3 PID: 4324 Comm: nvidia-sleep.sh Tainted: P          IOE      6.6.49-1-lts #1 219753d0980ba446fc22332bc8c42ed6852afe6e
Sep 09 04:37:32 reyyanarch kernel: Hardware name: System manufacturer System Product Name/H170 PRO GAMING, BIOS 0224 07/17/2015
Sep 09 04:37:32 reyyanarch kernel: RIP: 0010:nv_restore_user_channels+0x4e/0x1d0 [nvidia]
Sep 09 04:37:32 reyyanarch kernel: Code: 24 d0 05 00 00 4c 89 ef e8 bf d3 fb e6 f6 43 10 01 74 73 48 89 de 31 ff e8 1f a4 bc 00 41 89 c6 85 c0 0f 84 3a 01 00 00 31 ed <0f> 0b 49 81 c4 f8 06 00 00 4c 89 e7 e8 91 d3 fb e6 be 01 00 00 00
Sep 09 04:37:32 reyyanarch kernel: RSP: 0018:ffffc90002623d40 EFLAGS: 00010206
Sep 09 04:37:32 reyyanarch kernel: RAX: 0000000000000003 RBX: ffff888119c54000 RCX: ffffc90002623cc0
Sep 09 04:37:32 reyyanarch kernel: RDX: ffffc9000272fe40 RSI: 0000000000000246 RDI: ffffc90002623c70
Sep 09 04:37:32 reyyanarch kernel: RBP: ffff8881dbdf0000 R08: 0000000000000000 R09: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: R10: 00000000000390c0 R11: 0000000000000001 R12: ffff888119c54000
Sep 09 04:37:32 reyyanarch kernel: R13: ffff888119c545d0 R14: 0000000000000003 R15: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: FS:  000070410e61cb80(0000) GS:ffff88846ed80000(0000) knlGS:0000000000000000
Sep 09 04:37:32 reyyanarch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 09 04:37:32 reyyanarch kernel: CR2: 000063c37c5305f8 CR3: 0000000104e52001 CR4: 00000000003706e0
Sep 09 04:37:32 reyyanarch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 09 04:37:32 reyyanarch kernel: Call Trace:
Sep 09 04:37:32 reyyanarch kernel:  <TASK>
Sep 09 04:37:32 reyyanarch kernel:  ? nv_restore_user_channels+0x4e/0x1d0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  ? __warn+0x81/0x140
Sep 09 04:37:32 reyyanarch kernel:  ? nv_restore_user_channels+0x4e/0x1d0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  ? report_bug+0x16f/0x1a0
Sep 09 04:37:32 reyyanarch kernel:  ? handle_bug+0x3c/0x80
Sep 09 04:37:32 reyyanarch kernel:  ? exc_invalid_op+0x17/0x70
Sep 09 04:37:32 reyyanarch kernel:  ? asm_exc_invalid_op+0x1a/0x20
Sep 09 04:37:32 reyyanarch kernel:  ? nv_restore_user_channels+0x4e/0x1d0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  nv_set_system_power_state+0xe9/0x470 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  nv_procfs_write_suspend+0xef/0x170 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  proc_reg_write+0x5d/0xa0
Sep 09 04:37:32 reyyanarch kernel:  vfs_write+0xf2/0x410
Sep 09 04:37:32 reyyanarch kernel:  ksys_write+0x6d/0xf0
Sep 09 04:37:32 reyyanarch kernel:  do_syscall_64+0x5a/0x80
Sep 09 04:37:32 reyyanarch kernel:  ? do_dup2+0x91/0xe0
Sep 09 04:37:32 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:32 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:32 reyyanarch kernel:  ? exc_page_fault+0x7f/0x180
Sep 09 04:37:32 reyyanarch kernel:  entry_SYSCALL_64_after_hwframe+0x78/0xe2
Sep 09 04:37:32 reyyanarch kernel: RIP: 0033:0x70410e7997a4
Sep 09 04:37:32 reyyanarch kernel: Code: c7 00 16 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 80 3d c5 28 0e 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 55 48 89 e5 48 83 ec 20 48 89
Sep 09 04:37:32 reyyanarch kernel: RSP: 002b:00007fffb1008178 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Sep 09 04:37:32 reyyanarch kernel: RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 000070410e7997a4
Sep 09 04:37:32 reyyanarch kernel: RDX: 0000000000000007 RSI: 000063c388a87830 RDI: 0000000000000001
Sep 09 04:37:32 reyyanarch kernel: RBP: 00007fffb10081a0 R08: 0000000000000410 R09: 0000000000000001
Sep 09 04:37:32 reyyanarch kernel: R10: 0000000000000004 R11: 0000000000000202 R12: 0000000000000007
Sep 09 04:37:32 reyyanarch kernel: R13: 000063c388a87830 R14: 000070410e8755c0 R15: 000070410e872ea0
Sep 09 04:37:32 reyyanarch kernel:  </TASK>
Sep 09 04:37:32 reyyanarch kernel: ---[ end trace 0000000000000000 ]---
Sep 09 04:37:32 reyyanarch kernel: ------------[ cut here ]------------
Sep 09 04:37:32 reyyanarch kernel: WARNING: CPU: 3 PID: 4324 at /build/nvidia-lts/src/nvidia/560.35.03/build/nvidia/nv.c:4540 nv_set_system_power_state+0x2d7/0x470 [nvidia]
Sep 09 04:37:32 reyyanarch kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device intel_rapl_msr intel_rapl_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_soc_avs snd_soc_hda_codec snd_hda_ext_core irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 psmouse sha256_ssse3 vfat sha1_ssse3 fat serio_raw aesni_intel atkbd libps2 crypto_simd eeepc_wmi snd_soc_core snd_hda_codec_realtek iTCO_wdt asus_wmi vivaldi_fmap intel_pmc_bxt sparse_keymap cryptd snd_hda_codec_generic platform_profile mei_pxp mei_hdcp ee1004 iTCO_vendor_support ledtrig_audio snd_compress ac97_bus snd_pcm_dmaengine rapl snd_hda_codec_hdmi nvidia_drm(POE) i8042 mei_me snd_hda_intel uinput intel_cstate nvidia_modeset(POE) snd_intel_dspcfg i2c_i801 serio snd_intel_sdw_acpi intel_uncore rfkill wmi_bmof pcspkr e1000e i2c_smbus snd_hda_codec mei nvidia_uvm(POE) snd_hda_core cdc_acm snd_hwdep acpi_pad mousedev joydev mac_hid nvidia(POE) snd_aloop snd_pcm
Sep 09 04:37:32 reyyanarch kernel:  snd_timer snd soundcore i2c_dev crypto_user fuse loop dm_mod nfnetlink bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid i915 i2c_algo_bit drm_buddy mxm_wmi ttm intel_gtt crc32c_intel nvme drm_display_helper nvme_core xhci_pci nvme_common cec sr_mod xhci_pci_renesas cdrom video wmi
Sep 09 04:37:32 reyyanarch kernel: CPU: 3 PID: 4324 Comm: nvidia-sleep.sh Tainted: P        W IOE      6.6.49-1-lts #1 219753d0980ba446fc22332bc8c42ed6852afe6e
Sep 09 04:37:32 reyyanarch kernel: Hardware name: System manufacturer System Product Name/H170 PRO GAMING, BIOS 0224 07/17/2015
Sep 09 04:37:32 reyyanarch kernel: RIP: 0010:nv_set_system_power_state+0x2d7/0x470 [nvidia]
Sep 09 04:37:32 reyyanarch kernel: Code: 02 00 00 00 48 8b 70 78 48 8b 78 60 e8 82 cb ff ff 85 c0 0f 85 dd 00 00 00 48 8b ad f8 05 00 00 48 85 ed 75 d3 e9 d9 fd ff ff <0f> 0b e9 13 fe ff ff 48 8b 3d 43 b1 db 00 4c 89 f6 e8 c3 14 59 e6
Sep 09 04:37:32 reyyanarch kernel: RSP: 0018:ffffc90002623d70 EFLAGS: 00010206
Sep 09 04:37:32 reyyanarch kernel: RAX: 0000000000000003 RBX: 0000000000000002 RCX: 0000000000e65a03
Sep 09 04:37:32 reyyanarch kernel: RDX: 0000000000e65803 RSI: ffff8881dbdf3000 RDI: 0000000000e65803
Sep 09 04:37:32 reyyanarch kernel: RBP: ffff888119c54000 R08: 0000000000000000 R09: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: R10: 0000607b91016210 R11: 0000000000000001 R12: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: R13: ffff888117cf5c00 R14: ffffc90002623e98 R15: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: FS:  000070410e61cb80(0000) GS:ffff88846ed80000(0000) knlGS:0000000000000000
Sep 09 04:37:32 reyyanarch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 09 04:37:32 reyyanarch kernel: CR2: 000063c37c5305f8 CR3: 0000000104e52001 CR4: 00000000003706e0
Sep 09 04:37:32 reyyanarch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 09 04:37:32 reyyanarch kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 09 04:37:32 reyyanarch kernel: Call Trace:
Sep 09 04:37:32 reyyanarch kernel:  <TASK>
Sep 09 04:37:32 reyyanarch kernel:  ? nv_set_system_power_state+0x2d7/0x470 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  ? __warn+0x81/0x140
Sep 09 04:37:32 reyyanarch kernel:  ? nv_set_system_power_state+0x2d7/0x470 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  ? report_bug+0x16f/0x1a0
Sep 09 04:37:32 reyyanarch kernel:  ? handle_bug+0x3c/0x80
Sep 09 04:37:32 reyyanarch kernel:  ? exc_invalid_op+0x17/0x70
Sep 09 04:37:32 reyyanarch kernel:  ? asm_exc_invalid_op+0x1a/0x20
Sep 09 04:37:32 reyyanarch kernel:  ? nv_set_system_power_state+0x2d7/0x470 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  nv_procfs_write_suspend+0xef/0x170 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:32 reyyanarch kernel:  proc_reg_write+0x5d/0xa0
Sep 09 04:37:32 reyyanarch kernel:  vfs_write+0xf2/0x410
Sep 09 04:37:32 reyyanarch kernel:  ksys_write+0x6d/0xf0
Sep 09 04:37:32 reyyanarch kernel:  do_syscall_64+0x5a/0x80
Sep 09 04:37:32 reyyanarch kernel:  ? do_dup2+0x91/0xe0
Sep 09 04:37:32 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:32 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:32 reyyanarch kernel:  ? exc_page_fault+0x7f/0x180
Sep 09 04:37:32 reyyanarch kernel:  entry_SYSCALL_64_after_hwframe+0x78/0xe2
Sep 09 04:37:32 reyyanarch kernel: RIP: 0033:0x70410e7997a4
Sep 09 04:37:32 reyyanarch kernel: Code: c7 00 16 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 80 3d c5 28 0e 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 55 48 89 e5 48 83 ec 20 48 89
Sep 09 04:37:32 reyyanarch kernel: RSP: 002b:00007fffb1008178 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Sep 09 04:37:32 reyyanarch kernel: RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 000070410e7997a4
Sep 09 04:37:32 reyyanarch kernel: RDX: 0000000000000007 RSI: 000063c388a87830 RDI: 0000000000000001
Sep 09 04:37:32 reyyanarch kernel: RBP: 00007fffb10081a0 R08: 0000000000000410 R09: 0000000000000001
Sep 09 04:37:32 reyyanarch kernel: R10: 0000000000000004 R11: 0000000000000202 R12: 0000000000000007
Sep 09 04:37:32 reyyanarch kernel: R13: 000063c388a87830 R14: 000070410e8755c0 R15: 000070410e872ea0
Sep 09 04:37:32 reyyanarch kernel:  </TASK>
Sep 09 04:37:32 reyyanarch kernel: ---[ end trace 0000000000000000 ]---
Sep 09 04:37:32 reyyanarch kernel: 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])
Sep 09 04:37:32 reyyanarch kernel: nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer
Sep 09 04:37:32 reyyanarch kernel: 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])
Sep 09 04:37:32 reyyanarch kernel: nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer
Sep 09 04:37:33 reyyanarch systemd[1]: systemd-suspend.service: Deactivated successfully.
Sep 09 04:37:33 reyyanarch wireplumber[941]: spa.bluez5: BlueZ system service is not available
Sep 09 04:37:33 reyyanarch kernel: BUG: unable to handle page fault for address: ffffc90006f8ec04
Sep 09 04:37:33 reyyanarch kernel: #PF: supervisor read access in kernel mode
Sep 09 04:37:33 reyyanarch kernel: #PF: error_code(0x0000) - not-present page
Sep 09 04:37:33 reyyanarch kernel: PGD 100000067 P4D 100000067 PUD 1001fa067 PMD 0 
Sep 09 04:37:33 reyyanarch kernel: Oops: 0000 [#1] PREEMPT SMP PTI
Sep 09 04:37:33 reyyanarch kernel: CPU: 3 PID: 753 Comm: Xorg Tainted: P        W IOE      6.6.49-1-lts #1 219753d0980ba446fc22332bc8c42ed6852afe6e
Sep 09 04:37:33 reyyanarch kernel: Hardware name: System manufacturer System Product Name/H170 PRO GAMING, BIOS 0224 07/17/2015
Sep 09 04:37:33 reyyanarch kernel: RIP: 0010:_nv012662rm+0xbd/0x130 [nvidia]
Sep 09 04:37:33 reyyanarch kernel: Code: 8b 45 20 41 bf 01 00 00 00 41 89 54 24 20 41 89 44 24 24 4c 89 e6 4c 89 ef e8 bf 2f 6b 00 49 89 c4 48 85 c0 74 5f 49 8b 0c 24 <8b> 41 04 0f ae e8 41 39 44 24 20 74 dc 8b 41 08 0f b7 d8 25 00 00
Sep 09 04:37:33 reyyanarch kernel: RSP: 0018:ffffc900026cf698 EFLAGS: 00010282
Sep 09 04:37:33 reyyanarch kernel: RAX: ffff888156faf298 RBX: 0000000000000001 RCX: ffffc90006f8ec00
Sep 09 04:37:33 reyyanarch kernel: RDX: fffffffffffffff0 RSI: ffff888117e19008 RDI: ffff888117e19900
Sep 09 04:37:33 reyyanarch kernel: RBP: ffff8881dbdf2940 R08: 0000000000000000 R09: 0000000000000020
Sep 09 04:37:33 reyyanarch kernel: R10: ffff8881dbdf2984 R11: ffffffffc0d4f6a0 R12: ffff888156faf298
Sep 09 04:37:33 reyyanarch kernel: R13: ffff888117e19900 R14: ffff888117e19008 R15: 0000000000000000
Sep 09 04:37:33 reyyanarch kernel: FS:  00007484b2e8e9c0(0000) GS:ffff88846ed80000(0000) knlGS:0000000000000000
Sep 09 04:37:33 reyyanarch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 09 04:37:33 reyyanarch kernel: CR2: ffffc90006f8ec04 CR3: 0000000102b98006 CR4: 00000000003706e0
Sep 09 04:37:33 reyyanarch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 09 04:37:33 reyyanarch kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 09 04:37:33 reyyanarch kernel: Call Trace:
Sep 09 04:37:33 reyyanarch kernel:  <TASK>
Sep 09 04:37:33 reyyanarch kernel:  ? __die+0x23/0x70
Sep 09 04:37:33 reyyanarch kernel:  ? page_fault_oops+0x174/0x530
Sep 09 04:37:33 reyyanarch kernel:  ? _nv012662rm+0xbd/0x130 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  ? search_module_extables+0x19/0x60
Sep 09 04:37:33 reyyanarch kernel:  ? search_bpf_extables+0x5f/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? exc_page_fault+0x175/0x180
Sep 09 04:37:33 reyyanarch kernel:  ? asm_exc_page_fault+0x26/0x30
Sep 09 04:37:33 reyyanarch kernel:  ? _nv012663rm+0x1f0/0x1f0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  ? _nv012662rm+0xbd/0x130 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  ? _nv012662rm+0x42/0x130 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv036737rm+0x19e/0x2f0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv031308rm+0x24/0xc0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv022578rm+0x295/0x3c4 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv033274rm+0x63/0xc0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv012814rm+0x276/0x3d0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv033282rm+0x11e/0x370 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv028164rm+0x8f/0xb0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv043395rm+0x2e4/0x440 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv043402rm+0x4e/0x560 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv043314rm+0x107/0x610 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv043308rm+0x192/0x1c0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv021485rm+0x1bf/0x310 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv023350rm+0xc0/0xe6 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv047909rm+0x1a1/0x1b0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv022972rm+0xd9/0x160 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv049933rm+0x3ff/0x500 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv014741rm+0x3f1/0x690 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv048059rm+0x69/0xd0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv013137rm+0x86/0xa0 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  _nv000598rm+0x5e/0x70 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  rm_kernel_rmapi_op+0x127/0x213 [nvidia 5633931acc83ef1a49bd9b7ddeeec1ccbd06458b]
Sep 09 04:37:33 reyyanarch kernel:  nvkms_call_rm+0x4d/0x80 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  _nv002849kms+0x42/0x50 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? _nv002872kms+0x69/0xe0 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? _nv002437kms+0x434/0x450 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? __check_object_size+0x1ec/0x2c0
Sep 09 04:37:33 reyyanarch kernel:  ? _nv000424kms+0x80/0x80 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? nvKmsIoctl+0xf9/0x270 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? nvkms_unlocked_ioctl+0x110/0x180 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? __x64_sys_ioctl+0x97/0xd0
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x5a/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? _nv000722kms+0xb0/0xb0 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? nvKmsIoctl+0x169/0x270 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? _nv000722kms+0xb0/0xb0 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? up+0x16/0x60
Sep 09 04:37:33 reyyanarch kernel:  ? nvkms_unlocked_ioctl+0x130/0x180 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? __x64_sys_ioctl+0xaf/0xd0
Sep 09 04:37:33 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? up+0x16/0x60
Sep 09 04:37:33 reyyanarch kernel:  ? nvkms_unlocked_ioctl+0x130/0x180 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? __x64_sys_ioctl+0xaf/0xd0
Sep 09 04:37:33 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? nvKmsIoctl+0x169/0x270 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? up+0x16/0x60
Sep 09 04:37:33 reyyanarch kernel:  ? nvkms_unlocked_ioctl+0x130/0x180 [nvidia_modeset f060f14e9041de11867fe3717b8d2e5d7f4c28d7]
Sep 09 04:37:33 reyyanarch kernel:  ? __x64_sys_ioctl+0xaf/0xd0
Sep 09 04:37:33 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Sep 09 04:37:33 reyyanarch kernel:  ? do_syscall_64+0x66/0x80
Sep 09 04:37:33 reyyanarch kernel:  ? exc_page_fault+0x7f/0x180
Sep 09 04:37:33 reyyanarch kernel:  ? entry_SYSCALL_64_after_hwframe+0x78/0xe2
Sep 09 04:37:33 reyyanarch kernel:  </TASK>
Sep 09 04:37:33 reyyanarch kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device intel_rapl_msr intel_rapl_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_soc_avs snd_soc_hda_codec snd_hda_ext_core irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 psmouse sha256_ssse3 vfat sha1_ssse3 fat serio_raw aesni_intel atkbd libps2 crypto_simd eeepc_wmi snd_soc_core snd_hda_codec_realtek iTCO_wdt asus_wmi vivaldi_fmap intel_pmc_bxt sparse_keymap cryptd snd_hda_codec_generic platform_profile mei_pxp mei_hdcp ee1004 iTCO_vendor_support ledtrig_audio snd_compress ac97_bus snd_pcm_dmaengine rapl snd_hda_codec_hdmi nvidia_drm(POE) i8042 mei_me snd_hda_intel uinput intel_cstate nvidia_modeset(POE) snd_intel_dspcfg i2c_i801 serio snd_intel_sdw_acpi intel_uncore rfkill wmi_bmof pcspkr e1000e i2c_smbus snd_hda_codec mei nvidia_uvm(POE) snd_hda_core cdc_acm snd_hwdep acpi_pad mousedev joydev mac_hid nvidia(POE) snd_aloop snd_pcm
Sep 09 04:37:33 reyyanarch kernel:  snd_timer snd soundcore i2c_dev crypto_user fuse loop dm_mod nfnetlink bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid i915 i2c_algo_bit drm_buddy mxm_wmi ttm intel_gtt crc32c_intel nvme drm_display_helper nvme_core xhci_pci nvme_common cec sr_mod xhci_pci_renesas cdrom video wmi
Sep 09 04:37:33 reyyanarch kernel: CR2: ffffc90006f8ec04
Sep 09 04:37:33 reyyanarch kernel: ---[ end trace 0000000000000000 ]---
Sep 09 04:37:33 reyyanarch kernel: RIP: 0010:_nv012662rm+0xbd/0x130 [nvidia]
Sep 09 04:37:33 reyyanarch kernel: Code: 8b 45 20 41 bf 01 00 00 00 41 89 54 24 20 41 89 44 24 24 4c 89 e6 4c 89 ef e8 bf 2f 6b 00 49 89 c4 48 85 c0 74 5f 49 8b 0c 24 <8b> 41 04 0f ae e8 41 39 44 24 20 74 dc 8b 41 08 0f b7 d8 25 00 00
Sep 09 04:37:33 reyyanarch kernel: RSP: 0018:ffffc900026cf698 EFLAGS: 00010282
Sep 09 04:37:33 reyyanarch kernel: RAX: ffff888156faf298 RBX: 0000000000000001 RCX: ffffc90006f8ec00
Sep 09 04:37:33 reyyanarch kernel: RDX: fffffffffffffff0 RSI: ffff888117e19008 RDI: ffff888117e19900
Sep 09 04:37:33 reyyanarch kernel: RBP: ffff8881dbdf2940 R08: 0000000000000000 R09: 0000000000000020
Sep 09 04:37:33 reyyanarch kernel: R10: ffff8881dbdf2984 R11: ffffffffc0d4f6a0 R12: ffff888156faf298
Sep 09 04:37:33 reyyanarch kernel: R13: ffff888117e19900 R14: ffff888117e19008 R15: 0000000000000000
Sep 09 04:37:33 reyyanarch kernel: FS:  00007484b2e8e9c0(0000) GS:ffff88846ed80000(0000) knlGS:0000000000000000
Sep 09 04:37:33 reyyanarch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 09 04:37:33 reyyanarch kernel: CR2: ffffc90006f8ec04 CR3: 0000000102b98006 CR4: 00000000003706e0
Sep 09 04:37:33 reyyanarch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 09 04:37:33 reyyanarch kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 09 04:37:33 reyyanarch kernel: note: Xorg[753] exited with irqs disabled

Sep 09 04:27:48 reyyanarch systemd-udevd[329]: libkmod: kmod_config_parse: /etc/modprobe.d/nvidiafb.conf line 4: ignoring bad line starting with 'NVreg_PreserveVideoMemoryAllocations=1'
Sep 09 04:27:48 reyyanarch modprobe[356]: libkmod: kmod_config_parse: /etc/modprobe.d/nvidiafb.conf line 4: ignoring bad line starting with 'NVreg_PreserveVideoMemoryAllocations=1'
Sep 09 04:27:48 reyyanarch modprobe[359]: libkmod: kmod_config_parse: /etc/modprobe.d/nvidiafb.conf line 4: ignoring bad line starting with 'NVreg_PreserveVideoMemoryAllocations=1'

Sep 09 04:37:10 reyyanarch suspend[4249]: nvidia-suspend.service
Sep 09 04:37:10 reyyanarch logger[4249]: <13>Sep  9 04:37:10 suspend: nvidia-suspend.service
Sep 09 04:37:10 reyyanarch systemd[1]: nvidia-suspend.service: Deactivated successfully.
Sep 09 04:37:33 reyyanarch suspend[4359]: nvidia-resume.service
Sep 09 04:37:33 reyyanarch logger[4359]: <13>Sep  9 04:37:33 suspend: nvidia-resume.service
Sep 09 04:37:33 reyyanarch systemd[1]: nvidia-resume.service: Deactivated successfully.

Sep 09 04:37:32 reyyanarch kernel: WARNING: CPU: 3 PID: 4324 at /build/nvidia-lts/src/nvidia/560.35.03/build/nvidia/nv.c:4310 nv_restore_user_channels+0x4e/0x1d0 [nvidia]
Sep 09 04:37:32 reyyanarch kernel: CPU: 3 PID: 4324 Comm: nvidia-sleep.sh Tainted: P          IOE      6.6.49-1-lts #1 219753d0980ba446fc22332bc8c42ed6852afe6e
Sep 09 04:37:32 reyyanarch kernel: WARNING: CPU: 3 PID: 4324 at /build/nvidia-lts/src/nvidia/560.35.03/build/nvidia/nv.c:4540 nv_set_system_power_state+0x2d7/0x470 [nvidia]
Sep 09 04:37:32 reyyanarch kernel: CPU: 3 PID: 4324 Comm: nvidia-sleep.sh Tainted: P        W IOE      6.6.49-1-lts #1 219753d0980ba446fc22332bc8c42ed6852afe6e
Sep 09 04:37:33 reyyanarch kernel: CPU: 3 PID: 753 Comm: Xorg Tainted: P        W IOE      6.6.49-1-lts #1 219753d0980ba446fc22332bc8c42ed6852afe6e

Your configuration for the memory preservation seems broken, post /etc/modprobe.d/nvidiafb.conf

In doubt also try https://aur.archlinux.org/packages/nvidia-535xx-dkms - https://bbs.archlinux.org/viewtopic.php?id=298941

# Prevents the nvidiafb module from loading
blacklist nvidiafb

NVreg_PreserveVideoMemoryAllocations=1

added this from a reddit thread i found when i had the issue first so i completely forgot about this.