Bug 91168 - [Braswell HDMI] No HDMI signal output and kernel crash(Call Trace)
Summary: [Braswell HDMI] No HDMI signal output and kernel crash(Call Trace)
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-01 03:13 UTC by samuelchueh
Modified: 2017-07-24 22:46 UTC (History)
1 user (show)

See Also:
i915 platform: BSW/CHT
i915 features: display/HDMI


Attachments

Description samuelchueh 2015-07-01 03:13:39 UTC
Plug-in HDMI connecter after Ubuntu linux boot. No HDMI signal output on monitor and kernel Call Trace. kernel call trace message as below,


[ 1399.810589] ------------[ cut here ]------------
[ 1399.815507] WARNING: CPU: 1 PID: 32721 at 
/source/linux-4.1.0/drivers/gpu/drm/i915/intel_display.c:1846 vlv_wait_port_ready+0x105/0x111 [i915]()
[ 1399.831828] timed out waiting for port D ready: 0x0000000f
[ 1399.837510] Modules linked in: snd_seq_midi snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_midi_event snd_seq snd_seq_device cryptodev(O) iptable_filter ip_tables x_tables iscsi_scst(O) scst_vdisk(O) scst(O) snd_hda_codec_hdmi i915 drm_kms_helper drm snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_timer snd snd_hda_core isofs udf crc_itu_t sr_mod cdrom quota_v2 quota_tree dm_crypt [last unloaded: bluetooth]
[ 1399.878383] CPU: 1 PID: 32721 Comm: X Tainted: G           O    4.1.0 #1
[ 1399.885393] Hardware name: Insyde AS61xx/Type2 - Board Product Name, BIOS V1.09 06/03/2015
[ 1399.894076]  0000000000000736 ffff880177783948 ffffffff8151fa98 0000000000002df3
[ 1399.901914]  ffff880177783998 ffff880177783988 ffffffff810531f1 ffffffff810966a7
[ 1399.909705]  ffffffffa01a71d5 ffff880178810000 000000000000000f 0000000000186240
[ 1399.917499] Call Trace:
[ 1399.920032]  [<ffffffff8151fa98>] dump_stack+0x45/0x57
[ 1399.925396]  [<ffffffff810531f1>] warn_slowpath_common+0x97/0xb1
[ 1399.931606]  [<ffffffff810966a7>] ? update_rmtp+0x61/0x61
[ 1399.937279]  [<ffffffffa01a71d5>] ? vlv_wait_port_ready+0x105/0x111 [i915]
[ 1399.944423]  [<ffffffff8105329f>] warn_slowpath_fmt+0x41/0x43
[ 1399.950418]  [<ffffffffa01979d0>] ? chv_read32+0x146/0x151 [i915]
[ 1399.956793]  [<ffffffffa01a71d5>] vlv_wait_port_ready+0x105/0x111 [i915]
[ 1399.963779]  [<ffffffffa01d20f1>] chv_hdmi_pre_enable+0x3df/0x3ee [i915]
[ 1399.970754]  [<ffffffffa01ac797>] valleyview_crtc_enable+0x1c5/0x254 [i915]
[ 1399.978001]  [<ffffffffa01abe1a>] __intel_set_mode+0x917/0x9b7 [i915]
[ 1399.984761]  [<ffffffffa00e370e>] ? drm_atomic_get_crtc_state+0x19/0xaa [drm]
[ 1399.992258]  [<ffffffffa01b1c2c>] intel_crtc_set_config+0x898/0xc09 [i915]
[ 1399.999373]  [<ffffffffa00d5f64>] ? _object_find+0x7d/0x9e [drm]
[ 1400.005640]  [<ffffffffa00d6b84>] drm_mode_set_config_internal+0x54/0xe0 [drm]
[ 1400.013167]  [<ffffffffa00daa2d>] drm_mode_setcrtc+0x47f/0x4d7 [drm]
[ 1400.019726]  [<ffffffffa00ce93c>] drm_ioctl+0x28c/0x3bf [drm]
[ 1400.025697]  [<ffffffffa00da5ae>] ? drm_mode_setplane+0x186/0x186 [drm]
[ 1400.032577]  [<ffffffff81123d38>] do_vfs_ioctl+0x419/0x45a
[ 1400.038263]  [<ffffffff811159d9>] ? fdput.isra.18+0xf/0x11
[ 1400.043963]  [<ffffffff81115ae4>] ? fdput_pos.isra.22+0x29/0x30
[ 1400.050100]  [<ffffffff81123db9>] SyS_ioctl+0x40/0x5f
[ 1400.055370]  [<ffffffff81524957>] system_call_fastpath+0x12/0x6a
[ 1400.061616] ---[ end trace 301c639bb16a9228 ]---
Comment 1 samuelchueh 2015-07-17 06:57:08 UTC
Re-test driver version as below, this issue not fix. 

drm/i915 version : drm-intel-next-2015-07-03
Kernel Version: 4.1
Mesa - 10.6.0
xf86-video-intel - 2.99.917
Libdrm - 2.4.60
Libva - 1.6.0
vaapi intel-driver - 1.6.0
Cairo - 1.14.2
Xorg Xserver - 1.17.1
Comment 2 Jani Nikula 2016-04-21 12:39:16 UTC
Presumed fixed by now, closing. Please reopen if the problem persists with latest kernels.


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.