Created attachment 114840 [details] dmesg System Environment: -------------------------- Regression: not sure Non-working platforms: SKL ==kernel== -------------------------- drm-intel-nightly/d72ff1ab1499711c941831400629c14493313b3a commit d72ff1ab1499711c941831400629c14493313b3a Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Tue Mar 31 17:30:12 2015 +0200 drm-intel-nightly: 2015y-03m-31d-15h-29m-33s UTC integration manifest ==Bug detailed description== ----------------------------- Run ./kms_cursor_crc --run-subtest cursor-256x256-onscreen on SKL-Y with -nightly kernel, it causes system hang at the 2nd round. output: IGT-Version: 1.10-g2f0e3cd (x86_64) (Linux: 4.0.0-rc6_drm-intel-nightly_d72ff1_2 Beginning cursor-256x256-onscreen on pipe A, connector eDP-1 ............................ cursor-256x256-onscreen on pipe A, connector eDP-1: PASSED Beginning cursor-256x256-onscreen on pipe B, connector eDP-1 ............................ cursor-256x256-onscreen on pipe B, connector eDP-1: PASSED Beginning cursor-256x256-onscreen on pipe C, connector eDP-1 ............................ cursor-256x256-onscreen on pipe C, connector eDP-1: PASSED Subtest cursor-256x256-onscreen: SUCCESS (29.165s) real 0m29.859s user 0m5.726s sys 0m0.527s root@x-skly05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# time ./kms_cursor_crc --run-subtest cursor-256x256-onscreen IGT-Version: 1.10-g2f0e3cd (x86_64) (Linux: 4.0.0-rc6_drm-intel-nightly_d72ff1_20150401+ x86_64) Beginning cursor-256x256-onscreen on pipe A, connector eDP-1 .Warning on condition crc->crc[i] == 0xffffffff in fucntion crc_sanity_checks, file igt_debugfs.c:494 Suspicious CRC: it looks like the CRC read back was from a register in a powered down well ==Reproduce steps== ---------------------------- 1. run ./kms_cursor_crc --run-subtest cursor-256x256-onscreen twice
Could you provide the output of dmesg with drm.debug=0x1e leading to the hang?
Looks like dmesg got truncated. There is no information between timestamps 41.756717] and 112.931420. It also doesn't have the "kms_cursor_crc: executing" line. Could you give another try to get a complete dmesg?
I run it more than 5 cycles on the latest drm-intel-nightly kernel, it works well. Close it.
Verified.Fixed.
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.