Frequent kernel oops related to nvidia / nv_drm_master_set

Bug #1930903 reported by Christian Nassau
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux-restricted-modules (Ubuntu)
Confirmed
Undecided
Unassigned
nvidia-graphics-drivers-460 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After upgrading yesterday from ubuntu 20 to 21.04 my machine now exhibits frequent involuntary restarts, related to a kernel oops of the form

Jun 3 10:48:32 zotac kernel: [ 20.464926] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
[...]
Jun 3 10:48:32 zotac kernel: [ 20.464958] Call Trace:
Jun 3 10:48:32 zotac kernel: [ 20.464964] drm_new_set_master+0x7e/0x100 [drm]
Jun 3 10:48:32 zotac kernel: [ 20.464994] drm_master_open+0x6e/0xa0 [drm]
Jun 3 10:48:32 zotac kernel: [ 20.465017] drm_open+0xf8/0x250 [drm]
Jun 3 10:48:32 zotac kernel: [ 20.465044] drm_stub_open+0xba/0x140 [drm]
Jun 3 10:48:32 zotac kernel: [ 20.465070] chrdev_open+0xf7/0x220
Jun 3 10:48:32 zotac kernel: [ 20.465075] ? cdev_device_add+0x90/0x90
Jun 3 10:48:32 zotac kernel: [ 20.465078] do_dentry_open+0x156/0x370
Jun 3 10:48:32 zotac kernel: [ 20.465081] vfs_open+0x2d/0x30
Jun 3 10:48:32 zotac kernel: [ 20.465084] do_open+0x1c3/0x340
Jun 3 10:48:32 zotac kernel: [ 20.465087] path_openat+0x10a/0x1d0
Jun 3 10:48:32 zotac kernel: [ 20.465090] do_filp_open+0x8c/0x130
Jun 3 10:48:32 zotac kernel: [ 20.465093] ? __check_object_size+0x1c/0x20
Jun 3 10:48:32 zotac kernel: [ 20.465096] do_sys_openat2+0x9b/0x150
Jun 3 10:48:32 zotac kernel: [ 20.465099] __x64_sys_openat+0x56/0x90
Jun 3 10:48:32 zotac kernel: [ 20.465102] do_syscall_64+0x38/0x90
Jun 3 10:48:32 zotac kernel: [ 20.465105] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun 3 10:48:32 zotac kernel: [ 20.465108] RIP: 0033:0x7fe6ea270954

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.0a.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021
 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Jun 4 17:00:45 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 460.80, 5.11.0-18-generic, x86_64: installed
 nvidia, 460.80, 5.8.0-53-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438]
