Thanks wpierce, this only happens when an external monitor is connected, either via HDMI or type C.
Thanks for the additional info. With an external monitor attached via HDMI cable, I’m able to reproduce this with a few attempts. I’ll escalate this bug.
I have filed this bug under bug #2772874.
Thanks wpierce, so we should wait for the next update of the Nvidia driver?
It will take some time to look at. I don’t have a date when it will be fixed by. I will update when I have more information.
Thank you, appreciated!
Hi, i’m currently experiencing this with two machines (both with a GTX 1650).
Is there an issue tracker i am not aware of, where i can follow the bug?
Same issue with a GTX 870M
Arch Linux
Driver: 440.59
Kernel version: 5.5.5
Anyone have a public Discord server? We’re coming up on the one year anniversary of this and I’d like to celebrate that with everyone here lol.
I am also seeing this, every few unlocks. Xorg segfaults in the driver and even vconsole fails to display anything, requiring a restart. This is on a Nvidia 2080 Max-Q.
Kernel: 5.6.6-arch1-1
Nvidia Driver: 440.82
Apr 23 16:06:41 systemd-coredump[17391]: Process 17380 (Xorg) of user 0 dumped core.
Stack trace of thread 17380:
#0 0x00007f3a62222b8d _Unwind_IteratePhdrCallback (libgcc_s.so.1 + 0x11b8d)
#1 0x00007f3a630b4815 dl_iterate_phdr (libc.so.6 + 0x138815)
#2 0x00007f3a62223c56 _Unwind_Find_FDE (libgcc_s.so.1 + 0x12c56)
#3 0x00007f3a62220304 uw_frame_state_for (libgcc_s.so.1 + 0xf304)
#4 0x00007f3a62221510 uw_init_context_1 (libgcc_s.so.1 + 0x10510)
#5 0x00007f3a6222225c _Unwind_Backtrace (libgcc_s.so.1 + 0x1125c)
#6 0x00007f3a63088776 __backtrace (libc.so.6 + 0x10c776)
#7 0x0000562ba024278d xorg_backtrace (Xorg + 0xb378d)
#8 0x0000562ba0238cf8 n/a (Xorg + 0xa9cf8)
#9 0x00007f3a62fb7d70 __restore_rt (libc.so.6 + 0x3bd70)
#10 0x00007f3a6318d72d _dl_fixup (ld-linux-x86-64.so.2 + 0x1072d)
#11 0x00007f3a6319476e _dl_runtime_resolve_xsavec (ld-linux-x86-64.so.2 + 0x1776e)
#12 0x00007f3a6060ee1c n/a (libglamoregl.so + 0x1ee1c)
#13 0x0000562ba02b538f n/a (Xorg + 0x12638f)
#14 0x0000562ba028b83e n/a (Xorg + 0xfc83e)
#15 0x0000562ba02cba34 RRCrtcSet (Xorg + 0x13ca34)
#16 0x0000562ba02cc497 ProcRRSetCrtcConfig (Xorg + 0x13d497)
#17 0x00007f3a61a3cb7d n/a (nvidia_drv.so + 0x4e4b7d)
Also:
Apr 23 16:06:39 kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate fence signaling event
I would note that this is a Razer Blade 2019 Advanced with PRIME synchronization using LightDM and light-locker. This happens when my external gsync monitor is connected via mini displayport.
Hi all,
This issue has been fixed with the latest Vulkan Developer Beta Driver 440.66.11 available here.
It is part of these fixes:
- Fixed several synchronization bugs that could momentarily lock up the X server when moving/resizing/focusing OpenGL and Vulkan windows when PRIME Sync is enabled [Linux]
I will let you know when the fix reaches stable drivers.
This issue still exists with 440.82 driver for me. Does that mean, the Vulkan Beta Driver 440.66.11 has more recent fixes than the 440.82 driver?
I installed the the Vulkan Beta Driver 440.66.11 and I still have crashes.
Is there any workarounds making NVIDIA computers useful again in these days?
Unfortunately, I has just happened again now on my laptop with the latest driver :/
linux55-nvidia-440xx 440.82-6
Here is the stack trace:
May 15 08:41:20 Xtreme kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate fence signaling event
May 15 08:41:20 Xtreme kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate fence signaling event
May 15 08:41:20 Xtreme kernel: BUG: scheduling while atomic: Xorg/1160/0x00000003
May 15 08:41:20 Xtreme kernel: Modules linked in: rfcomm xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_>
May 15 08:41:20 Xtreme kernel: iwlwifi wmi_bmof intel_wmi_thunderbolt fat i915 kvm fuse snd_soc_core ofpart irqbypass intel_cstate intel_uncore psmouse input_leds pcspkr cmdlinepart snd_compress cfg80211 e1000e >
May 15 08:41:20 Xtreme kernel: crc32c_intel ghash_clmulni_intel serio_raw atkbd libps2 aesni_intel sdhci_pci cqhci crypto_simd sdhci cryptd xhci_pci glue_helper xhci_hcd mmc_core i8042 serio
May 15 08:41:20 Xtreme kernel: Preemption disabled at:
May 15 08:41:20 Xtreme kernel: [<0000000000000000>] 0x0
May 15 08:41:20 Xtreme kernel: CPU: 7 PID: 1160 Comm: Xorg Tainted: P OE 5.5.19-1-MANJARO #1
May 15 08:41:20 Xtreme kernel: Hardware name: LENOVO 20QVCTO1WW/20QVCTO1WW, BIOS N2OET42W (1.29 ) 01/20/2020
May 15 08:41:20 Xtreme kernel: Call Trace:
May 15 08:41:20 Xtreme kernel: dump_stack+0x66/0x90
May 15 08:41:20 Xtreme kernel: __schedule_bug.cold+0x8e/0x9b
May 15 08:41:20 Xtreme kernel: __schedule+0x64c/0x7a0
May 15 08:41:20 Xtreme kernel: ? _raw_spin_unlock_irqrestore+0x20/0x40
May 15 08:41:20 Xtreme kernel: schedule+0x46/0xf0
May 15 08:41:20 Xtreme kernel: schedule_hrtimeout_range_clock+0xa5/0x120
May 15 08:41:20 Xtreme kernel: ? hrtimer_init_sleeper+0xa0/0xa0
May 15 08:41:20 Xtreme kernel: usleep_range+0x67/0x90
May 15 08:41:20 Xtreme kernel: __intel_wait_for_register+0x19d/0x200 [i915]
May 15 08:41:20 Xtreme kernel: wait_panel_status+0x171/0x230 [i915]
May 15 08:41:20 Xtreme kernel: edp_panel_on+0x14c/0x210 [i915]
May 15 08:41:20 Xtreme kernel: intel_edp_panel_on+0x24/0x40 [i915]
May 15 08:41:20 Xtreme kernel: intel_ddi_pre_enable+0x177/0xf30 [i915]
May 15 08:41:20 Xtreme kernel: ? _raw_spin_lock_irqsave+0x26/0x50
May 15 08:41:20 Xtreme kernel: ? _raw_spin_unlock_irqrestore+0x20/0x40
May 15 08:41:20 Xtreme kernel: ? fwtable_read32+0x86/0x200 [i915]
May 15 08:41:20 Xtreme kernel: intel_encoders_pre_enable.isra.0+0x65/0x80 [i915]
May 15 08:41:20 Xtreme kernel: haswell_crtc_enable+0x87/0x7e0 [i915]
May 15 08:41:20 Xtreme kernel: intel_update_crtc+0x1bf/0x1e0 [i915]
May 15 08:41:20 Xtreme kernel: skl_commit_modeset_enables+0x286/0x420 [i915]
May 15 08:41:20 Xtreme kernel: intel_atomic_commit_tail+0x325/0x14a0 [i915]
May 15 08:41:20 Xtreme kernel: ? _raw_spin_unlock_irqrestore+0x20/0x40
May 15 08:41:20 Xtreme kernel: ? flush_workqueue_prep_pwqs+0x117/0x130
May 15 08:41:20 Xtreme kernel: ? flush_workqueue+0x1b8/0x450
May 15 08:41:20 Xtreme kernel: intel_atomic_commit+0x2d7/0x350 [i915]
May 15 08:41:20 Xtreme kernel: drm_atomic_connector_commit_dpms+0xd7/0x100 [drm]
May 15 08:41:20 Xtreme kernel: drm_mode_obj_set_property_ioctl+0x169/0x2e0 [drm]
May 15 08:41:20 Xtreme kernel: ? drm_connector_set_obj_prop+0x90/0x90 [drm]
May 15 08:41:20 Xtreme kernel: drm_connector_property_set_ioctl+0x41/0x60 [drm]
May 15 08:41:20 Xtreme kernel: drm_ioctl_kernel+0xb2/0x100 [drm]
May 15 08:41:20 Xtreme kernel: drm_ioctl+0x209/0x360 [drm]
May 15 08:41:20 Xtreme kernel: ? drm_connector_set_obj_prop+0x90/0x90 [drm]
May 15 08:41:20 Xtreme kernel: do_vfs_ioctl+0x4b7/0x730
May 15 08:41:20 Xtreme kernel: ksys_ioctl+0x5e/0x90
May 15 08:41:20 Xtreme kernel: __x64_sys_ioctl+0x16/0x20
May 15 08:41:20 Xtreme kernel: do_syscall_64+0x4e/0x150
May 15 08:41:20 Xtreme kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
May 15 08:41:20 Xtreme kernel: RIP: 0033:0x7f82db0be2eb
May 15 08:41:20 Xtreme kernel: Code: 0f 1e fa 48 8b 05 a5 8b 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 75 8b 0c 00>
May 15 08:41:20 Xtreme kernel: RSP: 002b:00007fff1637b848 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
May 15 08:41:20 Xtreme kernel: RAX: ffffffffffffffda RBX: 00007fff1637b880 RCX: 00007f82db0be2eb
May 15 08:41:20 Xtreme kernel: RDX: 00007fff1637b880 RSI: 00000000c01064ab RDI: 0000000000000015
May 15 08:41:20 Xtreme kernel: RBP: 00000000c01064ab R08: 00005628295cc6d0 R09: 0000000000000000
May 15 08:41:20 Xtreme kernel: R10: 00005628295cc6d0 R11: 0000000000000246 R12: 0000562829838160
May 15 08:41:20 Xtreme kernel: R13: 0000000000000015 R14: 000056282a178d60 R15: 0000000000000000
It’s quite a random bug. I had no issue for two weeks, locking, suspending, hibernating, … and then here locking my laptop for 20min triggered the issue.
Thanks for the help :)
Same here, interestingly enough, on the same kind of machine (Thinkpad X1 Extreme gen1) and same driver version (440.82). Typically crashes about once a week, always when the display is turned off (by screensaver) and almost systematically when I’m waking up the display to unlock the screen. I’m never suspending/hibernating the system, just lock the screen (which turns it off).
May 27 18:47:07 vanilla kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate fence signaling event
May 27 18:47:07 vanilla kernel: BUG: scheduling while atomic: X/5185/0x00000002
May 27 18:47:07 vanilla kernel: Modules linked in: xt_nat veth wireguard(E) ip6_udp_tunnel udp_tunnel msr 8021q garp mrp ccm vmnet(OE) vmmon(OE) vmw_vsock_vmci_transport vsock vmw_vmci xt_recent ipt_REJECT nf_reject_ipv4 xt_multiport xt_conntrack xt_hashlimit xt_addrtype xt_mark iptable_mangle xt_MASQUERADE xt_tcpudp xt_CT iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp iptable_filter iptable_nat nf_nat ip_tables x_tables bridge stp llc nf_conntrack_netlink nfnetlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo sd_mod nvidia_drm(POE) uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel wacom videobuf2_common hid_generic bluetooth
May 27 18:47:07 vanilla kernel: videodev uas usbhid ecdh_generic usb_storage mc hid ecc joydev mousedev x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_sof_pci irqbypass snd_sof_intel_byt snd_sof_intel_ipc snd_sof_xtensa_dsp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda nvidia_modeset(POE) snd_hda_codec_realtek snd_sof crct10dif_pclmul snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_ext_core crc32_pclmul snd_soc_acpi_intel_match snd_soc_acpi iTCO_wdt ghash_clmulni_intel iTCO_vendor_support mei_wdt 8250_dw mei_hdcp snd_soc_core aesni_intel iwlmvm intel_rapl_msr wmi_bmof nvidia(POE) crypto_simd intel_wmi_thunderbolt mac80211 snd_compress cryptd ac97_bus snd_pcm_dmaengine i915 glue_helper libarc4 snd_hda_intel i2c_algo_bit intel_cstate snd_intel_nhlt intel_uncore drm_kms_helper psmouse snd_hda_codec input_leds intel_rapl_perf iwlwifi e1000e drm serio_raw i2c_i801 snd_hda_core pcspkr ipmi_devintf tpm_crb snd_hwdep intel_gtt agpgart snd_pcm ipmi_msghandler thunderbolt thinkpad_acpi
May 27 18:47:07 vanilla kernel: intel_lpss_pci cfg80211 syscopyarea mei_me processor_thermal_device xhci_pci sysfillrect nvram sysimgblt intel_rapl_common intel_lpss snd_timer ucsi_acpi ledtrig_audio mei xhci_hcd tpm_tis idma64 fb_sys_fops intel_soc_dts_iosf rfkill typec_ucsi intel_pch_thermal tpm_tis_core snd tpm typec wmi i2c_dev soundcore battery int3403_thermal ac int340x_thermal_zone evdev int3400_thermal acpi_thermal_rel mac_hid msdos fat cramfs mtd overlay squashfs loop virtiofs fuse f2fs xfs nfs lockd grace sunrpc fscache jfs reiserfs btrfs xor raid6_pq crc32c_intel crc32c_generic libcrc32c ext4 crc16 mbcache jbd2 virtio_crypto crypto_engine virtio_mmio virtio_pci virtio_input virtio_balloon virtio_rng rng_core virtio_console virtio_blk virtio_scsi scsi_mod
May 27 18:47:07 vanilla kernel: Preemption disabled at:
May 27 18:47:07 vanilla kernel: [<0000000000000000>] 0x0
May 27 18:47:07 vanilla kernel: CPU: 9 PID: 5185 Comm: X Tainted: P U OE 5.4.38-gentoo-x86_64 #1
May 27 18:47:07 vanilla kernel: Hardware name: LENOVO 20MFCTO1WW/20MFCTO1WW, BIOS N2EET45W (1.27 ) 02/06/2020
May 27 18:47:07 vanilla kernel: Call Trace:
May 27 18:47:07 vanilla kernel: dump_stack+0x66/0x90
May 27 18:47:07 vanilla kernel: __schedule_bug.cold+0x8e/0x9b
May 27 18:47:07 vanilla kernel: __schedule+0x633/0x770
May 27 18:47:07 vanilla kernel: schedule+0x43/0xd0
May 27 18:47:07 vanilla kernel: schedule_hrtimeout_range_clock+0xa5/0x120
May 27 18:47:07 vanilla kernel: ? hrtimer_init_sleeper+0xa0/0xa0
May 27 18:47:07 vanilla kernel: usleep_range+0x67/0x90
May 27 18:47:07 vanilla kernel: skl_pcode_request+0xd7/0x210 [i915]
May 27 18:47:07 vanilla kernel: skl_set_cdclk+0x59/0x520 [i915]
May 27 18:47:07 vanilla kernel: intel_set_cdclk+0x52/0x110 [i915]
May 27 18:47:07 vanilla kernel: intel_atomic_commit_tail+0x10a6/0x1510 [i915]
May 27 18:47:07 vanilla kernel: ? flush_workqueue_prep_pwqs+0x117/0x130
May 27 18:47:07 vanilla kernel: ? flush_workqueue+0x1b8/0x450
May 27 18:47:07 vanilla kernel: intel_atomic_commit+0x284/0x2b0 [i915]
May 27 18:47:07 vanilla kernel: drm_atomic_connector_commit_dpms+0xd7/0x100 [drm]
May 27 18:47:07 vanilla kernel: drm_mode_obj_set_property_ioctl+0x169/0x2c0 [drm]
May 27 18:47:07 vanilla kernel: ? drm_connector_set_obj_prop+0x90/0x90 [drm]
May 27 18:47:07 vanilla kernel: drm_connector_property_set_ioctl+0x41/0x60 [drm]
May 27 18:47:07 vanilla kernel: drm_ioctl_kernel+0xb2/0x100 [drm]
May 27 18:47:07 vanilla kernel: drm_ioctl+0x209/0x360 [drm]
May 27 18:47:07 vanilla kernel: ? drm_connector_set_obj_prop+0x90/0x90 [drm]
May 27 18:47:07 vanilla kernel: do_vfs_ioctl+0x43d/0x6c0
May 27 18:47:07 vanilla kernel: ksys_ioctl+0x5e/0x90
May 27 18:47:07 vanilla kernel: ? ksys_read+0xcc/0xe0
May 27 18:47:07 vanilla kernel: __x64_sys_ioctl+0x16/0x20
May 27 18:47:07 vanilla kernel: do_syscall_64+0x4e/0x140
May 27 18:47:07 vanilla kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
May 27 18:47:07 vanilla kernel: RIP: 0033:0x7f12ccc5ed37
May 27 18:47:07 vanilla kernel: Code: 00 00 90 48 8b 05 59 31 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 29 31 0c 00 f7 d8 64 89 01 48
May 27 18:47:07 vanilla kernel: RSP: 002b:00007fffd01ed658 EFLAGS: 00003246 ORIG_RAX: 0000000000000010
May 27 18:47:07 vanilla kernel: RAX: ffffffffffffffda RBX: 00007fffd01ed690 RCX: 00007f12ccc5ed37
May 27 18:47:07 vanilla kernel: RDX: 00007fffd01ed690 RSI: 00000000c01064ab RDI: 000000000000000b
May 27 18:47:07 vanilla kernel: RBP: 00000000c01064ab R08: 000055faa67f1c00 R09: 0000000000000000
May 27 18:47:07 vanilla kernel: R10: 000055faa67f1c00 R11: 0000000000003246 R12: 000055faa6a09330
May 27 18:47:07 vanilla kernel: R13: 000000000000000b R14: 000055faa6a18f60 R15: 000055faa4c4ea3c
Same thing here with a similar laptop (Thinkpad X1 Extreme Gen2), same driver version (440.82) while trying to turn the screen on after an inactivity period.
Jun 12 13:44:00 geekuillaume-laptop kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate fence signaling event
Jun 12 13:44:00 geekuillaume-laptop kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate fence signaling event
Jun 12 13:44:00 geekuillaume-laptop audit[1493]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=1493 comm="Xorg" exe="/usr/lib/Xorg" sig=11 res=1
Jun 12 13:44:00 geekuillaume-laptop kernel: BUG: scheduling while atomic: Xorg/1493/0x00000003
Jun 12 13:44:00 geekuillaume-laptop kernel: Modules linked in: xt_nat xt_tcpudp veth snd_seq_dummy snd_hrtimer snd_seq rfcomm ccm acpi_call(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user x>
Jun 12 13:44:00 geekuillaume-laptop kernel: audit: type=1701 audit(1591962240.561:343): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=1493 comm="Xorg" exe="/usr/lib/Xorg" sig=11 res=1
Jun 12 13:44:00 geekuillaume-laptop kernel: br_netfilter bridge overlay fuse nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) cmac algif_hash algif_skcipher af_alg ipmi_devintf ipmi_msghandler msr snd_hda_codec_co>
Jun 12 13:44:00 geekuillaume-laptop kernel: irqbypass snd_intel_dspcfg intel_cstate i2c_algo_bit snd_hda_codec intel_uncore tpm_crb cfg80211 drm_kms_helper intel_rapl_perf psmouse snd_hda_core ofpart input_leds c>
Jun 12 13:44:00 geekuillaume-laptop kernel: xhci_pci xhci_hcd rtsx_pci i8042 serio battery
Jun 12 13:44:00 geekuillaume-laptop kernel: Preemption disabled at:
Jun 12 13:44:00 geekuillaume-laptop kernel: [<0000000000000000>] 0x0
Jun 12 13:44:00 geekuillaume-laptop kernel: CPU: 0 PID: 1493 Comm: Xorg Tainted: P OE 5.6.15-arch1-1 #1
Jun 12 13:44:00 geekuillaume-laptop kernel: Hardware name: LENOVO 20QVCTO1WW/20QVCTO1WW, BIOS N2OET42W (1.29 ) 01/20/2020
Jun 12 13:44:00 geekuillaume-laptop kernel: Call Trace:
Jun 12 13:44:00 geekuillaume-laptop kernel: dump_stack+0x64/0x88
Jun 12 13:44:00 geekuillaume-laptop kernel: __schedule_bug.cold+0x8e/0x9b
Jun 12 13:44:00 geekuillaume-laptop kernel: __schedule+0x69b/0x8a0
Jun 12 13:44:00 geekuillaume-laptop kernel: schedule+0x46/0xf0
Jun 12 13:44:00 geekuillaume-laptop kernel: schedule_timeout+0x12a/0x160
Jun 12 13:44:00 geekuillaume-laptop kernel: wait_for_completion+0xc9/0x130
Jun 12 13:44:00 geekuillaume-laptop kernel: ? wake_up_q+0xa0/0xa0
Jun 12 13:44:00 geekuillaume-laptop kernel: do_coredump+0x40c/0x1202
Jun 12 13:44:00 geekuillaume-laptop kernel: ? kfree+0xc4/0x250
Jun 12 13:44:00 geekuillaume-laptop kernel: get_signal+0x4c2/0x900
Jun 12 13:44:00 geekuillaume-laptop kernel: do_signal+0x43/0x680
Jun 12 13:44:00 geekuillaume-laptop kernel: ? kick_process+0x46/0x70
Jun 12 13:44:00 geekuillaume-laptop kernel: prepare_exit_to_usermode+0x115/0x1c0
Jun 12 13:44:00 geekuillaume-laptop kernel: ret_from_intr+0x25/0x25
Jun 12 13:44:00 geekuillaume-laptop kernel: RIP: 0033:0x7f2e1158b34d
Jun 12 13:44:00 geekuillaume-laptop kernel: Code: 58 b8 ff ff ff ff 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 48 8b 51 20 48 3b 15 dd 6c 00 00 48 8b 71 28 0f 84 9b 00 00 00 <48> 89 15 cc 6c 00 00 48 8d 15 b5 6d>
Jun 12 13:44:00 geekuillaume-laptop kernel: RSP: 002b:00007ffc43feae40 EFLAGS: 00010212
Jun 12 13:44:00 geekuillaume-laptop kernel: RAX: 000055d7b99ce040 RBX: 00007ffc43feaf80 RCX: 00007ffc43feaef0
Jun 12 13:44:00 geekuillaume-laptop kernel: RDX: 0000000000000061 RSI: 0000000000000000 RDI: 0000000000000040
Jun 12 13:44:00 geekuillaume-laptop kernel: RBP: 0000000000000061 R08: 000055d7b99ce000 R09: 0000000000000000
Jun 12 13:44:00 geekuillaume-laptop kernel: R10: 00000000000003ff R11: 0000000000000000 R12: 00007f2e1230d000
Jun 12 13:44:00 geekuillaume-laptop kernel: R13: 0000000000000000 R14: 00007ffc43feaf80 R15: 00007f2e1230e140
I had been using a custom compiled kernel to test out the 5.7 branch and I hadn’t run into this issue since I started running that kernel.
With the release of the 5.7 stable kernel, I reverted to arch’s official kernel and immediately this started happening. The driver would segfault every time I tried to change my display configuration through xrandr if it was connected through my thunderbolt dock, and if it was connected to my laptop’s mini-DP output, the driver would segfault every time the screen lock was activated.
Testing again on my custom-compiled kernel, no issues at all.
So I diffed lsmod from both kernels and I realized on my custom kernel I did not have the thunderbolt module (I was specifically testing USB4, so that makes sense), but I did have that on the default kernel.
Maybe there’s something here. Maybe this is an issue with thunderbolt, somehow? Looking through this post, it looks like everyone running into this issue has a laptop with thunderbolt.
Just to be clear, this happens weather or not the display is connected via thunderbolt, but unloading the thunderbolt module seems to fix the issue.
This is on 440.82 btw.
Hi all,
The fix to this issue is available in the 450 driver series (both the Beta which is out now and the Stable when it comes out.) The 450 Beta driver is currently available here: Linux x64 (AMD64/EM64T) Display Driver | 450.51 | Linux 64-bit | NVIDIA.
Note this Beta is not the Vulkan Developer Beta driver series I pointed to before.
Hi,
blacklisting thunderbolt module fixes the issue for me too on 440.82 with kernel 5.7.
Can we enable thunderbolt again with 450 driver series? Thanks