Regression: drm-tests are broken in VMs |
|||||
Issue description
Using a newbie build, ToT.
Started the build in qemu-2.9.0:
$ qemu-system-x86_64 -smp 4 --enable-kvm -m 2G -vga virtio -net nic,model=virtio -net user,hostfwd=tcp:127.0.0.1:9222-:22 -drive format=raw,file=${HOME}/chromeos/src/build/images/newbie/R60-9519.0.2017_05_03_1819-a1/chromiumos_qemu_image.bin -show-cursor -usb -device usb-tablet
SSH into the VM, then:
localhost ~ # stop ui
ui stop/waiting
localhost ~ # null_platform_test
The subsystem type is not supported yet
The subsystem type is not supported yet
The subsystem type is not supported yet
The subsystem type is not supported yet
The subsystem type is not supported yet
libEGL warning: MESA-LOADER: failed to retrieve device information
libEGL warning: DRI2: failed to open vgem (search paths /usr/lib64/dri)
The subsystem type is not supported yet
The subsystem type is not supported yet
The subsystem type is not supported yet
The subsystem type is not supported yet
The subsystem type is not supported yet
libEGL warning: MESA-LOADER: failed to retrieve device information
libEGL warning: DRI2: failed to open virtio_gpu (search paths /usr/lib64/dri)
ERROR:bs_egl_setup():egl.c:139:EGL_KHR_fence_sync and EGL_KHR_wait_sync extension not supported
ERROR:main():null_platform_test.c:136:failed to setup egl context
localhost ~ # linear_bo_test
The subsystem type is not supported yet
The subsystem type is not supported yet
The subsystem type is not supported yet
The subsystem type is not supported yet
The subsystem type is not supported yet
libEGL warning: MESA-LOADER: failed to retrieve device information
libEGL warning: DRI2: failed to open vgem (search paths /usr/lib64/dri)
The subsystem type is not supported yet
The subsystem type is not supported yet
The subsystem type is not supported yet
The subsystem type is not supported yet
The subsystem type is not supported yet
libEGL warning: MESA-LOADER: failed to retrieve device information
libEGL warning: DRI2: failed to open virtio_gpu (search paths /usr/lib64/dri)
ERROR:bs_egl_setup():egl.c:139:EGL_KHR_fence_sync and EGL_KHR_wait_sync extension not supported
ERROR:main():linear_bo_test.c:307:failed to setup egl context
localhost ~ #
The error message points to a change in https://chromium-review.googlesource.com/c/478773/ , so assigning to gurchetansingh@. If that's a red herring, can you help find an owner?
,
May 4 2017
Indeed, they used to work just fine.
,
May 4 2017
We should implement the sync extension in Mesa for the sw path.
,
May 11 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/f86e218df1f6fd1125774e7e9e80c5f0b04e108b commit f86e218df1f6fd1125774e7e9e80c5f0b04e108b Author: Gurchetan Singh <gurchetansingh@google.com> Date: Thu May 11 03:58:09 2017 media-libs/mesa: Add support for fences on VMs If we're really going to use the flush image external extension for synchronization, we'll need this capability as well. BUG= chromium:718507 , chromium:719983 TEST=null_platform_test runs on a VM Change-Id: Ia2b5830970a555002d91de5229f44907b1ef66e1 Reviewed-on: https://chromium-review.googlesource.com/497267 Commit-Ready: Gurchetan Singh <gurchetansingh@chromium.org> Tested-by: Gurchetan Singh <gurchetansingh@chromium.org> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> [add] https://crrev.com/f86e218df1f6fd1125774e7e9e80c5f0b04e108b/media-libs/mesa/files/17.0-st-dri-Add-fence-extension-to-SW-path.patch [rename] https://crrev.com/f86e218df1f6fd1125774e7e9e80c5f0b04e108b/media-libs/mesa/mesa-17.1.0-r8.ebuild [modify] https://crrev.com/f86e218df1f6fd1125774e7e9e80c5f0b04e108b/media-libs/mesa/mesa-17.1.0.ebuild [modify] https://crrev.com/f86e218df1f6fd1125774e7e9e80c5f0b04e108b/media-libs/mesa/mesa-9999.ebuild
,
May 11 2017
null_platform_test is now (R9540) working again. linear_bo_test doesn't throw errors but doesn't display anything when using the VNC output for qemu 2.6. It works with VNC and GTK for qemu 2.0. Not sure if ever worked, I'll assume this is a qemu 2.6 bug. It would be good to know if newer versions have fixed it.
,
Aug 1 2017
,
Jan 22 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by gurcheta...@chromium.org
, May 4 2017