InstallationDate: Installed on 2020-05-09 (391 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: NA ZBOX-ER51070
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash crashkernel=512M-:192M vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2019
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.asset.tag: Default string
dmi.board.name: ZBOX-ER51070
dmi.board.vendor: NA
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: ZBOX-ER51070
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: NA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

Revision history for this message
Christian Nassau (nassau) wrote :
affects: ubuntu → xorg (Ubuntu)
tags: added: nvidia
affects: xorg (Ubuntu) → nvidia-graphics-drivers-460 (Ubuntu)
Revision history for this message
Christian Nassau (nassau) wrote :

I'm somewhat embarrassed to report that these frequent oopses which occured during the first day after upgrading Ubuntu have not reappeared. One possible explanation is that all these crashes triggered an automatic reboot without actually powering off the machine: could this possibly have left the graphic card in an unexpected state that persisted across soft-reboots and was responsible for these problems?

Anyway, after a proper hardware reset and reboot ten+ days ago these problems have not reappeared once. I would propose to close this issue as invalid/wontfix/nothing-to-see-here...

Yao Wei (medicalwei)
tags: added: oem-priority originate-from-1939083 somerville
Yao Wei (medicalwei)
no longer affects: oem-priority
tags: removed: oem-priority originate-from-1939083
tags: removed: somerville
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers-460 (Ubuntu):
status: New → Confirmed
Revision history for this message
fuomag (fuomag) wrote :

Mine does not reboot but I still have logs in dmesg

226290.971074] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
[226290.971078] Code: 30 26 de 0f 1f 44 00 00 55 48 8b 47 48 48 8b 78 20 48 8b 05 bb 6c 00 00 48 89 e5 48 8b 40 28 e8 ef 8f 62 de 84 c0 74 02 5d c3 <0f> 0b 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56
[226290.971080] RSP: 0018:ffffb2ec90bafb80 EFLAGS: 00010246
[226290.971082] RAX: 0000000000000000 RBX: ffff91442f145400 RCX: 0000000000000008
[226290.971083] RDX: ffffffffc12d0ed8 RSI: 0000000000000292 RDI: ffffffffc12d0ea0
[226290.971084] RBP: ffffb2ec90bafb80 R08: 0000000000000008 R09: ffffb2ec90bafb68
[226290.971085] R10: 0000000000000000 R11: ffff91449a2e4db2 R12: ffff914e42620cc0
[226290.971086] R13: ffff9144849a2000 R14: 0000000000000000 R15: ffff9144849a2000
[226290.971087] FS: 00007f71ad066740(0000) GS:ffff91537ec40000(0000) knlGS:0000000000000000
[226290.971089] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[226290.971090] CR2: 00007f71abbed000 CR3: 000000022f62a000 CR4: 0000000000350ee0
[226290.971091] Call Trace:
[226290.971094] drm_new_set_master+0x7e/0x100 [drm]
[226290.971114] drm_master_open+0x6e/0xa0 [drm]
[226290.971132] drm_open+0xf8/0x250 [drm]
[226290.971149] drm_stub_open+0xba/0x140 [drm]
[226290.971168] chrdev_open+0xf7/0x220
[226290.971172] ? cdev_device_add+0x90/0x90
[226290.971174] do_dentry_open+0x156/0x370
[226290.971176] vfs_open+0x2d/0x30
[226290.971178] do_open+0x1c3/0x340
[226290.971180] path_openat+0x10a/0x1d0
[226290.971182] do_filp_open+0x8c/0x130
[226290.971184] ? __check_object_size+0x1c/0x20
[226290.971187] do_sys_openat2+0x9b/0x150
[226290.971189] __x64_sys_openat+0x56/0x90
[226290.971191] do_syscall_64+0x38/0x90
[226290.971193] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[226290.971196] RIP: 0033:0x7f71ad5108db
[226290.971198] Code: 25 00 00 41 00 3d 00 00 41 00 74 4b 64 8b 04 25 18 00 00 00 85 c0 75 67 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 91 00 00 00 48 8b 4c 24 28 64 48 2b 0c 25
[226290.971199] RSP: 002b:00007ffced99e140 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
[226290.971201] RAX: ffffffffffffffda RBX: 0000560941202120 RCX: 00007f71ad5108db
[226290.971202] RDX: 0000000000080002 RSI: 00005609412077e0 RDI: 00000000ffffff9c
[226290.971203] RBP: 00005609412077e0 R08: 00007f71abbcd4f0 R09: 0000560941207aa2
[226290.971204] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000080002
[226290.971205] R13: 00007f71abfea120 R14: 00005609412063a0 R15: 00007f71abfcc7a9
[226290.971207] ---[ end trace 6e93d5846e18c259 ]---

Revision history for this message
Drake Siard (drakesiard) wrote :
Download full text (4.3 KiB)

Confirmed, I see many instances of the same. Trace below, can post anything else required.

