Bug 1604231

Summary: [abrt] nvkm_vmm_iter: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 [nouveau]
Product: [Fedora] Fedora Reporter: Benjamin Hiebert <benjamin03112>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: airlied, benjamin03112, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, markus.laker, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/36066fd696acb1ee438fcc4f4748bf759d215c7a
Whiteboard: abrt_hash:c093223d82039c04d28b921716732f5fc5af8906;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-26 21:00:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: dmesg
none
dmesg from the latest instance of the crash none

Description Benjamin Hiebert 2018-07-19 21:39:09 UTC 
Additional info:
reporter:       libreport-2.9.5
BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
PGD 30af6c067 P4D 30af6c067 PUD 0 
Oops: 0000 [#1] SMP NOPTI
Modules linked in: fuse rfcomm xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun ccm nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack devlink ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep sunrpc vfat fat arc4 ath9k ath9k_common ath9k_hw edac_mce_amd snd_hda_codec_hdmi mac80211 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec kvm_amd ath3k btusb btrtl btbcm snd_hda_core snd_hwdep btintel bluetooth
 snd_seq kvm ath snd_seq_device joydev ecdh_generic snd_pcm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_timer snd cfg80211 soundcore rfkill wmi_bmof ccp sp5100_tco k10temp shpchp acpi_cpufreq pinctrl_amd i2c_piix4 gpio_amdpt gpio_generic nouveau video drm_kms_helper ttm mxm_wmi igb drm dca i2c_algo_bit crc32c_intel wmi
CPU: 4 PID: 17194 Comm: steam Not tainted 4.17.6-200.fc28.x86_64 #1
Hardware name: Micro-Star International Co., Ltd. MS-7A32/X370 GAMING PRO CARBON (MS-7A32), BIOS 1.G0 04/27/2018
RIP: 0010:gp100_vmm_pgt_mem+0xbd/0x170 [nouveau]
RSP: 0018:ffffb42e0c357840 EFLAGS: 00010212
RAX: 0000000000000178 RBX: 110000000490f001 RCX: 0000000000000010
RDX: 0000000000000000 RSI: 0000000000000178 RDI: ffff9494084fe380
RBP: 0000000000000000 R08: ffffb42e0c357a10 R09: 0000000000000000
R10: 0000000000000000 R11: ffff9493ff1dbb40 R12: 000000000000000f
R13: ffff9494353f7280 R14: 0000000000000010 R15: ffffb42e0c357a10
FS:  0000000000000000(0000) GS:ffff94943e700000(0063) knlGS:00000000f790f700
CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 0000000000000008 CR3: 000000031e726000 CR4: 00000000003406e0
Call Trace:
 nvkm_vmm_iter.constprop.11+0x2bc/0x810 [nouveau]
 ? nvkm_ioctl+0xd8/0x170 [nouveau]
 ? nvkm_vmm_map_choose+0xb0/0xb0 [nouveau]
 ? gp100_vmm_pd0_pde+0x190/0x190 [nouveau]
 nvkm_vmm_map+0x208/0x3f0 [nouveau]
 ? gp100_vmm_pd0_pde+0x190/0x190 [nouveau]
 nvkm_vram_map+0x56/0x80 [nouveau]
 nvkm_uvmm_mthd+0x5f8/0x8d0 [nouveau]
 nvkm_ioctl+0xd8/0x170 [nouveau]
 nvif_object_mthd+0x108/0x130 [nouveau]
 ? _cond_resched+0x15/0x30
 ? __kmalloc+0x19a/0x230
 nvif_vmm_map+0x81/0xb0 [nouveau]
 nouveau_mem_map+0x81/0xf0 [nouveau]
 nouveau_vma_new+0x1c6/0x1e0 [nouveau]
 nouveau_gem_object_open+0x120/0x160 [nouveau]
 drm_gem_handle_create_tail+0xc7/0x140 [drm]
 ? nouveau_gem_new+0x120/0x120 [nouveau]
 nouveau_gem_ioctl_new+0x8b/0xe0 [nouveau]
 drm_ioctl_kernel+0x5b/0xb0 [drm]
 drm_ioctl+0x1b3/0x370 [drm]
 ? nouveau_gem_new+0x120/0x120 [nouveau]
 ? selinux_file_ioctl+0x161/0x200
 nouveau_drm_ioctl+0x65/0xc0 [nouveau]
 nouveau_compat_ioctl+0x10/0x20 [nouveau]
 __ia32_compat_sys_ioctl+0x2de/0x11b0
 do_fast_syscall_32+0xa7/0x254
 entry_SYSCALL_compat_after_hwframe+0x45/0x4d
Code: 89 7f 48 42 8d 44 22 01 45 89 e6 89 44 24 0c 49 8b 7d 08 41 0f b7 45 12 48 8b 57 08 42 8d 04 f0 41 83 c6 01 48 89 c6 48 89 04 24 <4c> 8b 4a 08 89 da e8 d8 54 76 e7 49 8b 7d 08 48 8b 04 24 48 89 
RIP: gp100_vmm_pgt_mem+0xbd/0x170 [nouveau] RSP: ffffb42e0c357840
CR2: 0000000000000008
Comment 1 Benjamin Hiebert 2018-07-19 21:39:26 UTC 
Created attachment 1462583 [details]
File: dmesg
Comment 2 Laura Abbott 2018-10-01 21:25:47 UTC 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.
 
If you experience different issues, please open a new bug report for those.
Comment 3 Laura Abbott 2018-11-26 21:00:02 UTC 
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and let us know if the bug is still present on the latest kernel.

(Please note: sometimes bugs get mistakenly closed during our mass closing. If you think your bug was closed in error please reopen)
Comment 4 Markus Laker 2019-04-14 20:26:38 UTC 
Created attachment 1555093 [details]
dmesg from the latest instance of the crash
Comment 5 Markus Laker 2019-04-14 20:29:14 UTC 
The bug is still present in a fully-updated Fedora 29, running kernel version 5.0.7-200.fc29.x86_64.  I trust that this answers Laura's question of 2018-10-01.  I've attached a dmesg trace showing the crash.  Please let me know if I can do more to help you diagnose the problem.