Bug 1385380

Summary: [abrt] BUG: unable to handle kernel NULL pointer dereference at 0000000000000058
Product: [Fedora] Fedora Reporter: Thomas Schmitz <agrar.pfurtz>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: airlied, ajax, bskeggs, kernel-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fe1082b301b73aef8499bffcac3399799bc6d33f
Whiteboard: abrt_hash:0ca288190ec0f03e44e632c18f02cee4bd0e6efa;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 19:26:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dmesg none

Description Thomas Schmitz 2016-10-16 15:19:26 UTC
Description of problem:
gpu passthrough using vfio

Additional info:
reporter:       libreport-2.7.2
BUG: unable to handle kernel NULL pointer dereference at 0000000000000058
IP: [<ffffffff817cc942>] mutex_lock+0x12/0x30
PGD 0 
Oops: 0002 [#1] SMP 
Modules linked in: vfio_pci vfio_iommu_type1 vfio_virqfd vfio vhost_net vhost macvtap macvlan rfcomm ccm fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun ip6t_REJECT nf_reject_ipv6 xt_conntrack ip6t_rpfilter ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_raw ip6table_mangle ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_raw iptable_mangle iptable_security ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep arc4 iwlmvm iTCO_wdt iTCO_vendor_support snd_seq_midi snd_seq_midi_event mac80211 intel_rapl x86_pkg_temp_thermal coretemp kvm_intel btusb snd_ice1712 iwlwifi kvm snd_hda_codec_hdmi snd_cs8427 snd_i2c snd_hda_codec_realtek snd_soc_rt5640
 snd_ice17xx_ak4xxx snd_ak4xxx_adda snd_hda_codec_generic snd_soc_rl6231 snd_mpu401_uart btrtl snd_rawmidi btbcm snd_soc_ssm4567 btintel cfg80211 snd_soc_core snd_ac97_codec bluetooth snd_hda_intel snd_hda_codec snd_compress snd_pcm_dmaengine ac97_bus irqbypass joydev snd_hda_core snd_seq snd_hwdep rfkill snd_seq_device mei_me i2c_i801 shpchp mei lpc_ich snd_pcm snd_timer snd elan_i2c snd_soc_sst_acpi snd_soc_sst_match soundcore i2c_designware_platform i2c_designware_core tpm_infineon tpm_tis tpm spi_pxa2xx_platform acpi_pad nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt nouveau i915 mxm_wmi crct10dif_pclmul ttm crc32_pclmul crc32c_intel i2c_algo_bit ghash_clmulni_intel drm_kms_helper serio_raw drm alx mdio sdhci_acpi sdhci mmc_core wmi video fjes i2c_hid
CPU: 1 PID: 1528 Comm: libvirtd Not tainted 4.5.5-300.fc24.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. Z97X-Gaming 3/Z97X-Gaming 3, BIOS F7 09/18/2015
task: ffff880809125b80 ti: ffff8800becb0000 task.ti: ffff8800becb0000
RIP: 0010:[<ffffffff817cc942>]  [<ffffffff817cc942>] mutex_lock+0x12/0x30
RSP: 0018:ffff8800becb3960  EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000058 RCX: 0000000000000320
RDX: 0000000080000000 RSI: 0000000000000296 RDI: 0000000000000058
RBP: ffff8800becb3968 R08: 0000000000000300 R09: ffffc9000392c000
R10: 0000000000000000 R11: ffffc9000392c000 R12: ffff8807f59b1000
R13: ffff880807f711e8 R14: ffff88080686fa00 R15: ffff8800becb3b48
FS:  00007f63bf65f700(0000) GS:ffff88082fa40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000058 CR3: 00000007f875e000 CR4: 00000000001406e0
Stack:
 0000000000000058 ffff8800becb39e8 ffffffffa0397bdc ffff8800baf9cf78
 ffff8800baf9cf40 0000000000300000 ffff8800bef85c00 ffff8800baf9cf00
 00000000a0343947 0000000000000001 80000001a033d4dd 00000000b16ae370
Call Trace:
 [<ffffffffa0397bdc>] nouveau_bo_move_m2mf+0x11c/0x1c0 [nouveau]
 [<ffffffffa039801c>] nouveau_bo_move+0x9c/0x430 [nouveau]
 [<ffffffffa0124d2c>] ttm_bo_handle_move_mem+0x28c/0x5d0 [ttm]
 [<ffffffffa01251c1>] ttm_bo_evict+0x151/0x330 [ttm]
 [<ffffffffa012553a>] ttm_mem_evict_first+0x19a/0x220 [ttm]
 [<ffffffffa01259ea>] ttm_bo_force_list_clean+0x6a/0xb0 [ttm]
 [<ffffffffa0125a7b>] ttm_bo_clean_mm+0x4b/0x90 [ttm]
 [<ffffffffa039df73>] nouveau_ttm_fini+0x23/0x60 [nouveau]
 [<ffffffffa0394623>] nouveau_drm_unload+0x63/0xb0 [nouveau]
 [<ffffffffa0095319>] drm_dev_unregister+0x29/0xb0 [drm]
 [<ffffffffa0095a33>] drm_put_dev+0x23/0x60 [drm]
 [<ffffffffa0395557>] nouveau_drm_device_remove+0x47/0x70 [nouveau]
 [<ffffffffa0395595>] nouveau_drm_remove+0x15/0x20 [nouveau]
 [<ffffffff81421459>] pci_device_remove+0x39/0xc0
 [<ffffffff815130d1>] __device_release_driver+0xa1/0x160
 [<ffffffff815131b3>] device_release_driver+0x23/0x30
 [<ffffffff8151194d>] unbind_store+0x10d/0x160
 [<ffffffff81510ea5>] drv_attr_store+0x25/0x30
 [<ffffffff812c5e87>] sysfs_kf_write+0x37/0x40
 [<ffffffff812c544c>] kernfs_fop_write+0x11c/0x170
 [<ffffffff81241ba7>] __vfs_write+0x37/0x120
 [<ffffffff8135d215>] ? selinux_file_permission+0xc5/0x100
 [<ffffffff81352bad>] ? security_file_permission+0x3d/0xc0
 [<ffffffff810eefb2>] ? percpu_down_read+0x12/0x50
 [<ffffffff812424b2>] vfs_write+0xa2/0x190
 [<ffffffff812433e5>] SyS_write+0x55/0xc0
 [<ffffffff817cecee>] entry_SYSCALL_64_fastpath+0x12/0x6d
Code: 83 f8 01 0f 85 6d ff ff ff eb db e8 b9 93 8d ff 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb e8 2e e4 ff ff <f0> ff 0b 79 08 48 89 df e8 c1 fe ff ff 65 48 8b 04 25 c0 bc 00 
RIP  [<ffffffff817cc942>] mutex_lock+0x12/0x30
 RSP <ffff8800becb3960>

Comment 1 Thomas Schmitz 2016-10-16 15:19:37 UTC
Created attachment 1210987 [details]
File: dmesg

Comment 2 Fedora End Of Life 2017-07-25 23:30:10 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-08-08 19:26:59 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.