Created attachment 113268 [details] dmesg ==System Environment== -------------------------- Regression: not sure, this issue is not 100% reproducible. Non-working platforms: SNB ==kernel== -------------------------- nightly-2015-02-09/b4442ee4e150506cebeee72249efc566c5f14bbe ==Bug detailed description== -------------------------- Some of kms_flip subcases will hang, the white block stop fliping on monitor, and the case is unable to be stoped with ctrl+c or kill command. If you tried to reboot it, the ssh connection may lost, seems the system is hang. This issue is not 100% reproducible, so the affect case maybe more than listed. Affected cases: igt/kms_flip/plain-flip-fb-recreate igt/kms_flip/2x-plain-flip-fb-recreate-interruptible ==Reproduce steps== ---------------------------- 1. ./kms_flip --run-subtest plain-flip-fb-recreate
Add IVB in this bug.
add BYT-M in this bug
Add HSW in this bug. After running several sub cases in kms_flip, every kms_flip subcase will cause such dmesg output even it run well before: dmesg -r |grep '<[1-4]>'|grep drm <3>[10539.077274] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A <3>[10539.077283] [drm:cpt_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun <3>[10539.078778] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A <3>[10539.078788] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun And keep on running kms_flip subcases, you may see the case hang and not able to be stopped and system could not reboot either.
This might be the fb unref bug we've recently fixed in commit 8218c3f4df3bb1c637c17552405039a6dd3c1ee1 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Fri Feb 27 12:58:13 2015 +0100 drm: Fixup racy refcounting in plane_force_disable Reason for this hunch: Onyl -recreate seems to blow up.
pass on nightly branch latest commit 333cf6eed7cae0ee2d6bb1b4c4d421b94f84fc13(2015-04-03), close this bug
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.