[SOLVED] Kernel Panic after Suspending

tugoese · 2024-10-16 11:41:37

Like the title said, tried with this but no luck.
Sometimes it freeze with blank screen, here's the log

$ uname -r
6.11.3-273-tkg-bmq

$ pacman -Q | grep nvidia
lib32-nvidia-utils-tkg 560.35.03-258
lib32-opencl-nvidia-tkg 560.35.03-258
libva-nvidia-driver 0.0.12-1
nvidia-dkms-tkg 560.35.03-258
nvidia-egl-wayland-tkg 560.35.03-258
nvidia-settings-tkg 560.35.03-258
nvidia-utils-tkg 560.35.03-258
opencl-nvidia-tkg 560.35.03-258

Any ideas?

Last edited by tugoese (2024-10-26 16:40:38)

seth · 2024-10-16 12:37:28

Oct 16 18:00:08 exe0 kernel: CPU: 0 UID: 0 PID: 985 Comm: nvidia-sleep.sh Tainted: P           OE      6.11.3-273-tkg-bmq #1 1400000003000000474e5500c6db6f9aeb100957
Oct 16 18:00:08 exe0 kernel: CPU: 0 UID: 0 PID: 985 Comm: nvidia-sleep.sh Tainted: P        W  OE      6.11.3-273-tkg-bmq #1 1400000003000000474e5500c6db6f9aeb100957

https://wiki.archlinux.org/title/NVIDIA … er_suspend
What do you set for the nvreg parameters?

Have you tried the behavior w/ the regular kernel?

gromit · 2024-10-16 12:38:20

Is this also an issue when you use the repo packages for linux and nvidia?

tugoese · 2024-10-16 13:29:48

seth wrote:

What do you set for the nvreg parameters?

It's set to 1

Have you tried the behavior w/ the regular kernel?

I haven't use regular kernel for years, so I don't know

gromit wrote:

Is this also an issue when you use the repo packages for linux and nvidia?

You mean the official repo?

This happens after monthly system update (including kernel & nvidia from tkg repo) on 14th.
linux610 --> linux611
nvidia550 (vulkan dev) --> nvidia560

It runs fine on previous version.

tekstryder · 2024-10-16 13:30:15

See:

https://github.com/NVIDIA/open-gpu-kern … issues/662

Affects the proprietary driver as well.

Should be addressed with upcoming 565 driver release.

tekstryder · 2024-10-16 13:45:50

seth wrote:

https://wiki.archlinux.org/title/NVIDIA … er_suspend
What do you set for the nvreg parameters?

tugoese wrote:

seth wrote:
What do you set for the nvreg parameters?
It's set to 1

You should no longer be setting those options manually, as they're baked into nvidia-utils by default now to match upstream requirements.

• https://gitlab.archlinux.org/archlinux/ … 8e6b7c22d7

As I mentioned in another thread recently, you can simply delete /etc/modprobe.d/nvidia.conf following that packaging change, unless you have further modifications contained therein.

The wiki needs a few edits after the many recent changes in nvidia-utils. Unless you stay glued to GitLab, they can be easy to miss.

EDIT: In the same vein, the systemd services for nVidia are now force-enabled when you update to nvidia-utils 560.35.03-16.

• https://gitlab.archlinux.org/archlinux/ … ff35539678

I re-disabled the nvidia-hibernate.service manually following the update, as I do not use hibernation.

Last edited by tekstryder (2024-10-16 13:53:45)

tugoese · 2024-10-16 14:20:42

you can simply delete /etc/modprobe.d/nvidia.conf

Well, I do have other options in there

options nvidia NVreg_UsePageAttributeTable=1
options nvidia_drm modeset=1 fbdev=1

Don't know if I should delete it

I re-disabled the nvidia-hibernate.service manually following the update, as I do not use hibernation.

Me too, should I disable swap permanently?

seth · 2024-10-16 14:36:28

This has nothing to do w/ swap and the service is actually just inert if you don't hibernate, but looking at that patch, nvidia-resume seems a bold choice except for gnome being entirely silly in the wider regard - afair it had caused problems in the past.

tekstryder · 2024-10-16 14:45:55

tugoese wrote:

Well, I do have other options in there
options nvidia NVreg_UsePageAttributeTable=1
options nvidia_drm modeset=1 fbdev=1
Don't know if I should delete it.