[16772.065057] WARNING: CPU: 4 PID: 12381 at build/nvidia/470.57.02/build/nvidia-drm/nvidia-drm-drv.c:574 nv_drm_master_set+0x27/0x30 [nvidia_drm]
[16772.065067] Modules linked in: nvidia_uvm(PO) nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic intel_rapl_msr snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc mei_hdcp snd_sof snd_hda_codec_hdmi snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio intel_rapl_common snd_hda_intel x86_pkg_temp_thermal intel_powerclamp snd_intel_dspcfg nvidia_drm(PO) soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec snd_hda_core soundwire_bus nvidia_modeset(PO) snd_usb_audio kvm_intel snd_soc_core snd_usbmidi_lib snd_compress snd_hwdep r8153_ecm snd_seq_midi ac97_bus snd_seq_midi_event kvm cdc_ether snd_pcm_dmaengine usbnet snd_rawmidi mc r8152 snd_seq intel_cstate efi_pstore eeepc_wmi wmi_bmof ee1004 mii snd_pcm nvidia(PO) input_leds snd_seq_device joydev snd_timer snd mei_me soundcore mei sch_fq_codel nct6775 hwmon_vid coretemp msr mac_hid acpi_pad acpi_tad parport_pc ppdev lp
[16772.065155] parport ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid uas usb_storage i915 asus_wmi sparse_keymap mfd_aaeon i2c_algo_bit crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel syscopyarea aesni_intel sysfillrect sysimgblt fb_sys_fops crypto_simd cec cryptd glue_helper rc_core e1000e i2c_i801 drm i2c_smbus nvme intel_lpss_pci ahci intel_lpss nvme_core idma64 xhci_pci libahci virt_dma xhci_pci_renesas wmi video pinctrl_tigerlake
[16772.065208] CPU: 4 PID: 12381 Comm: gpu-manager Tainted: P W O 5.11.0-31-generic #33-Ubuntu
[16772.065211] Hardware name: ASUS System Product Name/PRIME B560M-A, BIOS 0820 04/27/2021
[16772.065213] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
[16772.065220] Code: c0 f8 be 0f 1f 44 00 00 55 48 8b 47 48 48 8b 78 20 48 8b 05 bb 6c 00 00 48 89 e5 48 8b 40 28 e8 0f 30 35 bf 84 c0 74 02 5d c3 <0f> 0b 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56
[16772.065224] RSP: 0018:ffffb649855cfb80 EFLAGS: 00010246
[16772.065227] RAX: 0000000000000000 RBX: ffff97e21cf48600 RCX: 0000000000000008
[16772.065229] RDX: ffffffffc31ffed8 RSI: 0000000000000292 RDI: ffffffffc31ffea0
[16772.065231] RBP: ffffb649855cfb80 R08: 0000000000000008 R09: ffffb649855cfb68
[16772.065233] R10: 0000000000000000 R11: ffff97e100459ff2 R12: ffff97e2a7f33cc0
[16772.065235] R13: ffff97e117089800 R14: 0000000000000000 R15: ffff97e117089800
[16772.065237] FS: 00007fe249a08c80(0000) GS:ffff97e44f500000(0000) knlGS:0000000000000000
[16772.065240] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[16772.065243] CR2: 00007fe249de1340 CR3: 00000002195bc001 CR4: 0000000000770ee0
[16772.065245] PKRU: 55555554
[16772.065247] Call Trace:
[16772.065249] drm_new_set_master+0x7e/0x100 [drm]
[16772.065281] drm_master_open+0x6e/0xa0 [drm]
[16772.065311] drm_open+0xf8/0x250 [drm]
[16772.065343] drm_stub_open+0xba/0x140 [drm]
[16772.065380] chrdev_open+0xf7/0x220
[16772.065386] ? c...

Read more...

Revision history for this message
Tim Eves (tim-eves) wrote (last edit ):
Download full text (11.1 KiB)

I am seeing the same bug, specifically both linux-modules-nvidia-460-generic and linux-modules-nvidia-470-generic Ubuntu packaged pre-built modules. I do not have dkms installed. These messages do not occur periodically on their own, but do seem to occur multiple times in quick succession after un-blanking and unlocking the laptop after the screen-saver has blanked the displays. I have a 2nd screen plugged in via DisplayPort. The machine is pugged into mains power and has not suspended or hibernated, between the screen locking and being unlocked a few hours later. This machine is operating in prime-select on-demand mode, with Hybrid graphics enabled in the UEFI BIOS.

