Summary: | [CI][DRMTIP] igt@kms_vblank@pipe-b-ts-continuation-idle - dmesg-warn - WARN_ON((val & icl_dpclka_cfgcr0_clk_off(dev_priv, port)) == 0) | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | XOrg git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | ICL | i915 features: | display/Other |
Description
Martin Peres
2018-10-23 07:52:52 UTC
Bumping the priority to high because it has the potential to affect any modeset (acked by Danvet). I will bump it again if necessary. Need to see with newer than BIOS ICLSFWR1.R00.2352 Not seen lately: last time 1 month, 2 weeks / 1155 runs ago Closing. (In reply to Jani Saarinen from comment #4) > Closing. The time it was no seen for is irrelevant without knowing the reproduction rate. Right now, we have one occurrence, in a drmtip run. There has been only 25 runs after this, so it should definitely remain open. This also passes on shards today, and BIOS also was updated. (In reply to Jani Saarinen from comment #6) > This also passes on shards today, and BIOS also was updated. Shards is a fair point. But we got at best 200 runs out of them, and it also "passes" on the same machine on the drmtip_ runs... Does not mean it is fixed though! Right now, we could have a bug with a reproduction rate of 1%. It's ok to drop the priority (just did it), but it does not warrant closing it... Please at least evaluate how bad this WARN is, and if it really is not too impactful for our users, then we can ignore the bug again for a couple more month and close it. (In reply to Martin Peres from comment #7) > (In reply to Jani Saarinen from comment #6) > > This also passes on shards today, and BIOS also was updated. > > Shards is a fair point. But we got at best 200 runs out of them, and it also > "passes" on the same machine on the drmtip_ runs... Does not mean it is > fixed though! > > Right now, we could have a bug with a reproduction rate of 1%. It's ok to > drop the priority (just did it), but it does not warrant closing it... This should be fixed by commit 70332ac539c5c5dffede580fe8986dcfc0751d55 Author: Imre Deak <imre.deak@intel.com> Date: Thu Nov 1 16:04:27 2018 +0200 drm/i915/icl+: Sanitize port to PLL mapping based on that the bug can be closed. > > Please at least evaluate how bad this WARN is, and if it really is not too > impactful for our users, then we can ignore the bug again for a couple more > month and close it. (In reply to Imre Deak from comment #8) > (In reply to Martin Peres from comment #7) > > (In reply to Jani Saarinen from comment #6) > > > This also passes on shards today, and BIOS also was updated. > > > > Shards is a fair point. But we got at best 200 runs out of them, and it also > > "passes" on the same machine on the drmtip_ runs... Does not mean it is > > fixed though! > > > > Right now, we could have a bug with a reproduction rate of 1%. It's ok to > > drop the priority (just did it), but it does not warrant closing it... > > This should be fixed by > commit 70332ac539c5c5dffede580fe8986dcfc0751d55 > Author: Imre Deak <imre.deak@intel.com> > Date: Thu Nov 1 16:04:27 2018 +0200 > > drm/i915/icl+: Sanitize port to PLL mapping > > based on that the bug can be closed. Thanks! |
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.