As I said, _unless_ you have other options therein. So, no.

tugoese wrote:

Me too, should I disable swap permanently?

Your system, your choice. I'm not advocating, rather simply noting recent relevant packaging changes regarding nvidia.

tekstryder · 2024-10-16 14:54:33

seth wrote:

but looking at that patch, nvidia-resume seems a bold choice except for gnome being entirely silly in the wider regard - afair it had caused problems in the past.

nvidia-resume is required if you're using nvidia-suspend. How is this "bold"?

And, what's that got to do with Gnome? I know you try to fit a jab in at any chance, but I'm at a loss with this one haha.

seth · 2024-10-16 14:56:32

https://wiki.archlinux.org/title/NVIDIA … er_suspend
See the notes, ok, not "gnome", GDM.

Edit: https://wiki.archlinux.org/title/GDM#Wa … DIA_driver
GDM mandates all sorts of random stuff in order to "allow" you to run it on wayland - and the entire process has a tendency to be fragile and leave frustrated users behind, search the forum if you want.

Last edited by seth (2024-10-16 14:58:38)

tekstryder · 2024-10-16 15:03:24

seth wrote:

https://wiki.archlinux.org/title/NVIDIA … er_suspend
See the notes, ok, not "gnome", GDM.

Arch Wiki wrote:

Note that GDM with Wayland however explicitly requires nvidia-resume.service to be enabled.

This? Not sure why, but I'm still missing your point.

In my opinion the force-enabling of all the nVidia systemd services was a "bold" move, but the rationale and concerns were all well-stated/defended in the MR prior to merge:

• https://gitlab.archlinux.org/archlinux/ … equests/16

tekstryder · 2024-10-16 15:05:41

seth wrote:

Edit: https://wiki.archlinux.org/title/GDM#Wa … DIA_driver
GDM mandates all sorts of random stuff in order to "allow" you to run it on wayland - and the entire process has a tendency to be fragile and leave frustrated users behind, search the forum if you want.

Ah, missed your edit. Agreed, a bit hacky.

Been following these forums for 18yrs. Yup, seen some stuff.

seth · 2024-10-16 15:21:42

https://wiki.archlinux.org/index.php?ti … did=799965
The wiki recommendation actually changed a couple of months ago - the collision w/ the sleep hook might have been resolved, the edit isn't commented itr.

Edit: there seems to have been an edit war before a third user just removed the recommendation that had existed for years.
Not sure whether the change was driven by any factual changes…

Last edited by seth (2024-10-16 15:29:01)

tugoese · 2024-10-23 03:27:05

Nvidia 565 series has arrived, no more KP but now it's just a black screen with a cursor. I had to switch tty and restart the display manager, which is kinda annoying.

seth · 2024-10-23 12:55:01

just a black screen with a cursor

On what kind of session (DE and display server), what'd you get otherwise (screensaver/locker)?

Do you currently have https://wiki.archlinux.org/title/NVIDIA … er_suspend in place?
(w/ or w/o the resume.service)

Is fbdev=1 or fbdev=0?

tekstryder · 2024-10-23 12:56:54

tugoese wrote:

Nvidia 565 series has arrived, no more KP but now it's just a black screen with a cursor.

How did you install the 565 beta driver?

What is your GPU hardware?

Please post a current system journal after a suspend/resume cycle.

tugoese · 2024-10-26 14:19:07

seth wrote:

On what kind of session (DE and display server),what'd you get otherwise (screensaver/locker)?

LXQt & X11, neither

Do you currently have https://wiki.archlinux.org/title/NVIDIA … er_suspend in place?
(w/ or w/o the resume.service)

Yes, w/ resume.service

Is fbdev=1 or fbdev=0?

fbdev=1

tekstryder wrote:

How did you install the 565 beta driver?

nvidia-all

What is your GPU hardware?

GTX 1060 6GB

Please post a current system journal after a suspend/resume cycle.

Here

Last edited by tugoese (2024-10-26 14:20:47)

seth · 2024-10-26 14:45:59

Do you run a compositor w/ lxqt (picom)?
Try to suspend w/o such.
Certainly also try "fbdev=0"

And if that doesn't help

