Summary: | [CI] igt@kms_frontbuffer_tracking@* - fail - FBC disabled: mode too large for compression | ||
---|---|---|---|
Product: | DRI | Reporter: | Marta Löfstedt <marta.lofstedt> |
Component: | IGT | Assignee: | Jose Roberto de Souza <jose.souza> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs, jose.souza |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | SKL | i915 features: | display/FBC |
Description
Marta Löfstedt
2018-03-22 07:17:04 UTC
from comment 59 in bug 101623: "Please go to the BIOS of the machine and increase the amount of stolen memory. Thanks, Paulo " changing component to IGT, although this need update in intel CI system HW. From Tomi: "SKL-6770hq BIOS settings Graphics minimum memory 64MB -> 256MB, Graphics mem aperture 256MB -> 1024MB Hopefully helps. This one is not related to memory, it is because the resolution is bigger than the resolution that hardware track can handle, so there is not fix for those. You can run this tests with "--use-small-modes" to avoid those errors. (In reply to Jose Roberto de Souza from comment #4) > This one is not related to memory, it is because the resolution is bigger > than the resolution that hardware track can handle, so there is not fix for > those. > You can run this tests with "--use-small-modes" to avoid those errors. We can not have arguments on cmd line when running on CI. The test need to be fixed. (In reply to Jose Roberto de Souza from comment #6) > Done: https://patchwork.freedesktop.org/series/41156/ Thanks for the patch, we'll need a drmtip run to see if it works, since the affected machine doesn't run those test on regular basis in BAT. Hi Marta did it ran? Should I ask someone else to review and merge? (In reply to Jose Roberto de Souza from comment #8) > Hi Marta did it ran? Should I ask someone else to review and merge? yes, the results from drmtip17 is in, and the issue isn't reproduced thanks for the fix I will close this bug. Nope it was not fixed for drmtip17: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_17/fi-skl-6770hq/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-msflip-blt.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_17/fi-skl-6770hq/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-shrfb-draw-mmap-wc.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_17/fi-skl-6770hq/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_17/fi-skl-6770hq/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html I need to repoen the bug But this tests ran with my patch merged into IGT? I don`t think that it happened. (In reply to Jose Roberto de Souza from comment #11) > But this tests ran with my patch merged into IGT? I don`t think that it > happened. I'll set the bug to resolved fix again so it can be checked on next drmtip run The discussed patch is not merged yet. Please changed the bug to resolved/fixed when that patch is merged. Fix merged in IGT Closed as this was not seen since few months (4). This issue can be reopened only if we see similar failure. Orelse need to check if there is a similar bug filed already, if not create a new bug. Used to be reproduced on drmtip every round. Now it was not seen since ~70 rounds rounds. CLosing the bug. |
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.