==System Environment== -------------------------- Regression: Yes. Non-working platforms: BYT ==kernel== -------------------------- origin/drm-intel-nightly:c5660b4ad395f1e34eacc22cf81c687edfc9c83c(fails) drm-intel-nightly: 2014y-09m-19d-18h-12m-22s UTC integration manifest ==Bug detailed description== ----------------------------- igt/kms_render/direct-render and gpu-blit cause "WARNING: CPU: 1 PID: 17633 at drivers/gpu/drm/i915/intel_display.c:1746 vlv_wait_port_ready+0xe5/0x11e [i915]()" Dmesg: [ 2132.759240] WARNING: CPU: 1 PID: 17633 at drivers/gpu/drm/i915/intel_display.c:1746 vlv_wait_port_ready+0xe5/0x11e [i915]() [ 2132.759245] timed out waiting for port C ready: 0x000020ff [ 2132.759249] Modules linked in: ip6table_filter ip6_tables ipv6 iptable_filter ip_tables ebtable_nat ebtables x_tables dm_mod snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iTCO_wdt iTCO_vendor_support snd_hda_intel snd_hda_controller serio_raw pcspkr snd_hda_codec snd_hwdep snd_pcm snd_timer i2c_i801 lpc_ich mfd_core snd soundcore iosf_mbi battery ac acpi_cpufreq i915 button video drm_kms_helper drm [ 2132.759316] CPU: 1 PID: 17633 Comm: kms_render Tainted: G W 3.17.0-rc5_prts_ab7f1a_20140917_debug+ #28 [ 2132.759321] 0000000000000000 ffff880074aafa60 ffffffff8181608c ffff880074aafaa8 [ 2132.759331] ffff880074aafa98 ffffffff8103e87f ffffffffa00cf6db ffff880003650000 [ 2132.759340] 00000000000000f0 0000000000186014 ffff880075935000 ffff880074aafaf8 [ 2132.759349] Call Trace: [ 2132.759361] [] dump_stack+0x45/0x56 [ 2132.759370] [] warn_slowpath_common+0x7f/0x98 [ 2132.759413] [] ? vlv_wait_port_ready+0xe5/0x11e [i915] [ 2132.759420] [] warn_slowpath_fmt+0x4c/0x4e [ 2132.759464] [] vlv_wait_port_ready+0xe5/0x11e [i915] [ 2132.759508] [] vlv_pre_enable_dp+0x10a/0x115 [i915] [ 2132.759550] [] valleyview_crtc_enable+0xa33/0xae2 [i915] [ 2132.759593] [] __intel_set_mode+0xc77/0x127f [i915] [ 2132.759602] [] ? trace_hardirqs_on_caller+0x16e/0x18a [ 2132.759644] [] intel_set_mode+0x14/0x2a [i915] [ 2132.759687] [] intel_crtc_set_config+0x9b6/0xa9f [i915] [ 2132.759713] [] drm_mode_set_config_internal+0x55/0xe0 [drm] [ 2132.759738] [] drm_mode_setcrtc+0x39e/0x498 [drm] [ 2132.759759] [] drm_ioctl+0x385/0x404 [drm] [ 2132.759783] [] ? drm_mode_setplane+0x1d8/0x1d8 [drm] [ 2132.759792] [] ? mntput_no_expire+0x5/0x1af [ 2132.759800] [] do_vfs_ioctl+0x3a3/0x46c [ 2132.759808] [] ? current_kernel_time+0x61/0x9a [ 2132.759816] [] ? trace_hardirqs_on_caller+0x16e/0x18a [ 2132.759823] [] SyS_ioctl+0x50/0x7d [ 2132.759831] [] system_call_fastpath+0x16/0x1b [ 2132.759835] ---[ end trace 271f8fc0a83a07a6 ]--- [ 2132.901162] [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe B underrun [ 2132.901171] [drm:valleyview_pipestat_irq_handler] *ERROR* pipe B underrun [ 2133.628905] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [ 2134.462175] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting", ==Reproduce steps== ---------------------------- 1. ./kms_render --run-subtest direct-render ==Bisect results form [PRTS][auto-bisect]== ---------------------------- commit f81d8eba4fb4448e6ea777aa2072c3b9f277e7cb Author: Chris Wilson <chris@chris-wilson.co.uk> AuthorDate: Fri Sep 12 09:11:55 2014 +0100 Commit: Chris Wilson <chris@chris-wilson.co.uk> CommitDate: Fri Sep 12 09:12:42 2014 +0100 igt/kms_render: Iterate only through the formats When testing each format, iterate through the formats and not randomly through the modes. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=83788 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Bisect result is incorrect, as that commit enables the testing...
(In reply to comment #1) > Bisect result is incorrect, as that commit enables the testing... Chris, do you mean: a) the bisect process is broken, and that's not the first bad commit. or b) it's the first bad commit, but not the culprit of the failure, i.e. the commit is correct, and reveals an earlier bug. I guess b). But saying "bisect result is incorrect" confuses me. I had similar confusion on several bugs, and want to get it clarified.
Indeed its (b): The commit enables testing that reveals a bug in another piece of code.
In this case I'd suggest "the bisected commit reveals the bug" instead of "the bisect result is incorrect". Thanks.
That implies that the bisection is finished, it is not. This bisect result is incorrect and the bisection needs to be restarted in order to find the correct result.
This direct-render test runs well for me on today's nightly. Could you please retest
pass in the latest nightly branch: d2a1764437d8b4c30948704ff6c64e4bbfd1df7c(2015-01-20) change state to "verified".
Closing old verified.
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.