On CI igt@gem_exec_reloc@basic-gtt incomplete https://intel-gfx-ci.01.org/CI/CI_DRM_2336/fi-byt-j1900/igt@gem_exec_reloc@basic-gtt.html Dmesg: https://intel-gfx-ci.01.org/CI/CI_DRM_2336/fi-byt-j1900/dmesg-during.log
*** This bug has been marked as a duplicate of bug 100130 ***
Seems like it came back to life.
Here are the results: https://intel-gfx-ci.01.org/CI/CI_DRM_2455/fi-byt-j1900/igt@gem_exec_reloc@basic-gtt.html
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.
Added w/a max_cstate=0 to BYT-j1900 kernel command line.
With the suggestion of Mika Kuoppala, removed max_cstate=0 and added maxcpus=2
*** Bug 100313 has been marked as a duplicate of this bug. ***
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
Assuming that these incompletes were the irq bugs fixed about the same time as these were filed.
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.