Bug 43178 - [IVB] *ERROR*missed IRQ while running gem_dummy_reloc_loop of Intel-gpu-tools
Summary: [IVB] *ERROR*missed IRQ while running gem_dummy_reloc_loop of Intel-gpu-tools
Status: CLOSED DUPLICATE of bug 38862
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Daniel Vetter
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-22 19:23 UTC by Guang Yang
Modified: 2017-10-06 14:51 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Guang Yang 2011-11-22 19:23:41 UTC
System Environment:
--------------------------
Platform: Ivybridge        
Kernel: (drm-intel-next)9a10f401a401ca69c6537641c8fc0d6b57b5aee8

Bug detailed description:
-------------------------
When I run gem_dummy_reloc_loop of Intel-gpu-tools,occurs a error.

dmesg information:
[drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed... gen6 bsd ring idle [waiting on 2100960, at 2100960], missed IRQ?
[drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed... gen6 bsd ring idle [waiting on 2102392, at 2102392], missed IRQ?
[drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed... gen6 bsd ring idle [waiting on 2107348, at 2107348], missed IRQ?
[drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed... gen6 bsd ring idle [waiting on 2108806, at 2108806], missed IRQ?
[drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed... gen6 bsd ring idle [waiting on 2109848, at 2109848], missed IRQ?
Comment 1 Daniel Vetter 2011-11-23 02:18:21 UTC
Let's keep track of all things "missed IRQ" in the original bug report. Finding a better tool to reproduce it doesn't really change anything of the underlying problem.

*** This bug has been marked as a duplicate of bug 38862 ***
Comment 2 Elizabeth 2017-10-06 14:51:25 UTC
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.