Description of problem: I left a Firefox and xosview and some xterm's running. I left the system alone, and came back to find the screensaver halted. Additional info: reporter: libreport-2.12.0 general protection fault: 0000 [#1] SMP PTI CPU: 7 PID: 1236 Comm: Xorg Not tainted 5.5.5-200.fc31.x86_64 #1 Hardware name: Dell Inc. XPS 13 9370/0VM1FG, BIOS 1.5.1 08/09/2018 RIP: 0010:kmem_cache_alloc+0x75/0x220 Code: 01 00 00 4c 8b 45 00 65 49 8b 50 08 65 4c 03 05 11 41 d3 52 4d 8b 20 4d 85 e4 0f 84 71 01 00 00 8b 5d 20 48 8b 7d 00 4c 01 e3 <48> 33 1b 48 33 9d 70 01 00 00 40 f6 c7 0f 0f 85 6e 01 00 00 48 8d RSP: 0018:ffffb2bf40dd3a28 EFLAGS: 00010286 RAX: 0000000000000000 RBX: c830733f2027e7ee RCX: 0000000000000000 RDX: 000000000037b36b RSI: 0000000000000cc0 RDI: 0000000000031730 RBP: ffff8925255a5180 R08: ffff8925267f1730 R09: ffff8924c8f84b50 R10: ffffdc85084cbe00 R11: ffff892520175900 R12: c830733f2027e7ee R13: 0000000000000cc0 R14: ffffffffc0767242 R15: ffff8925255a5180 FS: 00007f0abca1ef00(0000) GS:ffff8925267c0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f948f076000 CR3: 000000026a0d0004 CR4: 00000000003606e0 Call Trace: i915_active_ref+0x62/0x180 [i915] i915_vma_move_to_active+0x24/0x150 [i915] i915_gem_do_execbuffer+0xd7b/0x1900 [i915] ? check_preempt_curr+0x4a/0x90 ? __wake_up_common+0x80/0x180 ? __wake_up_common_lock+0x8a/0xc0 ? unix_stream_sendmsg+0x397/0x3d0 ? __kmalloc_node+0x1ff/0x310 i915_gem_execbuffer2_ioctl+0x1df/0x3d0 [i915] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] drm_ioctl_kernel+0xaa/0xf0 [drm] drm_ioctl+0x208/0x390 [drm] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] ? selinux_file_ioctl+0x174/0x220 do_vfs_ioctl+0x461/0x6d0 ksys_ioctl+0x5e/0x90 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x5b/0x1c0 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f0abce9938b Code: 0f 1e fa 48 8b 05 fd 9a 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 cd 9a 0c 00 f7 d8 64 89 01 48 RSP: 002b:00007ffe4346a908 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007ffe4346a950 RCX: 00007f0abce9938b RDX: 00007ffe4346a950 RSI: 0000000040406469 RDI: 0000000000000010 RBP: 0000000040406469 R08: 0000556e3cb545b0 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000556e3cb11940 R13: 0000000000000010 R14: ffffffffffffffff R15: 00007f0abc32fa68 Modules linked in: ccm rfcomm ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter cmac bnep sunrpc vfat fat snd_soc_skl snd_soc_sst_ipc snd_hda_codec_hdmi snd_soc_sst_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ath10k_pci snd_soc_core snd_hda_codec_realtek snd_compress iTCO_wdt ath10k_core mei_hdcp mei_wdt iTCO_vendor_support intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_generic dell_laptop ac97_bus coretemp ledtrig_audio kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm mac80211 snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib irqbypass dell_wmi snd_hwdep dell_smbios intel_cstate snd_rawmidi intel_uncore snd_seq dcdbas intel_rapl_perf btusb ath pcspkr uvcvideo btrtl snd_seq_device snd_pcm btbcm videobuf2_vmalloc videobuf2_memops dell_wmi_descriptor wmi_bmof intel_wmi_thunderbolt videobuf2_v4l2 btintel snd_timer videobuf2_common bluetooth snd cfg80211 i2c_i801 videodev soundcore ecdh_generic libarc4 ecc mc mei_me mei processor_thermal_device ucsi_acpi joydev typec_ucsi intel_rapl_common intel_xhci_usb_role_switch idma64 intel_soc_dts_iosf roles intel_pch_thermal typec int3400_thermal intel_hid int3403_thermal acpi_thermal_rel acpi_pad int340x_thermal_zone sparse_keymap ip_tables dm_crypt rfkill hid_logitech_hidpp i915 rtsx_pci_sdmmc hid_multitouch mmc_core crct10dif_pclmul i2c_algo_bit crc32_pclmul crc32c_intel drm_kms_helper nvme ghash_clmulni_intel r8152 drm nvme_core serio_raw hid_logitech_dj mii uas usb_storage rtsx_pci wmi i2c_hid pinctrl_sunrisepoint video pinctrl_intel fuse
Created attachment 1665507 [details] File: dmesg
Thanks for your report. The call trace looks very similar to the ones in these bug reports, although they are against 5.4 kernels: Bug 1805278 - i915: kernel NULL pointer dereference, address: 0000000000000040 appearing randomly Bug 1803372 - [abrt] i915_active_ref: BUG: kernel NULL pointer dereference, address: 0000000000000040 [i915]
*** Bug 1806767 has been marked as a duplicate of this bug. ***
This morning I hit the problem twice with kernel kernel-5.5.5-200.fc31.x86_64, which I upgraded to a day before (this means that I was running 5.5.5-200 for one whole day without hitting the problem). I no longer see this when I rebooted with kernel-5.4.20-200.fc31.x86_64, and neither did I see this before with other 5.4 kernel.
The current "stable" kernel built for Fedora is available: kernel-5.5.6-201.fc31, kernel-headers-5.5.6-200.fc31, & 1 more https://bodhi.fedoraproject.org/updates/FEDORA-2020-3cd64d683c
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are 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 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. 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 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those.
I no longer observe the problem with kernel 5.5.6-201.fc31.x86_64
Thanks for letting us know.
kernel-5.5.7-200.fc31.x86_64 exhibited this bug, or one just like it, on my box, today. I say "or one just like it" because the problem reporting tool, run after I power cycled the box, did not detect that I'd had a crash. So I don't have an details of the crash, sorry.
(In reply to Don Lindsay from comment #9) > kernel-5.5.7-200.fc31.x86_64 exhibited this bug, or one just like it, on my > box, today. Thanks for reopening this bug. This is currently in the "updates-testing" repo: kernel-5.5.8-200.fc31, kernel-headers-5.5.8-200.fc31, & 1 more https://bodhi.fedoraproject.org/updates/FEDORA-2020-d8c4450b82 > I say "or one just like it" because the problem reporting tool, run after I > power cycled the box, did not detect that I'd had a crash. So I don't have > an details of the crash, sorry. You can probably get the call trace with the journalctl "-b" option. This saves the log for the previous boot: $ journalctl -b -1 --no-hostname -k > dmesg-2.txt For a list of previous boots: $ journalctl --list-boots
Created attachment 1668371 [details] output of journalctl -b -2 --no-hostname -k (as suggested)
(In reply to Don Lindsay from comment #11) > Created attachment 1668371 [details] > output of journalctl -b -2 --no-hostname -k (as suggested) Thanks for attaching the log. It doesn't have a call trace, but it has a lot of error messages like this at the end: Mar 06 08:51:37 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=21470 end=21471) time 247 us, min 2146, max 2159, scanline start 2135, end 2168 That must be a different bug, so I suggest opening a new bug with this as the bug summary: "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A" And please attach dmesg-2.txt to that new bug.
(In reply to Don Lindsay from comment #9) ... > I say "or one just like it" because the problem reporting tool, run after I > power cycled the box, did not detect that I'd had a crash. So I don't have > an details of the crash, sorry. ABRT looks for kernel call traces in the log, but there wasn't one in that case. In contrast, there is a call trace in the first attachment. Snippet from the attached dmesg: ... [14471.621232] Call Trace: [14471.621341] i915_active_ref+0x62/0x180 [i915] ... See, also: $ pgrep -fa 'abrt-dump-journal-oops'
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-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 '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.