Log from 460 version see below for one from then 470 version.
------------[ cut here ]------------
Sep 10 22:07:08 tim-ThinkPad-P17 kernel: WARNING: CPU: 10 PID: 195514 at build/nvidia/460.91.03/build/nvidia-drm/nvidia-drm-drv.c:530 nv_drm_master_set+0x27/0x30 [nvidia_drm]
Sep 10 22:07:08 tim-ThinkPad-P17 kernel: Modules linked in: exfat mmc_block hid_logitech_hidpp uhid rfcomm xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype nft_compat br_netfilter ccm nft_counter nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct bridge stp llc nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 overlay ip_set nf_tables nfnetlink cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 nvidia_uvm(PO) nvidia_drm(PO) nvidia_modeset(PO) snd_sof_pci snd_sof_intel_hda_common snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi nvidia(PO) x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel snd_hda_codec_realtek mei_hdcp snd_hda_codec_generic intel_rapl_msr kvm iwlmvm snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence
Sep 10 22:07:08 tim-ThinkPad-P17 kernel: crct10dif_pclmul snd_hda_codec ghash_clmulni_intel mac80211 aesni_intel snd_hda_core crypto_simd cryptd glue_helper soundwire_bus rapl btusb btrtl btbcm libarc4 snd_usb_audio uvcvideo snd_soc_core thinkpad_acpi intel_cstate btintel videobuf2_vmalloc processor_thermal_device snd_usbmidi_lib iwlwifi snd_hwdep bluetooth cdc_ether videobuf2_memops processor_thermal_rfim videobuf2_v4l2 usbnet processor_thermal_mbox efi_pstore intel_wmi_thunderbolt wmi_bmof snd_compress videobuf2_common nvram ac97_bus snd_seq_midi ledtrig_audio ee1004 r8152 snd_seq_midi_event videodev snd_rawmidi snd_pcm_dmaengine mii joydev input_leds ucsi_acpi processor_thermal_rapl mei_me intel_rapl_common mc typec_ucsi ecdh_generic cfg80211 snd_pcm ecc mei intel_soc_dts_iosf intel_pch_thermal serio_raw typec snd_seq snd_seq_device snd_timer snd soundcore int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport ip_tables x_tables
Sep 10 22:07:08 tim-ThinkPad-P17 kernel: autofs4 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) btrfs blake2b_generic xor hid_generic usbhid hid raid6_pq libcrc32c ...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Revision history for this message
Tim Eves (tim-eves) wrote (last edit ):

This bug affects also the signed and ubuntu packaged versions distributed via the linux-modules-nvidia-{460,470}-generic binary packages and their dependencies

Changed in linux-restricted-modules (Ubuntu):
status: New → Confirmed
Tim Eves (tim-eves)
affects: nvidia-graphics-drivers-470 (Ubuntu) → linux-restricted-modules (Ubuntu)
Revision history for this message
Duane Johnson (duane-johnson) wrote :

Additional helpful insights from osmoticum on the Nvidia forum:

The Xorg modesetting DDX seems to be fighting with the Nvidia DDX for DRM nodes

[ 463.657] (II) modeset(G0): using drv /dev/dri/card0

but

[ 463.658] (II) Applying OutputClass "nvidia" options to /dev/dri/card0

Nvidia appears to be adding a lot of DRM related stuff to the kernel driver (so it looks a lot like a real DRM driver to userspace now) and the modesetting DDX is getting further into its initialization.

In my case, pointing the modesetting DDX to only look at non-Nvidia devices (the kmsdev option) and ensuring all the Nvidia kernel modules are fully loaded (instead of having them load on-demand) before starting X worked around this. The latter is for some weird race condition where the Nvidia driver is only partially loaded and https://gitlab.freedesktop.org/xorg/xserver/-/blob/master/config/udev.c#L135 fails, which causes modesetting to load regardless (it’s hardcoded in xf86platformAddDevice)

The WARN_ON itself can still be triggered by simply opening a Nvidia primary DRM node though, e.g. with https://gitlab.freedesktop.org/mesa/drm/-/blob/master/tests/drmdevice.c, when some other DRM client like X or fbcon already has master. Because of https://patchwork.freedesktop.org/patch/367748 the Nvidia kernel driver can no longer use its internal grabOwnership to report if DRM master can be taken.

https://forums.developer.nvidia.com/t/kernel-oops-on-boot-5-9-13-with-455-45-01/163751

Revision history for this message
Alireza Mortazavi (trans-paypal) wrote :
Download full text (4.8 KiB)

