Summary: | [BAT][BSW] CI run hit a scheduler warning (rq->clock_update_flags < RQCF_ACT_SKIP) | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED NOTOURBUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | critical | ||
Priority: | highest | CC: | intel-gfx-bugs |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | BSW/CHT | i915 features: | power/suspend-resume |
Description
Martin Peres
2017-04-11 14:03:13 UTC
Adding tag into "Whiteboard" field - ReadyForDev The bug still active *Status is correct *Platform is included *Feature is included *Priority and Severity correctly set Seems to be a bug in the kernel, not i915.. https://patchwork.kernel.org/patch/9586351/ (In reply to Maarten Lankhorst from comment #2) > Seems to be a bug in the kernel, not i915.. > > https://patchwork.kernel.org/patch/9586351/ Yes, it is. I filed it here because that's what we agreed on before, that we should file the bugs with i915 first since it impacts our testing, and then move it to the right owner. Of course, we never got to do that and I hope that we will soon have the man power to handle these bugs appropriately... Anyway, this is becoming funnier. The patch you mentioned made it to drm-tip but 2 days ago, we got this result: https://intel-gfx-ci.01.org/CI/CI_DRM_2590/fi-bsw-n3050/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html Martin, what are next steps here? I guess we really need to get someone to communicate with upstream so as they could propose a patch for it. (In reply to Martin Peres from comment #5) > I guess we really need to get someone to communicate with upstream so as > they could propose a patch for it. I don't see this happening anymore. Let's whitelist this test. |
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.