[Bug 101623] [IGT] kms_frontbuffer_tracking at fbc-*draw* has inconsistent results - FBC disabled | Failed assertion: !fbc_wait_until_enabled()

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=101623

--- Comment #60 from Marta Löfstedt <marta.lofstedt at intel.com> ---
(In reply to Paulo Zanoni from comment #59)
> (In reply to Marta Löfstedt from comment #57)
> > We have pulled in more data from the shards testlist runs on BAT machines. I
> > am not going to spam all links here just some examples. For overview of the
> > results see:
> > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip.html
> > 
> > (kms_frontbuffer_tracking:2822) WARNING: fbc_is_enabled()?
> > FBC disabled: mode too large for compression
> 
> This is an entirely different bug.
> 
> Please go to the BIOS of the machine and increase the amount of stolen
> memory.
> 
> Thanks,
> Paulo

Thanks for the feedback, I do agree that this bug is a big mess, but that is
what happens when bugs are not solved in reasonable time. If you can define
exactly how you want the bug to be split up based on information given in the
results, I will do that. However, the problem with the current version of
cibuglog is that once I have filed a (machine, test) pair on an issue I will
not see any new results from that pair. So, since a lot of machines flip-flop
on various failure on this test it will be random what issue I will file on
first. This will be fixed with the new cibuglog that Martin Peres is working
on.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180321/b9603415/attachment.html>