Bug 82687 - 4400: vbetool dpms on kills the video
Summary: 4400: vbetool dpms on kills the video
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-15 23:00 UTC by Konstantin Sobolev
Modified: 2014-08-16 06:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Konstantin Sobolev 2014-08-15 23:00:46 UTC
Hi. Having a problem with my laptop resuming video after S3 iff the screen was in dpms off mode on suspending: screen blinks with my desktop contents and immediately turns black with backlight on.

I think I managed to take hibernation out of the picture by playing with vbetool.

'vbetool dpms off' turns backlight off as it should
'vbetool dpms on' turns backlight on, but screen still stays black.

'vbetool dpms on' turns screen black even without doing 'dpms off' first.
There's no way to restore from this state other than a reboot.

'xset dpms force off/on' works fine, but doesn't recover the screen after 'vbetool dpms on'

This is on Lenovo T440.

00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b)
        Subsystem: Lenovo Device [17aa:220c]
        Kernel driver in use: i915

Kernel: 3.14.4

Here's what I'm seeing in dmesg:

[  425.680929] [drm:intel_pipe_config_compare] *ERROR* mismatch in dp_m_n.gmch_m (expected 4026531, found 8053063)
[  425.680935] ------------[ cut here ]------------
[  425.680950] WARNING: CPU: 1 PID: 5801 at drivers/gpu/drm/i915/intel_display.c:9530 check_crtc_state+0x6df/0xcb0()
[  425.680952] pipe state doesn't match!
[  425.680955] Modules linked in: iwlmvm x86_pkg_temp_thermal iwlwifi tpm_tis tpm
[  425.680970] CPU: 1 PID: 5801 Comm: X Not tainted 3.14.4-ck #8
[  425.680973] Hardware name: LENOVO 20AQ005TUS/20AQ005TUS, BIOS GJET72WW (2.22 ) 02/21/2014
[  425.680976]  0000000000000009 ffff88030c17b908 ffffffff8192114c 0000000000000007
[  425.680982]  ffff88030c17b958 ffff88030c17b948 ffffffff810752d7 ffff88030c17b950
[  425.680988]  ffff88030fec56d8 0000000000000001 ffff88030fed5800 ffff88030fec5000
[  425.680993] Call Trace:
[  425.681005]  [<ffffffff8192114c>] dump_stack+0x46/0x58
[  425.681014]  [<ffffffff810752d7>] warn_slowpath_common+0x87/0xb0
[  425.681021]  [<ffffffff810753a1>] warn_slowpath_fmt+0x41/0x50
[  425.681030]  [<ffffffff8148e0f2>] ? intel_ddi_get_config+0x102/0x190
[  425.681036]  [<ffffffff8147522f>] check_crtc_state+0x6df/0xcb0
[  425.681048]  [<ffffffff8117f4b0>] ? __pollwait+0xf0/0xf0
[  425.681053]  [<ffffffff814830f5>] intel_modeset_check_state+0x2a5/0x760
[  425.681059]  [<ffffffff8117f4b0>] ? __pollwait+0xf0/0xf0
[  425.681064]  [<ffffffff81484131>] intel_connector_dpms+0x61/0x70
[  425.681070]  [<ffffffff8143e658>] drm_mode_obj_set_property_ioctl+0x328/0x340
[  425.681075]  [<ffffffff8143e69b>] drm_mode_connector_property_set_ioctl+0x2b/0x30
[  425.681085]  [<ffffffff8142ebd9>] drm_ioctl+0x509/0x640
[  425.681090]  [<ffffffff8143e670>] ? drm_mode_obj_set_property_ioctl+0x340/0x340
[  425.681097]  [<ffffffff8100ce95>] ? __restore_xstate_sig+0x95/0x4e0
[  425.681104]  [<ffffffff8117e60e>] do_vfs_ioctl+0x7e/0x500
[  425.681114]  [<ffffffff813085df>] ? file_has_perm+0x8f/0xa0
[  425.681120]  [<ffffffff8117eb21>] SyS_ioctl+0x91/0xb0
[  425.681129]  [<ffffffff81932b62>] system_call_fastpath+0x16/0x1b
[  425.681133] ---[ end trace 5e855a20761ded50 ]---
[  478.805303] ------------[ cut here ]------------
[  478.805327] WARNING: CPU: 0 PID: 5801 at drivers/gpu/drm/i915/intel_dp.c:323 intel_dp_check_edp+0x75/0xe0()
[  478.805331] eDP powered off while attempting aux channel communication.
[  478.805334] Modules linked in: iwlmvm x86_pkg_temp_thermal iwlwifi tpm_tis tpm
[  478.805351] CPU: 0 PID: 5801 Comm: X Tainted: G        W    3.14.4-ck #8
[  478.805355] Hardware name: LENOVO 20AQ005TUS/20AQ005TUS, BIOS GJET72WW (2.22 ) 02/21/2014
[  478.805359]  0000000000000009 ffff88030c17bae8 ffffffff8192114c 0000000000000007
[  478.805366]  ffff88030c17bb38 ffff88030c17bb28 ffffffff810752d7 ffff88030c17bb90
[  478.805372]  ffff88030f7030c8 ffff88030f750000 ffff88030c17bc24 0000000000000001
[  478.805378] Call Trace:
[  478.805392]  [<ffffffff8192114c>] dump_stack+0x46/0x58
[  478.805404]  [<ffffffff810752d7>] warn_slowpath_common+0x87/0xb0
[  478.805411]  [<ffffffff810753a1>] warn_slowpath_fmt+0x41/0x50
[  478.805418]  [<ffffffff81491f55>] intel_dp_check_edp+0x75/0xe0
[  478.805426]  [<ffffffff81493527>] intel_dp_aux_native_write+0x37/0x120
[  478.805435]  [<ffffffff814b80a8>] ? gen6_read32+0x58/0x120
[  478.805442]  [<ffffffff81493629>] intel_dp_aux_native_write_1+0x19/0x20
[  478.805449]  [<ffffffff81495107>] intel_dp_sink_dpms+0x57/0x80
[  478.805457]  [<ffffffff8148e41c>] intel_ddi_post_disable+0xdc/0x150
[  478.805470]  [<ffffffff8147f728>] haswell_crtc_disable+0x158/0x320
[  478.805478]  [<ffffffff8147fc9f>] intel_crtc_update_dpms+0x6f/0xa0
[  478.805484]  [<ffffffff81484111>] intel_connector_dpms+0x41/0x70
[  478.805491]  [<ffffffff8143e658>] drm_mode_obj_set_property_ioctl+0x328/0x340
[  478.805497]  [<ffffffff8143e69b>] drm_mode_connector_property_set_ioctl+0x2b/0x30
[  478.805509]  [<ffffffff8142ebd9>] drm_ioctl+0x509/0x640
[  478.805515]  [<ffffffff8143e670>] ? drm_mode_obj_set_property_ioctl+0x340/0x340
[  478.805526]  [<ffffffff81372758>] ? lockref_put_or_lock+0x58/0x80
[  478.805537]  [<ffffffff8117e60e>] do_vfs_ioctl+0x7e/0x500
[  478.805548]  [<ffffffff813085df>] ? file_has_perm+0x8f/0xa0
[  478.805557]  [<ffffffff8116de99>] ? ____fput+0x9/0x10
[  478.805564]  [<ffffffff8117eb21>] SyS_ioctl+0x91/0xb0
[  478.805575]  [<ffffffff81932b62>] system_call_fastpath+0x16/0x1b
[  478.805580] ---[ end trace 5e855a20761ded51 ]---
Comment 1 Chris Wilson 2014-08-16 06:43:30 UTC
Don't use vbetool since it messes around without the driver knowledge and so unsurprisingly breaks things. If you want to investigate why the screen is turned black after resume, please capture a drm.debug=6 dmesg and a full-debug Xorg.0.log.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.