Bug 109961 - [CI][SHARDS] igt@gem_eio@in-flight-suspend - dmesg-warn - Failed to idle engines, declaring wedged!
Summary: [CI][SHARDS] igt@gem_eio@in-flight-suspend - dmesg-warn - Failed to idle engi...
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-11 15:58 UTC by Martin Peres
Modified: 2019-03-12 15:32 UTC (History)
1 user (show)

See Also:
i915 platform: ALL
i915 features: GEM/Other


Attachments

Description Martin Peres 2019-03-11 15:58:41 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5724/shard-snb6/igt@gem_eio@in-flight-suspend.html

<6> [22.494626] Freezing user space processes ... (elapsed 0.281 seconds) done.
<6> [22.775781] OOM killer disabled.
<6> [22.775783] Freezing remaining freezable tasks ... 
<4> [26.189452] hpet_rtc_timer_reinit: 68 callbacks suppressed
<4> [26.189454] hpet1: lost 6 rtc interrupts
<4> [26.219607] hpet1: lost 1 rtc interrupts
<4> [26.249706] hpet1: lost 1 rtc interrupts
<4> [26.289868] hpet1: lost 1 rtc interrupts
<4> [26.350115] hpet1: lost 3 rtc interrupts
<4> [26.400321] hpet1: lost 2 rtc interrupts
<4> [26.440488] hpet1: lost 2 rtc interrupts
<4> [26.480657] hpet1: lost 1 rtc interrupts
<4> [26.520824] hpet1: lost 2 rtc interrupts
<4> [26.601154] hpet1: lost 4 rtc interrupts
<4> [27.143408] (elapsed 4.367 seconds) done.
<6> [27.143607] printk: Suspending console(s) (use no_console_suspend to debug)
<3> [27.424551] i915 0000:00:02.0: Failed to idle engines, declaring wedged!
Comment 1 CI Bug Log 2019-03-12 15:32:22 UTC
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.


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.