BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
IP: nvkm_object_unmap+0x5/0x20 [nouveau]
PGD 0 P4D 0
Oops: 0000 [#1] SMP PTI
Modules linked in: rfcomm fuse nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ccm 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 bnep sunrpc snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel snd_hda_codec intel_powerclamp snd_hda_core coretemp kvm_intel kvm btusb arc4 iTCO_wdt btrtl btbcm irqbypass btintel snd_hwdep bluetooth crct10dif_pclmul iwldvm iTCO_vendor_support mac80211 mei_wdt iwlwifi crc32_pclmul
snd_seq snd_seq_device ghash_clmulni_intel ecdh_generic intel_cstate intel_uncore snd_pcm joydev thinkpad_acpi cfg80211 snd_timer snd rfkill wmi_bmof lpc_ich intel_ips mei_me shpchp tpm_tis tpm_tis_core tpm i2c_i801 soundcore mei acpi_cpufreq nouveau ata_generic hid_logitech_hidpp mxm_wmi i2c_algo_bit crc32c_intel drm_kms_helper firewire_ohci serio_raw ttm sdhci_pci sdhci pata_acpi drm e1000e mmc_core hid_logitech_dj firewire_core crc_itu_t ptp pps_core video wmi
CPU: 0 PID: 2601 Comm: gsd-wacom Not tainted 4.15.15-300.fc27.x86_64 #1
Hardware name: LENOVO 2537CTO/2537CTO, BIOS 6IET85WW (1.45 ) 02/14/2013
RIP: 0010:nvkm_object_unmap+0x5/0x20 [nouveau]
RSP: 0018:ffffbb6f45ea7c98 EFLAGS: 00010282
RAX: ffffffffc039f400 RBX: ffff9cfaa1487918 RCX: 0000000000000018
RDX: ffffffffc02bd9e0 RSI: ffff9cfaa1487938 RDI: 0000000000000000
RBP: ffff9cfaa1487908 R08: 00000000000250c0 R09: ffffffffc02baca3
R10: fffff63a480799c0 R11: ffffffff8695b1ed R12: ffff9cfaa1487938
R13: 00000020b6597854 R14: ffff9cfa68fa0020 R15: 0000000000000020
FS: 00007f0a6bdcef00(0000) GS:ffff9cfabbc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000223984000 CR4: 00000000000006f0
? nvkm_fifo_chan_dtor+0x100/0x100 [nouveau]
? nvkm_object_new_+0x60/0x60 [nouveau]
RSP: 002b:00007ffc8ca537f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000038 RCX: 00007f0a6810f0f7
RDX: 000055b459664b00 RSI: 00000000c0386447 RDI: 0000000000000006
RBP: 000055b459664b00 R08: 000055b45965bb80 R09: 000055b45965e530
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000c0386447
R13: 0000000000000006 R14: 000055b459664b38 R15: 0000000000000000
Code: ff c3 0f 1f 40 00 66 66 66 66 90 48 8b 07 48 8b 40 28 48 85 c0 74 05 e9 6a 5f 94 c5 b8 ed ff ff ff c3 0f 1f 40 00 66 66 66 66 90 <48> 8b 07 48 8b 40 30 48 85 c0 74 05 e9 4a 5f 94 c5 b8 ed ff ff
RIP: nvkm_object_unmap+0x5/0x20 [nouveau] RSP: ffffbb6f45ea7c98
Created attachment 1421499 [details]
I see the same behaviour and stack trace with all Fedora kernels > 4.14. Computer is not bootable.
Created attachment 1429514 [details]
dmesg on macbook 7.1
Bisected to commit:
commit fd542a3e525c9f7a7de186cb24208c035bcea2d1 (HEAD, refs/bisect/bad)
Author: Ben Skeggs <email@example.com>
Date: Wed Nov 1 03:56:19 2017 +1000
drm/nouveau/mmu/nv50,g84: implement new vmm backend
With that commit screen goes blank, but I don't get the above call trace. However, commits after do not work either.
Any updates on this bug? Situation is still the same with kernel 4.16.11.
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.
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 27 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.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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
Thank you for reporting this bug and we are sorry it could not be fixed.