Bug 1275258
Summary: | Displays stop working after lock screen | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomas Mlcoch <tmlcoch> |
Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 22 | CC: | ajax, dkopecek, lprosek, rsroka, xgl-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-19 18:20:36 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tomas Mlcoch
2015-10-26 11:58:19 UTC
I'm experiencing the same or very similar issue. I'm running on i3 with 2 monitors connected to a dock station (Lenovo T540p). One of the monitors usually doesn't come up after it goes to suspend/standby mode. It can be revived by manually running xrandr to turn it off and on again. Not sure whether it's related, but I'm seeing these backtraces in dmesg: kernel: ---[ end trace 211d4aecc3d54de3 ]--- kernel: [<ffffffff81778bee>] entry_SYSCALL_64_fastpath+0x12/0x71 kernel: [<ffffffff810acf1e>] ? SyS_rt_sigprocmask+0x8e/0xc0 kernel: [<ffffffff81231509>] SyS_ioctl+0x79/0x90 kernel: [<ffffffff8132930d>] ? selinux_file_ioctl+0x4d/0xc0 kernel: [<ffffffff812312b5>] do_vfs_ioctl+0x295/0x470 kernel: [<ffffffffa008a420>] ? drm_mode_setplane+0x1b0/0x1b0 [drm] kernel: [<ffffffffa007b365>] drm_ioctl+0x125/0x610 [drm] kernel: [<ffffffffa008a809>] drm_mode_setcrtc+0x3e9/0x500 [drm] kernel: [<ffffffffa0086326>] drm_mode_set_config_internal+0x66/0x100 [drm] kernel: [<ffffffffa0156ee6>] intel_crtc_set_config+0x2b6/0x580 [i915] kernel: [<ffffffffa015154f>] ? intel_modeset_compute_config+0x3af/0xb60 [i915] kernel: [<ffffffffa014fc48>] __intel_set_mode+0x568/0xb60 [i915] kernel: [<ffffffffa0141206>] haswell_crtc_compute_clock+0x16/0x40 [i915] kernel: [<ffffffff81202ee8>] ? __kmalloc_track_caller+0x1a8/0x250 kernel: [<ffffffffa014558b>] ? intel_check_primary_plane+0xdb/0x330 [i915] kernel: [<ffffffffa0095ee2>] ? drm_atomic_get_crtc_state+0x32/0xd0 [drm] kernel: [<ffffffffa016dd44>] intel_ddi_pll_select+0x44/0xf00 [i915] kernel: [<ffffffffa016d72d>] intel_ddi_get_crtc_new_encoder+0x8d/0xa0 [i915] kernel: [<ffffffff8109e535>] warn_slowpath_fmt+0x55/0x70 kernel: [<ffffffff8109e4a6>] warn_slowpath_common+0x86/0xc0 kernel: [<ffffffff8177220a>] dump_stack+0x45/0x57 kernel: Call Trace: kernel: 0000000000000000 ffff880409188800 ffff880036e17000 ffff8800b6fe4000 kernel: 0000000000000000 ffff8804099279d0 ffff8804099279b8 ffffffff8109e4a6 kernel: 0000000000000000 00000000cd0ba6ac ffff880409927978 ffffffff8177220a kernel: Hardware name: LENOVO 20BFS0W50C/20BFS0W50C, BIOS GMET70WW (2.18 ) 03/05/2015 kernel: CPU: 0 PID: 1602 Comm: Xorg Not tainted 4.2.3-200.fc22.x86_64 #1 kernel: coretemp videodev iwlwifi kvm_intel thinkpad_acpi cfg80211 kvm mei_me snd_timer media lpc_ich e1000e snd mei tpm_tis tpm rfkill ie31200_edac edac_core soundcore ptp i2c_i801 wmi shpc kernel: Modules linked in: md4 nls_utf8 cifs dns_resolver fscache xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun ccm ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_nat e kernel: 2 encoders on crtc for pipe A kernel: WARNING: CPU: 0 PID: 1602 at drivers/gpu/drm/i915/intel_ddi.c:603 intel_ddi_get_crtc_new_encoder+0x8d/0xa0 [i915]() kernel: ------------[ cut here ]------------ Versions: kernel-4.2.3-200.fc22.x86_64 xorg-x11-drv-intel-2.99.917-15.20150729.fc22.x86_64 I would like mention that this issue appeared about week or two ago. Before that everything worked properly. So this is probably some kind of regression. Daniel's intermittent issue could be related to bug 1179924. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. |