| Summary: | [HSW]igt/kms_flip/flip-vs-modeset-vs-hang-interruptible causes [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring with debug kernel | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | lu hua <huax.lu> | ||||||
| Component: | DRM/Intel | Assignee: | Daniel Vetter <daniel> | ||||||
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | CC: | gordon.jin, guang.a.yang | ||||||
| Version: | unspecified | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
This is an i915 test and shouldn't be affected at all by nouveau. Also [ 22.762957] [drm] Simulated gpu hang, resetting stop_rings so this isn't actually a bug, but just an issue with our debug output being a bit too noisy. Now this noisy error output to dmesg was added in commit 05407ff889ceebe383aa5907219f86582ef96b72 Author: Mika Kuoppala <mika.kuoppala@linux.intel.com> Date: Thu May 30 09:04:29 2013 +0300 drm/i915: detect hang using per ring hangcheck_score Why was that not caught as a regression? Or have I missed the bug report? I'll write a quick patch to tune down the debug output. Created attachment 84778 [details] [review] tune down hangcheck noise Fixed on latest -nightly kernel. 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.
Created attachment 84774 [details] dmesg System Environment: -------------------------- Platform: Haswell Kernel: (drm-intel-nightly_debug)aaf0996cd776c5131d108f08a2e587ab0baaa6d4 Bug detailed description: ----------------------------- It happens on haswell with NVIDIA card GT440. [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring appears in dmesg. # cat /sys/class/drm/card1/error no error state collected Following cases also has this issue. igt/kms_flip/flip-vs-modeset-vs-hang-interruptible igt/kms_flip/flip-vs-panning-vs-hang igt/kms_flip/flip-vs-panning-vs-hang-interruptible output: Using monotonic timestamps Beginning flip-vs-modeset-vs-hang-interruptible on crtc 3, connector 21 1920x1200 60 1920 1968 2000 2080 1200 1203 1209 1235 0x9 0x48 154000 ... flip-vs-modeset-vs-hang-interruptible on crtc 3, connector 21: PASSED Beginning flip-vs-modeset-vs-hang-interruptible on crtc 5, connector 21 1920x1200 60 1920 1968 2000 2080 1200 1203 1209 1235 0x9 0x48 154000 ... flip-vs-modeset-vs-hang-interruptible on crtc 5, connector 21: PASSED Beginning flip-vs-modeset-vs-hang-interruptible on crtc 7, connector 21 1920x1200 60 1920 1968 2000 2080 1200 1203 1209 1235 0x9 0x48 154000 ... flip-vs-modeset-vs-hang-interruptible on crtc 7, connector 21: PASSED Subtest flip-vs-modeset-vs-hang-interruptible: SUCCESS Reproduce steps: ---------------------------- 1. ./kms_flip --run-subtest flip-vs-modeset-vs-hang-interruptible