I have the same issue, causes screen freezes. Sometime I have to reset the PC manually.

```
[ 833.144906] ------------[ cut here ]------------
[ 833.144911] WARNING: CPU: 0 PID: 5386 at /var/lib/dkms/nvidia/470.63.01/build/nvidia-drm/nvidia-drm-drv.c:574 nv_drm_master_set+0x27/0x30 [nvidia_drm]
[ 833.144922] Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ip6table_filter ip6_tables iptable_filter bpfilter nvidia_uvm(POE) nvidia_drm(POE) nvidia_modeset(POE) snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_usb_audio snd_usbmidi_lib snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec nvidia(POE) snd_hda_core snd_hwdep hid_a4tech snd_pcm coretemp snd_seq_midi kvm_intel snd_seq_midi_event kvm snd_rawmidi rt2800pci snd_seq isl6421 rt2800mmio rt2800lib rt2x00pci rt2x00mmio b2c2_flexcop_pci input_leds rt2x00lib serio_raw mac80211 b2c2_flexcop snd_seq_device s5h1420 cx24113 cx24123 dvb_core snd_timer drm_kms_helper mc cfg80211 cec rc_core eeprom_93cx6 snd fb_sys_fops libarc4 syscopyarea sysfillrect sysimgblt soundcore x38_edac mac_hid sch_fq_codel msr parport_pc ppdev lp parport drm sunrpc ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0
[ 833.145001] multipath linear system76_io(OE) wmi system76_acpi(OE) pata_acpi gpio_ich firewire_ohci hid_generic i2c_i801 firewire_core i2c_smbus lpc_ich crc_itu_t r8169 usbhid realtek ahci libahci pata_jmicron hid
[ 833.145022] CPU: 0 PID: 5386 Comm: gst-plugin-scan Tainted: P OE 5.13.0-7614-generic #14~1631647151~20.04~930e87c-Ubuntu
[ 833.145025] Hardware name: Gigabyte Technology Co., Ltd. X48-DQ6/X48-DQ6, BIOS F8D 04/24/2009
[ 833.145027] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
[ 833.145033] Code: 0f 1f 00 0f 1f 44 00 00 55 48 8b 47 38 48 8b 78 20 48 8b 05 cb 6c 00 00 48 89 e5 48 8b 40 28 e8 7f 10 11 ec 84 c0 74 02 5d c3 <0f> 0b 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56
[ 833.145035] RSP: 0018:ffffa6e1c8397a10 EFLAGS: 00010246
[ 833.145038] RAX: 0000000000000000 RBX: ffff9a454f890e00 RCX: 0000000000000008
[ 833.145040] RDX: ffffffffc30d8e18 RSI: 0000000000000292 RDI: ffffffffc30d8de0
[ 833.145042] RBP: ffffa6e1c8397a10 R08: 0000000000000008 R09: ffffa6e1c83979f8
[ 833.145044] R10: 0000000000000000 R11: ffffffffc055de58 R12: ffff9a44c639f000
[ 833.145045] R13: ffff9a43f138a300 R14: 0000000000000001 R15: ffff9a44c639f000
[ 833.145047] FS: 00007feaeeb4b340(0000) GS:ffff9a45dfc00000(0000) knlGS:0000000000000000
[ 833.145050] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 833.145052] CR2: 00007feaee9cb000 CR3: 000000002d160000 CR4: 00000000000006f0
[ 833.145054] Call Trace:
[ 833.145058] drm_set_master+0x55/0x80 [drm]
[ 833.145097] drm_new_set_master+0x4d/0xa0 [drm]
[ 833.145126] drm_master_open+0x6e/0xa0 [drm]
[ 833.145155] drm_open+0x18a/0x260 [drm]
[ 833.145222] drm_stub_open+0xae/0x110 [drm]
[ 833.145255] chrdev_open+0xd3/0x1c0
[ 833.145261] ? cdev_default_release+0x20/0x20
[ 833.145264] do_dentry_open+0x156/0x370
[ 833.145268] vfs_open+0x2d/0x30
[ 833.145271] do_open.isra.0+0x224/0x4...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-restricted-modules (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.