[Bug 1722897] Re: Ubuntu Wayland seems to be allocating 2-3 framebuffer sized surfaces (more than Xorg)
FYI, I am going to upstream the workaround mentioned in #7. @vanvugt, regarding the pitch, can you point me to the place where this is determined so I can figure out a way to get around it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722897 Title: Ubuntu Wayland seems to be allocating 2-3 framebuffer sized surfaces (more than Xorg) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1722897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722897] Re: Ubuntu Wayland seems to be allocating 2-3 framebuffer sized surfaces (more than Xorg)
Hi Daniel, Regarding #1, I instrumented our DRM driver and compared the debug output between Xorg and Wayland login screen, since the same symptom occurs there. For Xorg (on Ubuntu 16.04), by the time the login screen shows up, I only see one request for a FB. For Wayland (on Ubuntu 17.10), when the login screen tries to come up I see the following sequence: FB 1 (prepare_fb) FB 2 (prepare_fb) FB 1 (cleanup_fb) FB 3 (prepare_fb) FB 2 (cleanup_fb) Now FB 1 and 2 are freed and the login screen presumably is displayed on FB 3. prepare_fb is where the surface gets pinned, and cleanup_fb is where it gets unpinned. So at one point in this sequence, the user mode is attempting to have 2 surfaces pinned. I'm guessing it doesn't want to give up the first FB until it knows the 2nd one is available. I can work around this one on my end, but I'd like to confirm that this behavior is from the user mode. It is possible that I goofed on my end, so I wanted to be sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722897 Title: Ubuntu Wayland seems to be allocating 2-3 framebuffer sized surfaces (more than Xorg) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1722897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722897] Re: Ubuntu Wayland seems to be allocating 2-3 framebuffer sized surfaces (more than Xorg)
Hi Daniel, Regarding #2, I'd like to know how the pitch is derived so I can compensate for it by not exposing modes that can take us outside of the memory limits. Since ours is a virtual device, a "mode" is like a surface. Can you point me to the code where this pitch is determined? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722897 Title: Ubuntu Wayland seems to be allocating 2-3 framebuffer sized surfaces (more than Xorg) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1722897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722897] [NEW] Unexpected behavior with Wayland desktop
Public bug reported: I'm fixing an issue with drm/vmwgfx on 17.10 Wayland desktop, and I'd like to chat with someone about how Ubuntu Wayland works. Specifically, when a VM is configured to have 4MB of GPU memory, we have trouble setting modes above 1024x768@32bpp even though there's technically enough GPU memory to handle the framebuffer. This does not happen with Ubuntu 17.10 Xorg desktop. >From what I can see there are two things: 1. Ubuntu Wayland seems to be allocated 2-3 framebuffer sized surfaces. Is it doing triple-buffering? 2. For certain modes, e.g. 1360x768 and 800x600, the pitch coming into .create_fb is greater than mode->width * bytes-per-pixel. For instance, for 800x600@32bpp, the requested pitch is 3328 instead of 3200. These two behaviors is different from what we assumed for low memory configurations, and so is causing some issues. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 Uname: Linux 4.13.0-syeh-v4.13 x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 12:50:08 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2017-10-03 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-username-v4.13 root=UUID=e5e24738-af43-4671-9595-cccd3f4c77b8 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet modprobe.blacklist=vmwgfx kgdboc=ttyS1,115200 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2017 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 11 12:38:36 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVMware VMware Virtual USB Mouse MOUSE, id 7 inputVirtualPS/2 VMware VMMouse MOUSE, id 8 inputVirtualPS/2 VMware VMMouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory vmware(0): Failed to open drm. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722897 Title: Unexpected behavior with Wayland desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693021] [NEW] Need two commits cherry-picked from Mesa main into 16.10
Public bug reported: Hi, Can we get Mesa patch (ca531aeeb120cdd) reported here ported to 16.10? https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1657296 I verified that on 16.10, Mesa-12.0.6, the provoking vertex fix is not there. thanks ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693021 Title: Need two commits cherry-picked from Mesa main into 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1693021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693021] Re: Need two commits cherry-picked from Mesa main into 16.10
Sorry, the title should've been "one commit" rather than "two commits" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693021 Title: Need two commits cherry-picked from Mesa main into 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1693021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459613] Re: connecting 2x 4k screens on a Dell XPS12 (9Q33): compiz crashed with SIGSEGV in GLTexture::matrix() from GLScreen::glPaintCompositedOutput
Hi, has anyone tried this on 16.04 with the software rasterizer
(swrast_dri.so)?
I'm seeing the same crash with with four 2560x1600 displays on Compiz
0.9.12.2.
The crash happens in libopengl.so when it tries to deference "priv"
const GLTexture::Matrix &
GLTexture::matrix () const
{
return priv->matrix;
}
In GDB, it's clear that "priv" is pointing to an invalid memory
location.
"Copy to Texture" is set to ON by default, and I've verified it with the
configuration manager. The same configuration works with a HW
accelerated driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1459613
Title:
connecting 2x 4k screens on a Dell XPS12 (9Q33): compiz crashed with
SIGSEGV in GLTexture::matrix() from GLScreen::glPaintCompositedOutput
To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1459613/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657296] [NEW] Need two commits cherry-picked from Mesa main into 16.04
Public bug reported: Hi, On Ubuntu 16.04, VMWare customers are running into a couple of issues: 1. Any app that uses glGenMipmap command will not work properly or crash (https://communities.vmware.com/thread/537924) 2. vmwgfx_dri.so is sending provoking vertex command when it is not supposed to. I have contacted the Mesa maintainer, but unfortunately 11.2.x is no longer being actively supported, and so I couldn't get the fixes cherry- picked over. Is there an internal process in Canonical to cherry-pick fixes over? To fix the two defects above, please cherry pick the following two commits from Mesa main: 7988513ac3d86ba367fbe44e73fe483ff96aaa29 ca531aeeb120cdd --- 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) libgl1-mesa-dri: Installed: 11.2.0-1ubuntu2.2 Candidate: 11.2.0-1ubuntu2.2 Version table: *** 11.2.0-1ubuntu2.2 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 11.2.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) Google Earth will run into the glGenMipmap issue, i.e. dmesg will show "Unsupported command" I'm not sure if the 2nd issue is observable without a debug build of VMWare software... 4) Through internal testing, the two commits above should the issues mentioned. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657296 Title: Need two commits cherry-picked from Mesa main into 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1657296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor
This also fixes a defect we are seeing in a VMWare guest with Ubuntu 16.10. The issue was wallpaper does not get resized when changing to a higher desktop resolution, leaving a black border around the wallpaper, and corruption occurs when when dragging a window over that black border. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626935 Title: [yakkety] desktop is black and/or flickering after plugging in a second monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1626935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550090] Re: linux-image-3.19.0-51-generic fails to boot to desktop under VMWare Player
This sounds like it's related to https://bugs.launchpad.net/ubuntu/wily/+source/linux/+bug/1548587 that had a fix yesterday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550090 Title: linux-image-3.19.0-51-generic fails to boot to desktop under VMWare Player To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1550090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491913] Re: Force high gfx mode with UNITY_LOW_GFX_MODE == 0
Thanks! Verified on trusty-proposed. This fix works for me. However, I've noticed that on 14.04, Unity seems to start in low graphics mode again. This fix has been released, right? https://bugs.launchpad.net/unity/+bug/1491555 Maybe there's something wrong with my configuration. I'll poke around a bit more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491913 Title: Force high gfx mode with UNITY_LOW_GFX_MODE == 0 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1491913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491913] Re: Force high gfx mode with UNITY_LOW_GFX_MODE == 0
Ah, you're right. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491913 Title: Force high gfx mode with UNITY_LOW_GFX_MODE == 0 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1491913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491555] Re: Unity unnecessarily goes to low graphics mode
Hi, can I request this patch to be backported to 14.04 here or should I file another bug for it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491555 Title: Unity unnecessarily goes to low graphics mode To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1491555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
