Bug 99742 - [SKL] [BAT] igt@gem_close_race@basic-threads hangs on SKL-6770HQ
Summary: [SKL] [BAT] igt@gem_close_race@basic-threads hangs on SKL-6770HQ
Status: CLOSED DUPLICATE of bug 100130
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-02-09 19:35 UTC by Jani Saarinen
Modified: 2017-07-24 22:39 UTC (History)
1 user (show)

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


Attachments

Comment 1 Chris Wilson 2017-02-09 20:40:48 UTC
Unrecorded hang.
Comment 2 Jani Saarinen 2017-02-14 07:51:58 UTC
This might have been only one occurrence,
Moving to staging component
Comment 3 Jani Saarinen 2017-02-16 08:47:21 UTC
Is there way to make more debugs info running runs?
Comment 4 Chris Wilson 2017-02-16 08:54:39 UTC
Whatever happened happened whilst igt was not running (gem_close_race had already finished), or at least it was not recorded that it started the next test. This is a job for serial/net consoles.
Comment 5 Abdiel Janulgue 2017-02-17 07:37:03 UTC
Did 100 gem_close_race@basic-threads iterations on SKL-6770HQ /drm-tip. No failures observed. This is a fluke.
Comment 6 Marta Löfstedt 2017-03-09 12:01:42 UTC
[   24.852687] [IGT] gem_close_race: starting subtest basic-process
[   24.872448] [IGT] gem_close_race: exiting, ret=0
[   24.930043] Console: switching to colour frame buffer device 240x75

So, igt@gem_close_race@basic-process terminated, but:
igt@gem_close_race@basic-threads is not reported as started in dmesg.
Comment 7 Jani Saarinen 2017-03-10 10:07:50 UTC
Collecting more data, setting need info.
Comment 8 Chris Wilson 2017-03-16 23:29:12 UTC
Either #100130 or #100232

*** This bug has been marked as a duplicate of bug 100130 ***


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.