Ubuntu

Display goes black, apparantly due to a bug in the i915 intel graphics driver

Asked by Mohammad Mehdi Salem Naraghi

A few days ago I started having a weird problem, where all attached displays (including the internal display) on my x280 lenovo notebook go black after a few minutes of inactivity (probably because some powersaving mechanism kicks in and tries to deactivate the display to preserve power). In the kernel logs I see the associated backtrace:

--------------------------- journalctl output ---------------------------
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000245
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: IP: intel_ddi_post_disable+0x54/0x170 [i915]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: PGD 0 P4D 0
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: Oops: 0000 [#1] SMP PTI
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ccm aufs overlay bnep binfmt_misc nls_iso8859_1 arc4 snd_usb_audio snd_usbmidi_lib joydev cdc_mbim cdc_wdm cdc_ncm uvcvideo usbnet mii btusb cdc_acm btrtl btbcm btintel bluetooth snd_hda_codec_hdmi ecdh_generic snd_soc_skl snd_soc_skl_ipc intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_ext_core snd_soc_sst_dsp iwlmvm snd_hda_codec_realtek snd_soc_sst_ipc snd_soc_acpi snd_hda_codec_generic kvm_intel mac80211 kvm snd_soc_core irqbypass snd_compress intel_cstate ac97_bus snd_pcm_dmaengine
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: intel_rapl_perf snd_seq_midi snd_seq_midi_event iwlwifi snd_rawmidi rmi_smbus snd_hda_intel input_leds rmi_core snd_hda_codec videobuf2_vmalloc cfg80211 serio_raw videobuf2_memops snd_hda_core videobuf2_v4l2 snd_hwdep snd_seq videobuf2_core snd_pcm videodev ucsi_acpi thinkpad_acpi mei_me snd_seq_device wmi_bmof media nvram processor_thermal_device typec_ucsi mei shpchp intel_pch_thermal intel_wmi_thunderbolt intel_soc_dts_iosf typec snd_timer snd int3403_thermal soundcore int340x_thermal_zone mac_hid acpi_pad int3400_thermal acpi_thermal_rel sch_fq_codel nfsd auth_rpcgss nfs_acl lockd coretemp grace parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul uas ghash_clmulni_intel pcbc usb_storage i915 aesni_intel aes_x86_64 crypto_simd i2c_algo_bit glue_helper cryptd drm_kms_helper nvme e1000e syscopyarea sysfillrect psmouse sysimgblt ptp fb_sys_fops i2c_i801 pps_core nvme_core thunderbolt drm wmi video
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: CPU: 6 PID: 1546 Comm: Xorg Tainted: G O 4.15.0-44-generic #47-Ubuntu
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: Hardware name: LENOVO 20KF001GGE/20KF001GGE, BIOS N20ET38W (1.23 ) 11/06/2018
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: RIP: 0010:intel_ddi_post_disable+0x54/0x170 [i915]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: RSP: 0018:ffffacdd0396fa60 EFLAGS: 00010297
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: RAX: 0000000000000007 RBX: ffff9cf3df46e000 RCX: ffffffffc05fe272
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9cf3df46e000
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: RBP: ffffacdd0396fa90 R08: 0000000000000007 R09: 0000000000000000
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: R10: 000000000000031e R11: 000000000000027b R12: 0000000000000000
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: R13: ffff9cf3df46e000 R14: ffff9cf3d2a20000 R15: ffff9cf3d4627800
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: FS: 00007f756b888600(0000) GS:ffff9cf3f2580000(0000) knlGS:0000000000000000
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: CR2: 0000000000000245 CR3: 000000043272a001 CR4: 00000000003606e0
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: Call Trace:
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: ? intel_dp_sink_dpms+0xbb/0xf0 [i915]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: intel_mst_post_disable_dp+0x99/0xd0 [i915]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: intel_encoders_post_disable.isra.102+0x66/0x80 [i915]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: haswell_crtc_disable+0xe8/0x150 [i915]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: intel_atomic_commit_tail+0x7ea/0xd30 [i915]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: intel_atomic_commit+0x277/0x2b0 [i915]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: drm_atomic_commit+0x51/0x60 [drm]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: drm_atomic_connector_commit_dpms+0xef/0x100 [drm]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: drm_mode_obj_set_property_ioctl+0x176/0x280 [drm]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: ? drm_mode_connector_set_obj_prop+0x80/0x80 [drm]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: drm_mode_connector_property_set_ioctl+0x3f/0x60 [drm]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: drm_ioctl_kernel+0x5f/0xb0 [drm]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: drm_ioctl+0x31b/0x3d0 [drm]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: ? drm_mode_connector_set_obj_prop+0x80/0x80 [drm]
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: ? __check_object_size+0xaf/0x1b0
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: ? _copy_to_user+0x26/0x30
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: ? _cond_resched+0x19/0x40
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: ? _cond_resched+0x19/0x40
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: do_vfs_ioctl+0xa8/0x630
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: ? __fput+0x193/0x220
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: SyS_ioctl+0x79/0x90
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: do_syscall_64+0x73/0x130
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: RIP: 0033:0x7f7568c8d5d7
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: RSP: 002b:00007fff3990d208 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: RAX: ffffffffffffffda RBX: 000055843c701f00 RCX: 00007f7568c8d5d7
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: RDX: 00007fff3990d240 RSI: 00000000c01064ab RDI: 000000000000000c
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: RBP: 00007fff3990d240 R08: 00007fff3990d230 R09: 0000000000000000
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: R10: 0000000000000030 R11: 0000000000000246 R12: 00000000c01064ab
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: R13: 000000000000000c R14: 00007f756b7ec001 R15: 00007f756b7ec000
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: Code: 0d f6 86 44 02 00 00 40 0f 85 81 00 00 00 83 f8 06 72 77 83 f8 08 76 13 83 f8 0a 75 6d 41 f6 86 60 06 00 00 40 0f 84 dd 00 00 00 <41> f6 84 24 45 02 00 00 08 4d 8d bd 00 01 00 00 74 3e 48 89 df
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: RIP: intel_ddi_post_disable+0x54/0x170 [i915] RSP: ffffacdd0396fa60
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: CR2: 0000000000000245
Jan 31 12:50:24 mehdi-ThinkPad-X280 kernel: ---[ end trace e5a6ee3ed6d0922a ]---

--------------------------- end of journalctl output ---------------------------

any ideas what may be causing this issue?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Mohammad Mehdi Salem Naraghi
Solved:
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said : 		#1

There is a bug report about display problems with the recent kernel version
Bug #1813663: External monitors does not work anymore 4.15.0-44
Maybe this is also the cause for your behavior.
Temporary workaround is using the 4.15.0-43 kernel.

Can you try booting an older kernel to verify whether this helps?

Or - hottest news - upgrade to the 4.15.0-45 version of the kernel which has been published three hours ago.

Revision history for this message
Mohammad Mehdi Salem Naraghi (momesana) said : 		#2

Hi Manfred and thanks for the hint. I did actually upgrade to 18.10 which runs on the 4.18.0-13-generic kernel and that too fixed the issue.