From: Doug Brown <doug@schmorgal.com>
To: Zack Rusin <zack.rusin@broadcom.com>
Cc: dri-devel@lists.freedesktop.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
regressions@lists.linux.dev
Subject: [REGRESSION] drm/vmwgfx shows green Xv instead of actual video (bisected I think)
Date: Thu, 11 Jul 2024 13:37:15 -0700 [thread overview]
Message-ID: <bd9cb3c7-90e8-435d-bc28-0e38fee58977@schmorgal.com> (raw)
Hello,
I have discovered a problem in vmwgfx that caused Xv playback to break
between v6.3 and v6.4-rc1. In v6.3, inside of an Ubuntu 24.04 VMware VM
with 3D acceleration disabled, I can run the following GStreamer command
("sudo apt install gstreamer1.0-tools" if you don't already have it):
gst-launch-1.0 videotestsrc !
video/x-raw,format=YV12,width=640,height=480 ! xvimagesink
And it works fine, showing a test pattern.
In v6.4-rc1 and all the way up to a build I just made today of Linus's
latest master branch and also including Zack's latest patchset [1]:
Linux doug-Ubuntu-MATE-2404 6.10.0-rc7+ #55 SMP PREEMPT_DYNAMIC Thu Jul
11 12:46:06 PDT 2024 x86_64 x86_64 x86_64 GNU/Linux
...if I run the same command, the GStreamer window shows up containing
solid green rather than the test pattern.
I believe I have bisected the problem to commit:
39985eea5a6d ("drm/vmwgfx: Abstract placement selection")
However, the bisect process was complicated because two earlier commits
temporarily broke vmwgfx so I had to undo them during bisection, which
also required some conflict resolution:
180253782038 ("drm/ttm: stop allocating dummy resources during BO
creation") and
f87c1f0b7b79 ("drm/ttm: prevent moving of pinned BOs")
Note that if you have gstreamer1.0-vaapi installed, you should
temporarily remove it first before testing because there is a separate
Xorg bug that causes Xorg to crash when you run the above command if
gstreamer1.0-vaapi is installed.
I'm happy to do any further testing as needed. I've reproduced this
problem across several different machines and distros. A fully-updated
Arch Linux is also affected.
As a side note, that same gst-launch-1.0 command is also currently
broken with 3D acceleration enabled, but that's a separate issue in mesa
that I've submitted a patch for [2].
Thanks,
Doug
[1]
https://lore.kernel.org/all/20240702021254.1610188-1-zack.rusin@broadcom.com/#t
[2] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30116
#regzbot introduced: v6.3..v6.4-rc1
next reply other threads:[~2024-07-11 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 20:37 Doug Brown [this message]
2024-07-15 19:32 ` Ian Forbes
2024-07-16 1:44 ` Doug Brown
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=bd9cb3c7-90e8-435d-bc28-0e38fee58977@schmorgal.com \
--to=doug@schmorgal.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=zack.rusin@broadcom.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
all inboxes | Powered by JetHome®