From: Melissa Wen <melissa.srw@gmail.com>
To: igt-dev@lists.freedesktop.org
Cc: kernel-usp@googlegroups.com, twoerner@gmail.com
Subject: [igt-dev] [PATCH i-g-t v2 0/1] test/kms_cursor_crc: tie some loose ends in prepare_crtc
Date: Thu, 16 Jul 2020 08:24:49 -0300 [thread overview]
Message-ID: <cover.1594897760.git.melissa.srw@gmail.com> (raw)
Hi,
Using vkms, when running a sequence of subtests from kms_cursor_crc,
several strange timeout failures occurred. For example, running the
alpha-opaque cursor twice, the first run is successful and the second
fails. In addition, if we run the entire test in a call (i.e.: sudo
IGT_FORCE_DRIVER=vkms build/tests/kms_cursor_crc), the first subtest
passes and the rest of the subtests fail - even those that succeed when
run in isolation.
igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
igt_core-INFO: Timed out: Opening crc fd, and poll for first CRC.
During my debugging process, I found two issues that were blocking
execution:
1 - When a subtest fails, it exits and skips the cleaning step, leaving
the pipe_crc allocated and blocked for the next subtest; the following
patch addresses it by releasing any old pipe_crc before creating a new
one.
2 - When the CRC capture process starts, it enters an endless wait; in
the previous version, I thought it was a matter of timing in test using
vkms, but after further investigation, other problems arise in the same
subject and I am dropping the 2nd patch to better solve the problem on
the vkms side.
Changes in v2:
- Rebase 1st patch on master
- Drop the 2nd patch
Melissa Wen (1):
test/kms_cursor_crc: release old pipe_crc before create a new one
tests/kms_cursor_crc.c | 2 ++
1 file changed, 2 insertions(+)
--
2.27.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-07-16 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 11:24 Melissa Wen [this message]
2020-07-16 11:25 ` [igt-dev] [PATCH i-g-t v2 1/1] test/kms_cursor_crc: release old pipe_crc before create a new one Melissa Wen
2020-07-20 15:10 ` Arkadiusz Hiler
2020-07-16 11:52 ` [igt-dev] ✓ Fi.CI.BAT: success for test/kms_cursor_crc: tie some loose ends in prepare_crtc (rev2) Patchwork
2020-07-16 15:10 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=cover.1594897760.git.melissa.srw@gmail.com \
--to=melissa.srw@gmail.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kernel-usp@googlegroups.com \
--cc=twoerner@gmail.com \
/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