Created attachment 98961 [details] dmesg ==System Environment== -------------------------- Regression: No. Non-working platforms: HSW ULT ==kernel== -------------------------- -nightly: 18a7661946082f5a3b353e50d1ced5d89f864024 (fails) -queued: ca26115df8a2ed25b2c0ed1b7c9557c7779d1556 (fails) Author: Ville Syrjälä <ville.syrjala@linux.intel.com> Date: Thu May 8 22:19:42 2014 +0300 x86/gpu: Sprinkle const, __init and __initconst to stolen memory quirks gen8_stolen_size() is missing __init, so add it. Also all the intel_stolen_funcs structures can be marked __initconst. intel_stolen_ids[] can also be made const if we replace the __initdata with __initconst. Cc: Ingo Molnar <mingo@kernel.org> Cc: H. Peter Anvin <hpa@zytor.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> -fixes: 05adaf1f101f25f40f12c29403e6488f0e45f6b6 (fails) Author: Jani Nikula <jani.nikula@intel.com> Date: Fri May 9 14:52:34 2014 +0300 drm/i915/vlv: reset VLV media force wake request register Media force wake get hangs the machine when the system is booted without displays attached. The assumption is that (at least some versions of) the firmware has skipped some initialization in that case. Empirical evidence suggests we need to reset the media force wake request register in addition to the render one to avoid hangs. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=75895 Reported-by: Imre Deak <imre.deak@intel.com> Reported-by: Darren Hart <dvhart@linux.intel.com> Tested-by: Darren Hart <dvhart@linux.intel.com> Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com> Cc: stable@vger.kernel.org Signed-off-by: Jani Nikula <jani.nikula@intel.com> ==Bug detailed description== ----------------------------- Some subcases of igt/drv_suspend below hang sporadically, the hang rate was about 1 out of 3, and the cases fail sometimes. igt/drv_suspend/debugfs-reader igt/drv_suspend/fence-restore-tiled2untiled igt/drv_suspend/fence-restore-untiled igt/drv_suspend/forcewake igt/drv_suspend/sysfs-reader Output: ./drv_suspend --run-subtest debugfs-reader IGT-Version: 1.6-gd848a36 (x86_64) (Linux: 3.15.0-rc3_drm-intel-next-queued_ca2611_20140513+ x86_64) rtcwake: wakeup from "mem" using /dev/rtc0 at Tue May 13 05:48:36 2014 sh: line 1: 4459 Done find /sys/kernel/debug/dri/0/ -type f 4460 Segmentation fault (core dumped) | xargs cat > /dev/null 2>&1 Test assertion failure function igt_stop_helper, file igt_core.c:791: Last errno: 0, Success Failed assertion: WIFSIGNALED(status) && WTERMSIG(status) == (proc->use_SIGKILL ? SIGKILL : SIGQUIT) Subtest debugfs-reader: FAIL drv_suspend: igt_core.c:726: fork_helper_exit_handler: Assertion `ret == 0' failed. Aborted (core dumped) ./drv_suspend --run-subtest forcewake IGT-Version: 1.6-gd848a36 (x86_64) (Linux: 3.15.0-rc3_drm-intel-next-queued_ca2611_20140513+ x86_64) rtcwake: wakeup from "mem" using /dev/rtc0 at Tue May 13 05:51:56 2014 rtcwake: write error Test assertion failure function igt_system_suspend_autoresume, file igt_aux.c:327: Last errno: 0, Success Failed assertion: ret == 0 Subtest forcewake: FAIL ==Reproduce steps== ---------------------------- 1. ./drv_suspend --run-subtest forcewake
Is this a regression? Only certain subtests or all of them? Specifically I'm thinking of drv_suspend/forcewake, which is currently still hitting a known issue with runtime pm.
Also does this only happen on ult or also on other hsw platforms? Any other general stability issues (suspend failing, modeset issues) on this platform?
(In reply to comment #2) > Also does this only happen on ult or also on other hsw platforms? Any other > general stability issues (suspend failing, modeset issues) on this platform? I tried on other hsw more than 10 times, didn't found system hang.Here has another stability bug 78059 about igt/drv_suspend/forcewake.
(In reply to comment #1) > Is this a regression? Only certain subtests or all of them? > > Specifically I'm thinking of drv_suspend/forcewake, which is currently still > hitting a known issue with runtime pm. I didn't find good commit on -next-queued. Not only drv_suspend/forcewake causes system hang, other cases like drv_suspend/sysfs-reader can causes system hang too.
Hi Guo, is it still happening on latest nightly? Is there any error_state?
Test passes on latest -nightly(2ea23cd593ba60ead60e2f796fae675aa4475b1a) [root@x-hswu22 tests]# ./drv_suspend --run-subtest forcewake IGT-Version: 1.6-gff3c122 (x86_64) (Linux: 3.17.0_drm-intel-nightly_2ea23c_20141016+ x86_64) rtcwake: wakeup from "mem" using /dev/rtc0 at Thu Oct 16 19:06:04 2014 Subtest forcewake: SUCCESS [root@x-hswu22 tests]# echo $? 0
Closing old verified+fixed.
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.