Bug 100254 - [BYT][BAT] gem_exec_reloc@basic-gttin incomplete in CI
Summary: [BYT][BAT] gem_exec_reloc@basic-gttin incomplete in CI
Status: CLOSED FIXED
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:
: 100313 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-03-17 15:30 UTC by Jani Saarinen
Modified: 2017-06-27 15:19 UTC (History)
2 users (show)

See Also:
i915 platform: BYT
i915 features:


Attachments

Comment 1 Chris Wilson 2017-03-17 15:32:14 UTC

*** This bug has been marked as a duplicate of bug 100130 ***
Comment 2 Martin Peres 2017-04-03 09:18:13 UTC
Seems like it came back to life.
Comment 4 Chris Wilson 2017-04-03 09:31:26 UTC
Going by those results, there is no bug. There is an old Baytrail instability bug (w/a max_cstate=0) that can cause a hard hang, so unless this is still occurring across multiple machines (which iirc recent CI is all about byt j1900) or we have something actionable from the logs, max_cstate=0 would be the next step.
Comment 5 Tomi Sarvela 2017-04-03 13:15:40 UTC
Added w/a max_cstate=0 to BYT-j1900 kernel command line.
Comment 6 Tomi Sarvela 2017-04-03 14:00:54 UTC
With the suggestion of Mika Kuoppala, removed max_cstate=0 and added maxcpus=2
Comment 7 Mika Kuoppala 2017-04-05 11:08:24 UTC
*** Bug 100313 has been marked as a duplicate of this bug. ***
Comment 8 Mika Kuoppala 2017-04-05 11:16:59 UTC
maxcpus=2 was chosen as a workaround for pm/intel_idle problems with 4 core baytrails. References:

https://bugzilla.kernel.org/show_bug.cgi?id=109051
https://bugzilla.kernel.org/show_bug.cgi?id=195255
Comment 9 Chris Wilson 2017-05-03 13:33:11 UTC
Assuming that these incompletes were the irq bugs fixed about the same time as these were filed.
Comment 10 Ricardo 2017-06-27 15:19:46 UTC
issue is solved and now closing - Cleaning our bug BD from resolved


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.