FWIW, I am able to get graphics on the screen now - Apparently only the hdmi port works on HSW right now - which I was unaware of.<div>This stack was a red-herring to that problem.</div><div><br></div><div>Thanks for the response.</div>
<div><br></div><div>Ben</div><div><div><br><div class="gmail_quote">On Thu, Sep 27, 2012 at 2:34 AM, Daniel Vetter <span dir="ltr"><<a href="mailto:daniel@ffwll.ch" target="_blank">daniel@ffwll.ch</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thu, Sep 27, 2012 at 06:32:06AM +0000, Wang, Xingchao wrote:<br>
> Hi Ben,<br>
><br>
> I have no idea about the resolution, maybe Paulo and Daniel know more details?<br>
<br>
</div>Oh, it's just an older assert for pre-hsw that we haven't properly<br>
disabled yet. Since this code will change quite a bit with Paulo's new<br>
way of handling ddi/fdi on haswell, we somehow never bothered with the<br>
real fix. Should be quite as soon as Paulo's patchbomb lands.<br>
-Daniel<br>
<div class="im"><br>
><br>
> Thanks<br>
> --xingchao<br>
><br>
> From: <a href="mailto:ben.guthro@gmail.com">ben.guthro@gmail.com</a> [mailto:<a href="mailto:ben.guthro@gmail.com">ben.guthro@gmail.com</a>] On Behalf Of Ben Guthro<br>
> Sent: Wednesday, September 26, 2012 4:43 AM<br>
> To: Wang, Xingchao<br>
> Cc: <a href="mailto:intel-gfx@lists.freedesktop.org">intel-gfx@lists.freedesktop.org</a>; Zanoni, Paulo R; Fu, Michael; Wu, Fengguang<br>
> Subject: Re: [Intel-gfx] assertion on intel_disable_transcoder<br>
><br>
> I am seeing this same trace (and no video) on multiple Haswell SDP's, with 3.6-rc7 (and earlier kernels)<br>
><br>
> Was there ever a resolution on this?<br>
><br>
><br>
><br>
</div><div><div class="h5">> On Wed, Aug 15, 2012 at 3:24 AM, Wang, Xingchao <<a href="mailto:xingchao.wang@intel.com">xingchao.wang@intel.com</a><mailto:<a href="mailto:xingchao.wang@intel.com">xingchao.wang@intel.com</a>>> wrote:<br>
> Hi,<br>
><br>
> Some update related to this warning.<br>
> Ironlake_crtc_dpms() will enable/disable crtc which pipe was enabled/disabled there.<br>
> Ironlake_crtc_dpms(DRM_MODE_DPMS_OFF) was called before the warning and crtc was disabled, that causes intel_wait_for_vblank() timeout and some assertions.<br>
><br>
> I think it's a bug but I have no clue where/when to enable crtc again.<br>
><br>
> Here's part of dmesg before the warning and the message showing dpms off.<br>
><br>
> [ 19.332220] [drm:intel_lvds_init], LVDS is not present in VBT<br>
> [ 19.332261] [drm:intel_crt_init], pch crt adpa set to 0x80f40000<br>
> [ 19.332295] [drm:intel_dp_i2c_init], i2c_init DPDDC-B<br>
> [ 19.334807] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f<br>
> [ 19.334809] [drm:intel_dp_i2c_aux_ch], aux_ch failed -110<br>
> [ 19.337318] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x5145003f<br>
> [ 19.337319] [drm:intel_dp_i2c_aux_ch], aux_ch failed -110<br>
> [ 19.337432] [drm:ironlake_crtc_dpms], crtc 0/0 dpms off<br>
> [ 19.337436] [drm:i915_get_vblank_timestamp], crtc 0 is disabled<br>
> [ 19.351826] ------------[ cut here ]------------<br>
> [ 19.351848] WARNING: at drivers/gpu/drm/i915/intel_display.c:1118 assert_fdi_tx+0x87/0x90 [i915]()<br>
> [ 19.351849] Hardware name: Shark Bay Client platform<br>
> [ 19.351850] FDI TX state assertion failure (expected off, current on)<br>
> [ 19.351867] Modules linked in: i915(+) kvm snd_hda_codec_realtek snd_hda_codec_hdmi drm_kms_helper<br>
> drm snd_hda_intel snd_hda_codec snd_hwdep snd_pcm ghash_clmulni_intel snd_seq_midi snd_rawmidi snd_s<br>
> eq_midi_event snd_seq aesni_intel snd_timer i2c_algo_bit cryptd mcs7830 psmouse snd_seq_device usbnet<br>
> snd joydev aes_x86_64 hid_generic soundcore serio_raw snd_page_alloc lpc_ich microcode mac_hid video<br>
> lp parport e1000e usbhid hid<br>
> [ 19.351869] Pid: 535, comm: modprobe Not tainted 3.5.0-rc46patches+ #29<br>
> [ 19.351870] Call Trace:<br>
> [ 19.351876] [<ffffffff8105278f>] warn_slowpath_common+0x7f/0xc0<br>
><br>
> thanks<br>
> --xingchao<br>
><br>
><br>
> > -----Original Message-----<br>
> > From: Wang, Xingchao<br>
> > Sent: Tuesday, August 07, 2012 3:26 PM<br>
> > To: Daniel Vetter; Zanoni, Paulo R<br>
</div></div><div><div class="h5">> > Cc: <a href="mailto:intel-gfx@lists.freedesktop.org">intel-gfx@lists.freedesktop.org</a><mailto:<a href="mailto:intel-gfx@lists.freedesktop.org">intel-gfx@lists.freedesktop.org</a>>; Fu, Michael; Wu, Fengguang; 'Zhenyu<br>
> > Wang (<a href="mailto:zhenyuw@linux.intel.com">zhenyuw@linux.intel.com</a><mailto:<a href="mailto:zhenyuw@linux.intel.com">zhenyuw@linux.intel.com</a>>)'; Zhao, Yakui<br>
> > Subject: assertion on intel_disable_transcoder<br>
> ><br>
> > Hi Daniel/Paulo,<br>
> ><br>
> > It's easy to see such WARNING in dmesg, the DDI port is not disabled prior to<br>
> > disable transcoder.<br>
> > I am not sure it will impact the Pipe/transcoder/DDI-port configurations,<br>
> > anyway after some times WARNING, I could not make HDMI audio work<br>
> > anymore.<br>
> > With intel_audio_dump I could see the related configurations was totally<br>
> > disabled.<br>
> ><br>
> > DDI_BUF_CTL_A 0x00000080 DDI Buffer Controler A<br>
> > DDI_BUF_CTL_B 0x00000000 DDI Buffer Controler B<br>
> > DDI_BUF_CTL_C 0x00000080 DDI Buffer Controler C<br>
> > DDI_BUF_CTL_D 0x00000000 DDI Buffer Controler D<br>
> > DDI_BUF_CTL_E 0x80000002 DDI Buffer Controler E<br>
> > PIPE_CONF_A 0x00000000 PIPE Configuration A<br>
> > PIPE_CONF_B 0x00000000 PIPE Configuration B<br>
> > PIPE_CONF_C 0x00000000 PIPE Configuration C<br>
> > PIPE_CONF_EDP 0x00000000 PIPE Configuration EDP<br>
> > PIPE_DDI_FUNC_CTL_A 0xc4034002 PIPE DDI Function Control A<br>
> > PIPE_DDI_FUNC_CTL_B 0xa0035000 PIPE DDI Function Control B<br>
> > PIPE_DDI_FUNC_CTL_C 0x00030000 PIPE DDI Function Control C<br>
> > PIPE_DDI_FUNC_CTL_EDP 0x00030000 PIPE DDI Function Control EDP<br>
> > TRANS_CONF 0x00000000 Transcoder Configuration<br>
> ><br>
> > Thanks<br>
> > --xingchao<br>
> ><br>
> > [ 16.835658] ------------[ cut here ]------------<br>
> > [ 16.835690] WARNING: at drivers/gpu/drm/i915/intel_display.c:1118<br>
> > assert_fdi_tx+0x87/0x90 [i915]()<br>
> > [ 16.835691] Hardware name: Shark Bay Client platform<br>
> > [ 16.835692] FDI TX state assertion failure (expected off, current on)<br>
> > [ 16.835706] Modules linked in: snd_seq_midi_event i915(+) snd_seq<br>
> > snd_timer drm_kms_helper snd_seq<br>
> > _device ghash_clmulni_intel drm aesni_intel snd cryptd mcs7830 usbnet joydev<br>
> > aes_x86_64 soundcore psm ouse snd_page_alloc hid_generic i2c_algo_bit<br>
> > serio_raw video mac_hid microcode lpc_ich lp parport e10 00e usbhid hid<br>
> > [ 16.835708] Pid: 470, comm: modprobe Not tainted 3.5.0-rc46patches+ #12<br>
> > [ 16.835709] Call Trace:<br>
> > [ 16.835715] [<ffffffff8105278f>] warn_slowpath_common+0x7f/0xc0<br>
> > [ 16.835718] [<ffffffff81052886>] warn_slowpath_fmt+0x46/0x50<br>
> > [ 16.835728] [<ffffffffa01cc847>] assert_fdi_tx+0x87/0x90 [i915]<br>
> > [ 16.835739] [<ffffffffa01d5cf5>] ironlake_crtc_disable+0x185/0x820 [i915]<br>
> > [ 16.835748] [<ffffffffa01d641e>] ironlake_crtc_dpms+0x8e/0xa0 [i915]<br>
> > [ 16.835756] [<ffffffffa01cdbd8>] intel_crtc_dpms+0x48/0x140 [i915]<br>
> > [ 16.835768] [<ffffffffa01d49d5>] intel_crtc_disable+0x35/0xb0 [i915]<br>
> > [ 16.835772] [<ffffffffa012d6a5>]<br>
> > drm_helper_disable_unused_functions+0x115/0x190 [drm_kms_helper]<br>
> > [ 16.835785] [<ffffffffa01d849d>] intel_modeset_init+0x8ad/0xf90 [i915]<br>
> > [ 16.835796] [<ffffffffa01aebba>] i915_driver_load+0xa8a/0xb90 [i915]<br>
> > [ 16.835812] [<ffffffffa016fa7b>] ? drm_get_minor+0x26b/0x310 [drm]<br>
> > [ 16.835819] [<ffffffffa0171e71>] drm_get_pci_dev+0x191/0x2b0 [drm]<br>
> > [ 16.835834] [<ffffffffa01fc01b>] i915_pci_probe+0x4f/0x57 [i915]<br>
> > [ 16.835837] [<ffffffff8134230c>] local_pci_probe+0x5c/0xd0<br>
> > [ 16.835840] [<ffffffff81343c49>] pci_device_probe+0x109/0x130<br>
> > [ 16.835843] [<ffffffff814065ee>] driver_probe_device+0x7e/0x220<br>
> > [ 16.835845] [<ffffffff8140683b>] __driver_attach+0xab/0xb0<br>
> > [ 16.835848] [<ffffffff81406790>] ? driver_probe_device+0x220/0x220<br>
> > [ 16.835850] [<ffffffff81404a26>] bus_for_each_dev+0x56/0x90<br>
> > [ 16.835852] [<ffffffff8140610e>] driver_attach+0x1e/0x20<br>
> > [ 16.835854] [<ffffffff81405cc0>] bus_add_driver+0x1a0/0x270<br>
> > [ 16.835856] [<ffffffff81406d96>] driver_register+0x76/0x130<br>
> > [ 16.835859] [<ffffffff81343916>] __pci_register_driver+0x56/0xd0<br>
> > [ 16.835862] [<ffffffff8166949d>] ? notifier_call_chain+0x4d/0x70<br>
> > [ 16.835869] [<ffffffffa01720aa>] drm_pci_init+0x11a/0x130 [drm]<br>
> > [ 16.835871] [<ffffffffa0230000>] ? 0xffffffffa022ffff<br>
> > [ 16.835880] [<ffffffffa0230066>] i915_init+0x66/0x68 [i915]<br>
> > [ 16.835884] [<ffffffff8100203f>] do_one_initcall+0x3f/0x170<br>
> > [ 16.835887] [<ffffffff810b581e>] sys_init_module+0xbe/0x230<br>
> > [ 16.835890] [<ffffffff8166d769>] system_call_fastpath+0x16/0x1b<br>
> > [ 16.835891] ---[ end trace bd9532eaee4e4542 ]---<br>
> _______________________________________________<br>
> Intel-gfx mailing list<br>
</div></div>> <a href="mailto:Intel-gfx@lists.freedesktop.org">Intel-gfx@lists.freedesktop.org</a><mailto:<a href="mailto:Intel-gfx@lists.freedesktop.org">Intel-gfx@lists.freedesktop.org</a>><br>
> <a href="http://lists.freedesktop.org/mailman/listinfo/intel-gfx" target="_blank">http://lists.freedesktop.org/mailman/listinfo/intel-gfx</a><br>
<div class="HOEnZb"><div class="h5">><br>
<br>
> _______________________________________________<br>
> Intel-gfx mailing list<br>
> <a href="mailto:Intel-gfx@lists.freedesktop.org">Intel-gfx@lists.freedesktop.org</a><br>
> <a href="http://lists.freedesktop.org/mailman/listinfo/intel-gfx" target="_blank">http://lists.freedesktop.org/mailman/listinfo/intel-gfx</a><br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Daniel Vetter<br>
Software Engineer, Intel Corporation<br>
<a href="tel:%2B41%20%280%29%2079%20365%2057%2048" value="+41793655748">+41 (0) 79 365 57 48</a> - <a href="http://blog.ffwll.ch" target="_blank">http://blog.ffwll.ch</a><br>
</font></span></blockquote></div><br></div></div>