Created attachment 863125 [details]
Last kernel 6.0.8 boot and crash

Hello I need help to find the root cause of crashes (complete freeze of the
workstation).

Since the introduction of kernel 6.0.8 and latest nvidia 525.53 I constantly
face complete machine freeze, when I'm using my external monitors.

nov 25 16:05:34 qt-kt kernel: BUG: kernel NULL pointer dereference, address:
0000000000000000
nov 25 16:05:34 qt-kt kernel: #PF: supervisor instruction fetch in kernel mode
nov 25 16:05:34 qt-kt kernel: #PF: error_code(0x0010) - not-present page
nov 25 16:05:34 qt-kt kernel: PGD 0 P4D 0
nov 25 16:05:34 qt-kt kernel: Oops: 0010 [#1] PREEMPT SMP PTI
nov 25 16:05:34 qt-kt kernel: CPU: 3 PID: 1004 Comm: nvidia-modeset/ Tainted: P
          OE      6.0.8-1-default #1 openSUSE Tumbleweed
9d20364b934f5aab0a9bdf84e8f45cfdfae39dab
nov 25 16:05:34 qt-kt kernel: Hardware name: Dell Inc. Precision 7510/0YH43H,
BIOS 1.29.3 09/18/2022
nov 25 16:05:34 qt-kt kernel: RIP: 0010:0x0
nov 25 16:05:34 qt-kt kernel: Code: Unable to access opcode bytes at RIP
0xffffffffffffffd6.
nov 25 16:05:34 qt-kt kernel: RSP: 0018:ffffadc300703c90 EFLAGS: 00010207
nov 25 16:05:34 qt-kt kernel: RAX: 0000000000000000 RBX: ffff9b2996c75378 RCX:
0000000000000004
nov 25 16:05:34 qt-kt kernel: RDX: 0000000000000010 RSI: ffff9b2996c75378 RDI:
ffffadc300703a10
nov 25 16:05:34 qt-kt kernel: RBP: ffff9b292ef8b560 R08: 0000000000000000 R09:
0000000000000040
nov 25 16:05:34 qt-kt kernel: R10: ffff9b2886b28008 R11: ffffadc300703c00 R12:
0000000000000000
nov 25 16:05:34 qt-kt kernel: R13: 0000000000000000 R14: ffffffffc4fbee70 R15:
ffffffffc4eb7580
nov 25 16:05:34 qt-kt kernel: FS:  0000000000000000(0000)
GS:ffff9b37c44c0000(0000) knlGS:0000000000000000
nov 25 16:05:34 qt-kt kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
nov 25 16:05:34 qt-kt kernel: CR2: ffffffffffffffd6 CR3: 000000075be10001 CR4:
00000000003706e0
nov 25 16:05:34 qt-kt kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
nov 25 16:05:34 qt-kt kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400
nov 25 16:05:34 qt-kt kernel: Call Trace:
nov 25 16:05:34 qt-kt kernel:  <TASK>
nov 25 16:05:34 qt-kt kernel:  _nv001281kms+0x194/0x1a0 [nvidia_modeset
4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8]
nov 25 16:05:34 qt-kt kernel:  ? _nv001274kms+0x9a/0xd0 [nvidia_modeset
4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8]
nov 25 16:05:34 qt-kt kernel:  ? _nv001466kms+0x172/0x180 [nvidia_modeset
4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8]
nov 25 16:05:34 qt-kt kernel:  ? _nv001149kms+0xf3/0xa50 [nvidia_modeset
4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8]
nov 25 16:05:34 qt-kt kernel:  ? schedule+0x5a/0xd0
nov 25 16:05:34 qt-kt kernel:  ? schedule_timeout+0x10e/0x150
nov 25 16:05:34 qt-kt kernel:  ? nvkms_sema_up+0x10/0x10 [nvidia_modeset
4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8]
nov 25 16:05:34 qt-kt kernel:  ? __down_common+0x10b/0x1e0
nov 25 16:05:34 qt-kt kernel:  ? nvkms_sema_up+0x10/0x10 [nvidia_modeset
4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8]
nov 25 16:05:34 qt-kt kernel:  ? _nv002457kms+0x2d/0x70 [nvidia_modeset
4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8]
nov 25 16:05:34 qt-kt kernel:  ? nvkms_kthread_q_callback+0x88/0xf0
[nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8]
nov 25 16:05:34 qt-kt kernel:  ? _main_loop+0x77/0x130 [nvidia_modeset
4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8]
nov 25 16:05:34 qt-kt kernel:  ? kthread+0xd7/0x100
nov 25 16:05:34 qt-kt kernel:  ? kthread_complete_and_exit+0x20/0x20
nov 25 16:05:34 qt-kt kernel:  ? ret_from_fork+0x1f/0x30
nov 25 16:05:34 qt-kt kernel:  </TASK>
nov 25 16:05:34 qt-kt kernel: Modules linked in: rfcomm snd_seq_dummy
snd_hrtimer snd_seq nf_nat_sip nft_objref af_packet nf_conntrack_sip
nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4
nf_reject_ipv6 nft_reject nft_ct n>
nov 25 16:05:34 qt-kt kernel:  processor_thermal_device_pci_legacy irqbypass
iwlwifi processor_thermal_device pcspkr ledtrig_audio processor_thermal_rfim
snd_usbmidi_lib efi_pstore snd_intel_sdw_acpi sparse_keymap
processor_thermal_mbox cdc_wdm videob>
nov 25 16:05:34 qt-kt kernel:  fuse configfs dmi_sysfs ip_tables x_tables cmac
algif_hash algif_skcipher af_alg hid_logitech_hidpp hid_logitech_dj hid_generic
dm_crypt usbhid essiv authenc trusted asn1_encoder tee bnep btusb btrtl btbcm
btintel btmtk >
nov 25 16:05:34 qt-kt kernel: CR2: 0000000000000000
nov 25 16:05:34 qt-kt kernel: ---[ end trace 0000000000000000 ]---

Most of the time this happen after resuming the screens, the primary one get
on, but the second is always in suspend mode, I have to open neither display
settings in plasma or nvidia-settings to set on the second monitor (displayport
slave link) after switching off and on the monitor.