Description of problem: Display remains blank while trying to login via the lock screen. Dec 30 12:37:23 hostname kernel: ------------[ cut here ]------------ Dec 30 12:37:23 hostname kernel: kernel BUG at drivers/gpu/drm/i915/intel_ddi.c:577! Dec 30 12:37:23 hostname kernel: invalid opcode: 0000 [#1] SMP Dec 30 12:37:23 hostname kernel: Modules linked in: vhost_net vhost macvtap macvlan fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_na Dec 30 12:37:23 hostname kernel: btbcm btintel snd_hda_intel v4l2_common bluetooth snd_hda_codec lpc_ich snd_hda_core videodev rtsx_pci_ms snd_hwdep i2c_i801 joydev memstick snd_seq snd_seq_device media snd_pcm thinkpad_acpi mei_me mei snd_timer snd tpm Dec 30 12:37:23 hostname kernel: CPU: 2 PID: 2225 Comm: Xorg Tainted: G W 4.2.6-301.fc23.x86_64 #1 Dec 30 12:37:23 hostname kernel: Hardware name: LENOVO 20BWS1KY0L/20BWS1KY0L, BIOS JBET47WW (1.12 ) 03/10/2015 Dec 30 12:37:23 hostname kernel: task: ffff880306e4bb00 ti: ffff88032cc88000 task.ti: ffff88032cc88000 Dec 30 12:37:23 hostname kernel: RIP: 0010:[<ffffffffa01e9574>] [<ffffffffa01e9574>] intel_ddi_get_crtc_encoder+0x94/0xa0 [i915] Dec 30 12:37:23 hostname kernel: RSP: 0018:ffff88032cc8bad8 EFLAGS: 00010246 Dec 30 12:37:23 hostname kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000006 Dec 30 12:37:23 hostname kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000009 Dec 30 12:37:23 hostname kernel: RBP: ffff88032cc8bae8 R08: 000000000000000a R09: 0000000000001592 Dec 30 12:37:23 hostname kernel: R10: 000000000003f150 R11: 0000000000001592 R12: ffff88032b5f0000 Dec 30 12:37:23 hostname kernel: R13: ffff88032c007000 R14: ffff88032b5f0000 R15: ffff88032b5f0000 Dec 30 12:37:23 hostname kernel: FS: 00007f1e4b774a00(0000) GS:ffff88033dc80000(0000) knlGS:0000000000000000 Dec 30 12:37:23 hostname kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 30 12:37:23 hostname kernel: CR2: 00005631389121d8 CR3: 00000000aa7f2000 CR4: 00000000003426e0 Dec 30 12:37:23 hostname kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Dec 30 12:37:23 hostname kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Dec 30 12:37:23 hostname kernel: Stack: Dec 30 12:37:23 hostname kernel: ffff88032cc8bb28 ffff88032c007000 ffff88032cc8bb28 ffffffffa01ebeae Dec 30 12:37:23 hostname kernel: ffff88032cc8bb28 0000000000000100 0000000000000001 0000000018e93492 Dec 30 12:37:23 hostname kernel: ffff8800aa3ceb50 ffff8800aa3ceb48 ffff88032cc8bba8 ffffffffa01d04a2 Dec 30 12:37:23 hostname kernel: Call Trace: Dec 30 12:37:23 hostname kernel: [<ffffffffa01ebeae>] intel_ddi_enable_pipe_clock+0x2e/0x90 [i915] Dec 30 12:37:23 hostname kernel: [<ffffffffa01d04a2>] haswell_crtc_enable+0x442/0xa90 [i915] Dec 30 12:37:23 hostname kernel: [<ffffffffa01ccd86>] __intel_set_mode+0x916/0xb60 [i915] Dec 30 12:37:23 hostname kernel: [<ffffffffa01d3c86>] intel_crtc_set_config+0x2b6/0x580 [i915] Dec 30 12:37:23 hostname kernel: [<ffffffffa0096306>] drm_mode_set_config_internal+0x66/0x100 [drm] Dec 30 12:37:23 hostname kernel: [<ffffffffa009a819>] drm_mode_setcrtc+0x3e9/0x500 [drm] Dec 30 12:37:23 hostname kernel: [<ffffffffa008b365>] drm_ioctl+0x125/0x610 [drm] Dec 30 12:37:23 hostname kernel: [<ffffffffa009a430>] ? drm_mode_setplane+0x1b0/0x1b0 [drm] Dec 30 12:37:23 hostname kernel: [<ffffffff81231445>] do_vfs_ioctl+0x295/0x470 Dec 30 12:37:23 hostname kernel: [<ffffffff813294dd>] ? selinux_file_ioctl+0x4d/0xc0 Dec 30 12:37:23 hostname kernel: [<ffffffff81231699>] SyS_ioctl+0x79/0x90 Dec 30 12:37:23 hostname kernel: [<ffffffff81233841>] ? SyS_poll+0x71/0x130 Dec 30 12:37:23 hostname kernel: [<ffffffff817793ee>] entry_SYSCALL_64_fastpath+0x12/0x71 Dec 30 12:37:23 hostname kernel: Code: c9 31 db 44 8b 87 08 04 00 00 48 c7 c2 78 18 23 a0 be 3f 02 00 00 48 c7 c7 c8 17 23 a0 41 83 c0 41 e8 81 4f eb e0 48 85 db 75 ca <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 Dec 30 12:37:23 hostname kernel: RIP [<ffffffffa01e9574>] intel_ddi_get_crtc_encoder+0x94/0xa0 [i915] Dec 30 12:37:23 hostname kernel: RSP <ffff88032cc8bad8> Dec 30 12:37:23 hostname kernel: ---[ end trace 31b5a40e6021a515 ]--- Version-Release number of selected component (if applicable): * Lenovo Thinkpad T450s * Fedora 23 * Kernel 4.2.8-300.fc23.x86_64 How reproducible: * Intermittent
H/W involved: * Serveredge KP02UDPA - 2-port USB/DisplayPort Cable KVM * Samsung S32D850 monitor * Lenovo ThinkPad Compact USB Keyboard with TrackPoint (external keyboard)
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
I have NOT experienced this issue on Fedora 24.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.