Bug 92411

Summary:	Sony VAIO Z2; boot with external HDMI monitor gives blank screen
Product:	Drivers	Reporter:	John Hughes (john)
Component:	Video(DRI - Intel)	Assignee:	intel-gfx-bugs (intel-gfx-bugs)
Status:	RESOLVED CODE_FIX
Severity:	normal	CC:	damienrg+bug, intel-gfx-bugs
Priority:	P3
Hardware:	Intel
OS:	Linux
Kernel Version:	3.16	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	dmesg with drm.debug=14 dmesg with drm.debug=14 from drm-intel-nightly build complete dmesg output with drm.debug=14, kernel 3.19 complete dmesg output with drm.debug=14, kernel 3.19 drm-nightly kernel.log with drm.debug=14 kernel.log with drm.debug=14

Description John Hughes 2015-01-31 11:38:45 UTC

For some time, at least since 3.16, and all the way up to 3.19-rc6, booting my laptop with an external display (connected via HDMI) gives me a grey screen on the external display and a black screen on the laptop display.

ssh'ing in to the laptop shows a few

 [drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up 

and

[drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe B stuck
[drm:intel_pipe_update_start [i915]] *ERROR* Potential atomic update failure on pipe B

I can sometimes plug in the external monitor after boot and login (gdm3), but attempts to change the monitor configuration often give me errors like:

[   71.526433] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
[  215.916411] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
[  216.129349] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
[  216.137659] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
[  216.145879] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
[  216.154062] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
[  216.162219] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
[  216.170341] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
[  216.170520] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting
[  216.201028] [drm:cpt_verify_modeset] *ERROR* mode set failed: pipe A stuck
[  296.173419] ------------[ cut here ]------------
[  296.173498] WARNING: CPU: 2 PID: 1341 at /build/linux-CMiYW9/linux-3.16.7-ckt2/drivers/gpu/drm/i915/intel_display.c:3324 intel_crtc_wait_for_pending_flips+0x165/0x170 [i915]()
[  296.173503] Modules linked in: binfmt_misc bnep cpufreq_stats cpufreq_powersave cpufreq_userspace cpufreq_conservative qmi_wwan cdc_wdm usbnet joydev tpm_infineon qcserial option usb_wwan usbserial arc4 iTCO_wdt iTCO_vendor_support uvcvideo ecb iwldvm x86_pkg_temp_thermal videobuf2_vmalloc videobuf2_memops snd_hda_codec_hdmi intel_powerclamp mac80211 intel_rapl videobuf2_core coretemp v4l2_common snd_hda_codec_realtek kvm_intel videodev snd_hda_codec_generic kvm media psmouse pcspkr serio_raw btusb iwlwifi bluetooth 6lowpan_iphc rtsx_pci_ms i2c_i801 memstick snd_hda_intel snd_hda_controller cfg80211 snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss sony_laptop snd_pcm rfkill snd_timer battery tpm_tis snd tpm evdev soundcore processor ac mei_me shpchp mei lpc_ich loop fuse parport_pc ppdev lp parport
[  296.173593]  autofs4 ext4 crc16 mbcache jbd2 sha256_ssse3 sha256_generic algif_skcipher af_alg dm_crypt dm_mod raid0 md_mod sg sd_mod crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel rtsx_pci_sdmmc mmc_core aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci libahci libata scsi_mod i915 ehci_pci i2c_algo_bit xhci_hcd ehci_hcd drm_kms_helper r8169 mii drm rtsx_pci mfd_core usbcore i2c_core usb_common thermal button video thermal_sys
[  296.173662] CPU: 2 PID: 1341 Comm: Xorg Not tainted 3.16.0-4-amd64 #1 Debian 3.16.7-ckt2-1
[  296.173666] Hardware name: Sony Corporation VPCZ22AGX/VAIO, BIOS R1010H5 07/28/2011
[  296.173670]  0000000000000009 ffffffff81507263 0000000000000000 ffffffff81065847
[  296.173677]  0000000000000000 ffff88025291e000 ffff880252f18210 ffff880252b2f800
[  296.173683]  ffff880252b2f800 ffffffffa021fe85 0000000000000000 ffff88009636d370
[  296.173690] Call Trace:
[  296.173703]  [<ffffffff81507263>] ? dump_stack+0x41/0x51
[  296.173713]  [<ffffffff81065847>] ? warn_slowpath_common+0x77/0x90
[  296.173745]  [<ffffffffa021fe85>] ? intel_crtc_wait_for_pending_flips+0x165/0x170 [i915]
[  296.173754]  [<ffffffff810a5940>] ? prepare_to_wait_event+0xf0/0xf0
[  296.173782]  [<ffffffffa0222fd0>] ? intel_crtc_disable_planes+0x30/0x1a0 [i915]
[  296.173809]  [<ffffffffa0223555>] ? ironlake_crtc_disable+0x45/0x910 [i915]
[  296.173831]  [<ffffffffa00aeb5a>] ? drm_modeset_lock+0x2a/0xd0 [drm]
[  296.173840]  [<ffffffff8150bace>] ? mutex_lock+0xe/0x2a
[  296.173868]  [<ffffffffa0224817>] ? intel_crtc_update_dpms+0x67/0x90 [i915]
[  296.173897]  [<ffffffffa0228419>] ? intel_connector_dpms+0x59/0x70 [i915]
[  296.173921]  [<ffffffffa00a5fd6>] ? drm_mode_obj_set_property_ioctl+0x396/0x3b0 [drm]
[  296.173942]  [<ffffffffa00a601e>] ? drm_mode_connector_property_set_ioctl+0x2e/0x40 [drm]
[  296.173962]  [<ffffffffa00958b7>] ? drm_ioctl+0x1c7/0x5b0 [drm]
[  296.173976]  [<ffffffff812b4c88>] ? lockref_put_or_lock+0x48/0x80
[  296.173984]  [<ffffffff811bb44f>] ? dput+0x1f/0x170
[  296.173990]  [<ffffffff811b7d2f>] ? do_vfs_ioctl+0x2cf/0x4b0
[  296.173997]  [<ffffffff8108314c>] ? task_work_run+0x9c/0xd0
[  296.174003]  [<ffffffff811b7f91>] ? SyS_ioctl+0x81/0xa0
[  296.174010]  [<ffffffff8150d5ea>] ? int_signal+0x12/0x17
[  296.174016]  [<ffffffff8150d32d>] ? system_call_fast_compare_end+0x10/0x15
[  296.174021] ---[ end trace a16743e82932155b ]---


Help?

Comment 1 Jani Nikula 2015-02-11 13:39:17 UTC

Please attach dmesg with drm.debug=14 module parameter set, from boot to reproducing the problem.

Comment 2 John Hughes 2015-02-12 08:45:48 UTC

Created attachment 166541 [details]
dmesg with drm.debug=14

Here is the dmesg output with drm.debug=14, kernel 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt4-2 (2015-01-27)

Comment 3 John Hughes 2015-02-12 08:46:33 UTC

I'll be able to try other kernels this weekend.

Comment 4 John Hughes 2015-02-14 17:04:33 UTC

Created attachment 166811 [details]
dmesg with drm.debug=14 from drm-intel-nightly build

Here is the dmesg with drm.debug=14 from a drm-intel-nightly (3.19.0) kernel

Comment 5 John Hughes 2015-02-28 14:20:28 UTC

Created attachment 168441 [details]
complete dmesg output with drm.debug=14, kernel 3.19

Comment 6 John Hughes 2015-02-28 14:22:26 UTC

Created attachment 168451 [details]
complete dmesg output with drm.debug=14, kernel 3.19 drm-nightly

The drm nighly build has another problem, even when no external display is present the laptop screen is messed up.  Should I report this as a seperate bug?

Comment 7 Damien R. 2015-08-30 09:23:55 UTC

Created attachment 186231 [details]
kernel.log with drm.debug=14

I have a similar problem. If I use only my external screen all is working. When I want to add my internal screen as a secondary screen I got a blank screen on both screen and ctrl+alt+f1 does not work.
I am using:
Linux debian 4.1.0-2-amd64 #1 SMP Debian 4.1.5-1 (2015-08-15) x86_64 GNU/Linux

Comment 8 Jani Nikula 2015-10-07 12:12:07 UTC

Right now I can only suggest to try v4.3-rc or drm-intel-nightly branch of http://cgit.freedesktop.org/drm-intel

Comment 9 John Hughes 2015-10-07 14:21:19 UTC

On 07/10/15 14:12, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=92411
>
> --- Comment #8 from Jani Nikula <jani.nikula@intel.com> ---
> Right now I can only suggest to try v4.3-rc or drm-intel-nightly branch of
> http://cgit.freedesktop.org/drm-intel
>
Ok, was planning to try that.

Comment 10 Damien R. 2015-10-10 08:32:21 UTC

I have just installed kernel 4.3-rc4 and for now I do not have the problem when I boot the system but if I change the configuration of the display (via gnome) when I am logged I got the problem. I had the same behavior with kernel 4.2.
If it is useful for you I can attach a log with drm.debug=14.

Comment 11 Jani Nikula 2015-10-13 07:31:24 UTC

(In reply to Damien R. from comment #10)
> If it is useful for you I can attach a log with drm.debug=14.

Please do, thanks.

Comment 12 Damien R. 2015-10-13 18:16:13 UTC

Created attachment 190201 [details]
kernel.log with drm.debug=14

I tested on:
Linux debian 4.3.0-rc4-amd64 #1 SMP Debian 4.3~rc4-1~exp1 (2015-10-06) x86_64 GNU/Linux
The boot was ok and I tried to turn off the external monitor by software resulting in a blank screen. Then I unplugged my external monitor from HDMI but it did not change anything.

Comment 13 Jani Nikula 2015-10-20 13:29:43 UTC

Okay, so the original problem seems to be fixed. Closing, thanks for the report.

For any other issues, like the one you also had in v4.2, please file new bugs at https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel