Bug 100998 - [BAT][BLK] igt@gem_busy@basic-hang-default hanged on CI
Summary: [BAT][BLK] igt@gem_busy@basic-hang-default hanged on CI
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-11 07:19 UTC by Jani Saarinen
Modified: 2017-06-27 14:16 UTC (History)
1 user (show)

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


Attachments

Description Jani Saarinen 2017-05-11 07:19:13 UTC
On CI igt@gem_busy@basic-hang-default was incompleted.

https://intel-gfx-ci.01.org/CI/CI_DRM_2602/fi-blk-e6850/igt@gem_busy@basic-hang-default.html

Dmesg: https://intel-gfx-ci.01.org/CI/CI_DRM_2602/fi-blk-e6850/dmesg-during.log

HW: 
fi-elk-e7500	HP Compaq 8000	Eagle Lake Core2Duo E7500	GMA4500	DP (VGA)

Documenting and mark to CI as known.
Comment 1 Chris Wilson 2017-05-11 07:23:41 UTC
Notice the loss of dmesg, and lost information as to what took the machine out.

How about if we mount the fs with sync?
Comment 2 Martin Peres 2017-06-15 11:27:16 UTC
Good idea Chris! Tomi will try to remount the filesystem with sync before running IGT.

I will close this bug for now, it used to happen every day, but we got no new occurence since May 24th!
Comment 3 Chris Wilson 2017-06-15 11:59:31 UTC
commit 48f1fc3a301d50c27c07a0fe73cd3a75d4f59552
Author: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Date:   Mon May 22 12:02:44 2017 +0300

    drm/i915/g33: Improve reset reliability
    
    We improved the reset reliablity on gen4 with
    stopping all engines before commencing reset, in
    commit 2c80353f3cd0 ("drm/i915/g4x: Improve gpu reset reliability")
    
    Evidence indicates that this same trick works with g33.
Comment 4 Ricardo 2017-06-27 14:16:31 UTC
Closing bug since there is no new failures


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.