From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105680] [CI] igt@kms_frontbuffer_tracking@* - fail - FBC disabled: mode too large for compression
Date: Thu, 29 Mar 2018 19:40:05 +0000 [thread overview]
Message-ID: <bug-105680-502-4lOgXwAPAV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105680-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 434 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105680
--- Comment #4 from Jose Roberto de Souza <jose.souza@intel.com> ---
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1333 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-03-29 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-105680-502@http.bugs.freedesktop.org/>
2018-03-29 8:52 ` [Bug 105680] [CI] igt@kms_frontbuffer_tracking@* - fail - FBC disabled: mode too large for compression bugzilla-daemon
2018-03-29 13:59 ` bugzilla-daemon
2018-03-29 19:40 ` bugzilla-daemon [this message]
2018-04-04 8:24 ` bugzilla-daemon
2018-04-04 20:34 ` bugzilla-daemon
2018-04-05 5:38 ` bugzilla-daemon
2018-04-11 17:31 ` bugzilla-daemon
2018-04-12 7:58 ` bugzilla-daemon
2018-04-12 7:58 ` bugzilla-daemon
2018-04-12 8:26 ` bugzilla-daemon
2018-04-12 16:12 ` bugzilla-daemon
2018-04-13 5:37 ` bugzilla-daemon
2018-04-16 11:01 ` bugzilla-daemon
2018-04-20 21:54 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-105680-502-4lOgXwAPAV@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox