From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Patchwork <patchwork@emeril.freedesktop.org>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_frontbuffer_tracking: Make sure GPU is quiescent before handling assertions.
Date: Thu, 13 Dec 2018 14:39:25 +0100 [thread overview]
Message-ID: <52aab19e-1176-5d88-3a93-d6e919d02c38@linux.intel.com> (raw)
In-Reply-To: <154470538172.11001.13933758979769931703@skylake-alporthouse-com>
Op 13-12-2018 om 13:49 schreef Chris Wilson:
> Quoting Patchwork (2018-12-13 12:39:18)
>> #### Possible regressions ####
>>
>> * igt@kms_frontbuffer_tracking@fbc-modesetfrombusy:
>> - shard-glk: PASS -> TIMEOUT
>> - shard-hsw: PASS -> TIMEOUT
>> - shard-kbl: PASS -> TIMEOUT
>> - shard-snb: PASS -> TIMEOUT
> Ah, the modesetfrombusy will never idle as it does
> while (1) igt_draw_rect(IGT_DRAW_BLT); and gem_quiescent_gpu() calls
> DROP_IDLE under the belief that nothing is queueing more work and will
> eventually idle.
>
> /o\
> -Chris
Right, v2 sent. :)
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2018-12-13 13:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 9:52 [igt-dev] [PATCH i-g-t] tests/kms_frontbuffer_tracking: Make sure GPU is quiescent before handling assertions Maarten Lankhorst
2018-12-13 10:00 ` Daniel Vetter
2018-12-13 10:05 ` Chris Wilson
2018-12-14 0:18 ` Dhinakaran Pandiyan
2018-12-14 0:22 ` Dhinakaran Pandiyan
2018-12-14 9:31 ` Maarten Lankhorst
2018-12-13 10:20 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2018-12-13 11:44 ` Patchwork
2018-12-13 11:47 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2018-12-13 12:39 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-12-13 12:49 ` Chris Wilson
2018-12-13 13:39 ` Maarten Lankhorst [this message]
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=52aab19e-1176-5d88-3a93-d6e919d02c38@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=patchwork@emeril.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