Oct 26 21:51:19 exe0 logger[4018]: <13>Oct 26 21:51:19 suspend: nvidia-suspend.service
Oct 26 21:51:19 exe0 rtkit-daemon[674]: Supervising 7 threads of 5 processes of 1 users.
Oct 26 21:51:19 exe0 rtkit-daemon[674]: Successfully made thread 4027 of process 840 owned by '1000' RT at priority 5.
Oct 26 21:51:19 exe0 rtkit-daemon[674]: Supervising 8 threads of 5 processes of 1 users.
Oct 26 21:51:19 exe0 kernel: ------------[ cut here ]------------
Oct 26 21:51:19 exe0 kernel: WARNING: CPU: 0 PID: 4019 at include/linux/rwsem.h:80 follow_pte+0x1de/0x200
Oct 26 21:51:19 exe0 kernel: Modules linked in: ntfs3 nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security rfkill nf_tables libcrc32c ip6table_filter ip6_tables iptable_filter intel_rapl_msr intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_scodec_component snd_hda_intel mousedev x86_pkg_temp_thermal joydev snd_intel_dspcfg snd_intel_sdw_acpi intel_powerclamp snd_hda_codec snd_hda_core usblp coretemp snd_hwdep kvm_intel snd_pcm kvm vfat snd_timer snd crct10dif_pclmul fat crc32_pclmul polyval_clmulni soundcore polyval_generic ghash_clmulni_intel sha512_ssse3 iTCO_wdt mei_hdcp sha256_ssse3 alx mei_pxp intel_pmc_bxt sha1_ssse3 aesni_intel mei_me iTCO_vendor_support gf128mul crypto_simd mdio cryptd mei rapl intel_cstate at24 intel_uncore mac_hid i2c_i801 i2c_smbus
Oct 26 21:51:19 exe0 kernel:  i2c_mux lpc_ich pcspkr vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) i2c_dev dm_mod loop nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 nvidia_uvm(POE) nvidia_drm(POE) drm_ttm_helper ttm nvidia_modeset(POE) ata_generic uas pata_acpi hid_generic usbhid nvidia(POE) usb_storage xhci_pci crc32c_intel ata_piix video xhci_pci_renesas wmi
Oct 26 21:51:19 exe0 kernel: CPU: 0 UID: 0 PID: 4019 Comm: nvidia-sleep.sh Tainted: P           OE      6.11.3-273-tkg-bmq #1 1400000003000000474e5500c6db6f9aeb100957
Oct 26 21:51:19 exe0 kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Oct 26 21:51:19 exe0 kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./H77-DS3H, BIOS F10 11/14/2013
Oct 26 21:51:19 exe0 kernel: RIP: 0010:follow_pte+0x1de/0x200
Oct 26 21:51:19 exe0 kernel: Code: cc cc cc 48 81 e2 00 00 00 c0 48 09 c2 48 f7 d2 48 85 fa 75 20 e8 52 f0 ff ff 48 8b 35 6b f6 5e 01 48 81 e6 00 00 00 c0 eb 8d <0f> 0b 48 3b 1f 0f 83 50 fe ff ff bd ea ff ff ff eb b6 49 8b 3c 24
Oct 26 21:51:19 exe0 kernel: RSP: 0018:ffffa1f14b5f7ab0 EFLAGS: 00010246
Oct 26 21:51:19 exe0 kernel: RAX: 0000000000000000 RBX: 000073a75e603000 RCX: ffffa1f14b5f7af0
Oct 26 21:51:19 exe0 kernel: RDX: ffffa1f14b5f7ae8 RSI: 000073a75e603000 RDI: ffff8bfda2cc8370
Oct 26 21:51:19 exe0 kernel: RBP: ffffa1f14b5f7b30 R08: ffffa1f14b5f7c88 R09: 0000000000000000
Oct 26 21:51:19 exe0 kernel: R10: ffff8bfe33e7b000 R11: ffffffffc4629720 R12: ffffa1f14b5f7af0
Oct 26 21:51:19 exe0 kernel: R13: ffffa1f14b5f7ae8 R14: ffff8bfd4006bc80 R15: ffffa1f14b5f7c88
Oct 26 21:51:19 exe0 kernel: FS:  00007becbc195b80(0000) GS:ffff8c014aa00000(0000) knlGS:0000000000000000
Oct 26 21:51:19 exe0 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 26 21:51:19 exe0 kernel: CR2: 0000589e7bd435e0 CR3: 00000001068be003 CR4: 00000000001706f0
Oct 26 21:51:19 exe0 kernel: Call Trace:
Oct 26 21:51:19 exe0 kernel:  <TASK>
Oct 26 21:51:19 exe0 kernel:  ? follow_pte+0x1de/0x200
Oct 26 21:51:19 exe0 kernel:  ? __warn.cold+0x8e/0xe8
Oct 26 21:51:19 exe0 kernel:  ? follow_pte+0x1de/0x200
Oct 26 21:51:19 exe0 kernel:  ? report_bug+0xff/0x140
Oct 26 21:51:19 exe0 kernel:  ? handle_bug+0x3c/0x80
Oct 26 21:51:19 exe0 kernel:  ? exc_invalid_op+0x17/0x70
Oct 26 21:51:19 exe0 kernel:  ? asm_exc_invalid_op+0x1a/0x20
Oct 26 21:51:19 exe0 kernel:  ? follow_pte+0x1de/0x200
Oct 26 21:51:19 exe0 kernel:  follow_phys+0x49/0x110
Oct 26 21:51:19 exe0 kernel:  untrack_pfn+0x55/0x120
Oct 26 21:51:19 exe0 kernel:  unmap_single_vma+0xb2/0xf0
Oct 26 21:51:19 exe0 kernel:  zap_page_range_single+0x122/0x1d0
Oct 26 21:51:19 exe0 kernel:  unmap_mapping_range+0x116/0x140
Oct 26 21:51:19 exe0 kernel:  nv_revoke_gpu_mappings_locked+0x47/0x70 [nvidia 1400000003000000474e55002c840b24451a0457]
Oct 26 21:51:19 exe0 kernel:  nv_set_system_power_state+0x1cd/0x480 [nvidia 1400000003000000474e55002c840b24451a0457]
Oct 26 21:51:19 exe0 kernel:  nv_procfs_write_suspend+0xef/0x170 [nvidia 1400000003000000474e55002c840b24451a0457]
Oct 26 21:51:19 exe0 kernel:  proc_reg_write+0x5a/0xa0
Oct 26 21:51:19 exe0 kernel:  vfs_write+0xf3/0x450
Oct 26 21:51:19 exe0 kernel:  ? __pte_offset_map+0x1b/0x180
Oct 26 21:51:19 exe0 kernel:  ? __handle_mm_fault+0x89a/0x8c0
Oct 26 21:51:19 exe0 kernel:  ksys_write+0x6d/0xf0
Oct 26 21:51:19 exe0 kernel:  do_syscall_64+0x82/0x190
Oct 26 21:51:19 exe0 kernel:  ? __count_memcg_events+0x57/0xf0
Oct 26 21:51:19 exe0 kernel:  ? count_memcg_events.constprop.0+0x1a/0x30
Oct 26 21:51:19 exe0 kernel:  ? handle_mm_fault+0x1b1/0x2b0
Oct 26 21:51:19 exe0 kernel:  ? do_user_addr_fault+0x33d/0x620
Oct 26 21:51:19 exe0 kernel:  ? exc_page_fault+0x81/0x190
Oct 26 21:51:19 exe0 kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Oct 26 21:51:19 exe0 kernel: RIP: 0033:0x7becbc3127a4
Oct 26 21:51:19 exe0 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
Oct 26 21:51:19 exe0 kernel: RSP: 002b:00007ffc4f2a8598 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Oct 26 21:51:19 exe0 kernel: RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 00007becbc3127a4
Oct 26 21:51:19 exe0 kernel: RDX: 0000000000000008 RSI: 0000634e8c470cd0 RDI: 0000000000000001
Oct 26 21:51:19 exe0 kernel: RBP: 00007ffc4f2a85c0 R08: 0000000000000410 R09: 0000000000000001
Oct 26 21:51:19 exe0 kernel: R10: 0000000000000004 R11: 0000000000000202 R12: 0000000000000008
Oct 26 21:51:19 exe0 kernel: R13: 0000634e8c470cd0 R14: 00007becbc3ee5c0 R15: 00007becbc3ebea0
Oct 26 21:51:19 exe0 kernel:  </TASK>
Oct 26 21:51:19 exe0 kernel: ---[ end trace 0000000000000000 ]---
Oct 26 21:51:19 exe0 kernel: ------------[ cut here ]------------
Oct 26 21:51:19 exe0 kernel: WARNING: CPU: 0 PID: 4019 at include/linux/rwsem.h:80 follow_pte+0x1de/0x200
Oct 26 21:51:19 exe0 kernel: Modules linked in: ntfs3 nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security rfkill nf_tables libcrc32c ip6table_filter ip6_tables iptable_filter intel_rapl_msr intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_scodec_component snd_hda_intel mousedev x86_pkg_temp_thermal joydev snd_intel_dspcfg snd_intel_sdw_acpi intel_powerclamp snd_hda_codec snd_hda_core usblp coretemp snd_hwdep kvm_intel snd_pcm kvm vfat snd_timer snd crct10dif_pclmul fat crc32_pclmul polyval_clmulni soundcore polyval_generic ghash_clmulni_intel sha512_ssse3 iTCO_wdt mei_hdcp sha256_ssse3 alx mei_pxp intel_pmc_bxt sha1_ssse3 aesni_intel mei_me iTCO_vendor_support gf128mul crypto_simd mdio cryptd mei rapl intel_cstate at24 intel_uncore mac_hid i2c_i801 i2c_smbus
Oct 26 21:51:19 exe0 kernel:  i2c_mux lpc_ich pcspkr vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) i2c_dev dm_mod loop nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 nvidia_uvm(POE) nvidia_drm(POE) drm_ttm_helper ttm nvidia_modeset(POE) ata_generic uas pata_acpi hid_generic usbhid nvidia(POE) usb_storage xhci_pci crc32c_intel ata_piix video xhci_pci_renesas wmi

completely disable the VRAM preservation (parameter and services)

tugoese · 2024-10-26 16:39:53

Do you run a compositor w/ lxqt (picom)?
Try to suspend w/o such.
Certainly also try "fbdev=0"

This

tekstryder · 2024-10-26 17:33:04

tugoese wrote:

What is your GPU hardware?
GTX 1060 6GB
try "fbdev=0"
This

Known issue with GPUs of certain older generations. See:

• https://gitlab.archlinux.org/archlinux/ … /issues/16

EDIT: And, as for the errors logged at suspend time see:

• https://bbs.archlinux.org/viewtopic.php … 1#p2204381

Should be fixed with kernel 6.12.

Last edited by tekstryder (2024-10-26 17:40:58)

Arch Linux

#1 2024-10-16 11:41:37

[SOLVED] Kernel Panic after Suspending

#2 2024-10-16 12:37:28

Re: [SOLVED] Kernel Panic after Suspending

#3 2024-10-16 12:38:20

Re: [SOLVED] Kernel Panic after Suspending

#4 2024-10-16 13:29:48

Re: [SOLVED] Kernel Panic after Suspending

#5 2024-10-16 13:30:15

Re: [SOLVED] Kernel Panic after Suspending

#6 2024-10-16 13:45:50

Re: [SOLVED] Kernel Panic after Suspending

#7 2024-10-16 14:20:42

Re: [SOLVED] Kernel Panic after Suspending

#8 2024-10-16 14:36:28

Re: [SOLVED] Kernel Panic after Suspending

#9 2024-10-16 14:45:55

Re: [SOLVED] Kernel Panic after Suspending

#10 2024-10-16 14:54:33

Re: [SOLVED] Kernel Panic after Suspending

#11 2024-10-16 14:56:32

Re: [SOLVED] Kernel Panic after Suspending

#12 2024-10-16 15:03:24

Re: [SOLVED] Kernel Panic after Suspending

#13 2024-10-16 15:05:41

Re: [SOLVED] Kernel Panic after Suspending

#14 2024-10-16 15:21:42

Re: [SOLVED] Kernel Panic after Suspending

#15 2024-10-23 03:27:05

Re: [SOLVED] Kernel Panic after Suspending

#16 2024-10-23 12:55:01

Re: [SOLVED] Kernel Panic after Suspending

#17 2024-10-23 12:56:54

Re: [SOLVED] Kernel Panic after Suspending

#18 2024-10-26 14:19:07

Re: [SOLVED] Kernel Panic after Suspending

#19 2024-10-26 14:45:59

Re: [SOLVED] Kernel Panic after Suspending

#20 2024-10-26 16:39:53

Re: [SOLVED] Kernel Panic after Suspending

#21 2024-10-26 17:33:04

Re: [SOLVED] Kernel Panic after Suspending

Board footer