Bug#839239: xserver-xorg-core: slight tearing with Intel modesetting driver
Package: xserver-xorg-core Version: 2:1.20.0-2 Followup-For: Bug #839239 This issue still exists in the latest version. It should be noted that this issue is (usually) papered over if you have window compositing enabled. The root cause is obviously that rectangular blits are being decomposed (by glamor? By OpenGL itself?) into two triangles, rendered sequentially. Thus, there is a brief window of time where half of the window frame is filled with new pixels (just drawn by the first triangle), and the other half contains old pixels (shorly to be overdrawn by the second triangle). The result is a diagonal "tear" across the window where the triangle edges meet. Microsoft made this mistake over a decade ago when they first tried to leverage Direct3D for their video player. It looked awful then, too. If you have a keyboard-driven window manager (such as i3 or awesome), this is fairly easy to see: - If you have it enabled, disable window compositing. - Create two windows -- one containing mostly light-color imagery, the other mostly dark imagery. - Resize both windows to full screen. - Using the window manager's keyboard shortcuts, cycle between the two windows. If you hold down the keyboard shortcut, the keyboard's auto-repeat will usually kick in and rapidly ping-pong between the two windows. The diagonal "tear" should become apparent. Note also that, if you resize the window, the "tear" follows the diagonal axis of the window. Thank you for your attention to this matter. Schwab -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 4 -rw-r--r-- 1 root root 149 Jul 18 2017 20-intel.conf.disabled /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27) Xorg X server log files on system: -- -rw-r--r-- 1 root root 43481 Jun 12 15:20 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 6.022] X.Org X Server 1.20.0 X Protocol Version 11, Revision 0 [ 6.022] Build Operating System: Linux 4.9.0-6-amd64 x86_64 Debian [ 6.022] Current Operating System: Linux walkies 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64 [ 6.022] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-2-amd64 root=UUID=c83db6d8-15bf-493f-9339-a9d6129a7992 ro quiet [ 6.022] Build Date: 24 May 2018 04:23:27PM [ 6.022] xorg-server 2:1.20.0-2 (https://www.debian.org/support) [ 6.022] Current version of pixman: 0.34.0 [ 6.022]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 6.022] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 6.022] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 12 12:52:19 2018 [ 6.023] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 6.024] (==) No Layout section. Using the first Screen section. [ 6.024] (==) No screen section available. Using defaults. [ 6.024] (**) |-->Screen "Default Screen Section" (0) [ 6.024] (**) | |-->Monitor "" [ 6.025] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 6.025] (==) Automatically adding devices [ 6.025] (==) Automatically enabling devices [ 6.025] (==) Automatically adding GPU devices [ 6.025] (==) Max clients allowed: 256, resource mask: 0x1f [ 6.026] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 6.026]Entry deleted from font path. [ 6.031] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 6.031] (==) ModulePath set to "/usr/lib/xorg/modules" [ 6.031] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 6.031] (II) Loader magic: 0x55bae1604de0 [ 6.031] (II) Module ABI versions: [
Bug#833959: xserver-xorg-video-intel: Rendering Performance Impacted
On Mon, Aug 15, 2016 at 06:46:21PM +0900, Michel Dänzer wrote: > On 11/08/16 06:34 AM, Leo L. Schwab wrote: > > Package: xserver-xorg-video-intel > > Version: 2:2.99.917+git20160706-1 > > Severity: important > > > > Dear Maintainer, > > > > Since updating to the latest Intel driver, I've noted rendering > > performance has suffered in some applications. > > As you can see in the Xorg log file, you're no longer using the intel > driver. > Well, that's embarrassing. Should I refile against xserver-xorg-core, which contains the 'glamor' driver? > FWIW, https://patchwork.freedesktop.org/patch/105129/ should help with > this particular issue. > Thank you kindly. Schwab
Bug#833959: xserver-xorg-video-intel: Rendering Performance Impacted
Package: xserver-xorg-video-intel Version: 2:2.99.917+git20160706-1 Severity: important Dear Maintainer, Since updating to the latest Intel driver, I've noted rendering performance has suffered in some applications. I've finally identified a program that reliably exhibits the issue -- 'phosphor' from the xscreensaver package. To reproduce: - Run phosphor by hand: /usr/lib/xscreensaver/phosphor - Wait for the cursor to arrive at the bottom of the window. When the "terminal" scrolls, rendering performance tanks immediately. This is doubtless due to the full-window fade effect being applied, which has now become very slow. This slowness was not present in previous driver versions. The system is a Thinkpad X1 Carbon (Gen.3), 1440p display. 'glxinfo' reports the GPU as Intel HD Graphics 5500 (Broadwell GT2). I have xscreensaver v5.34-2 installed. I used to write graphics drivers back in the day, so I can probably answer obscure questions and run tests. Thanks, Schwab -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.0 20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18) Xorg X server log files on system: -- -rw-r--r-- 1 root root 31415 Aug 4 16:48 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 4.376] X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 4.376] X Protocol Version 11, Revision 0 [ 4.376] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [ 4.376] Current Operating System: Linux walkies 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64 [ 4.376] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64 root=UUID=c83db6d8-15bf-493f-9339-a9d6129a7992 ro quiet [ 4.376] Build Date: 20 July 2016 05:14:41AM [ 4.376] xorg-server 2:1.18.4-1 (http://www.debian.org/support) [ 4.376] Current version of pixman: 0.33.6 [ 4.376]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 4.376] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 4.377] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 4 16:48:23 2016 [ 4.377] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 4.378] (==) No Layout section. Using the first Screen section. [ 4.378] (==) No screen section available. Using defaults. [ 4.378] (**) |-->Screen "Default Screen Section" (0) [ 4.378] (**) | |-->Monitor "" [ 4.379] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 4.379] (==) Automatically adding devices [ 4.379] (==) Automatically enabling devices [ 4.379] (==) Automatically adding GPU devices [ 4.379] (==) Max clients allowed: 256, resource mask: 0x1f [ 4.380] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 4.380]Entry deleted from font path. [ 4.381] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 4.381] (==) ModulePath set to "/usr/lib/xorg/modules" [ 4.381] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 4.381] (II) Loader magic: 0x55b2597b7dc0 [ 4.381] (II) Module ABI versions: [ 4.381]X.Org ANSI C Emulation: 0.4 [ 4.381]X.Org Video Driver: 20.0 [ 4.381]X.Org XInput driver : 22.1 [ 4.381]X.Org Server Extension : 9.0 [ 4.382] (++) using VT number 7 [ 4.382] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 4.382] (II) xfree86: Adding drm device (/dev/dri/card0) [ 4.383] (--) PCI:*(0:0:2:0) 8086:1616:17aa:2227 rev 9, Mem @ 0xe000/16777216, 0xc000/536870912, I/O @ 0x3000/64, BIOS @
Bug#560126: xserver-xorg-video-radeon: Launching GL Apps Corrupts System
On Wed, Dec 09, 2009 at 07:45:35AM +0100, Brice Goglin wrote: Leo L. Schwab wrote: I've upgraded to the 'unstable' mesa libraries, and to the 2.6.32-rc8 kernel. Same problems. You may try upgrading to experimental now... Those were the latest available versions that I could find via packages.debian.org. When did this problem start? What did you upgrade when it started? This is basically a virgin 'testing' install. The machine is a Sony VAIO VGN-S150 laptop. This machine was decommissioned about two years ago when the keyboard inexplicably died. Prior to that, it was running Debian 'unstable' on a daily basis just fine, including GL acceleration. The keyboard just as inexplicably came back to life recently, and I've been experimenting with various desktops as a prelude to gifting it to my mother. But then this corruption issue surfaced. It's a Sony, so I suppose it's possible the machine has traded a broken keyboard for a broken graphics chip (is there a way to test this?), but it has never been subjected to any abuse. It also passes MemTest86+ without issue, so it would not seem to be a problem with flaky memory. Since nobody else has ever reported such a critical problem (while the radeon driver has many users), I suggest your check your installation (with debsums for instance) and maybe check your hardware as well (memtest, smartctl, is there some sort of memtest for video?). The laptop in question isn't being used for anything (yet), so I can subject it to any form of diagnostic abuse you choose :-). Something strange is going on here... I wholeheartedly agree. Thanks, Schwab -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560126: xserver-xorg-video-radeon: Launching GL Apps Corrupts System
Further information: - An extended 'smartctl' test revealed no errors. So it's probably not the disk. - 'debsums -s' reported errors for a couple of files in OpenOffice; everything else was fine. I also did some fiddling with options in xorg.conf this morning. Setting AGPMode to 1 does not improve behavior. Setting AGPFastWrites to False does not improve behavior. The system still goes to pieces when GL kicks in. Setting DRI to False improves things -- GL acceleration is disabled, but the system remains stable. Schwab -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#337650: x11-common: run_parts utility misused in /etc/X11/Xsession?
Package: x11-common Version: 6.8.2.dfsg.1-4 Followup-For: Bug #337650 I too have encountered the same problem. I was trying to get 'xscreensaver' to launch on session start, but it was never invoked no matter where I put the command (.xsession, .Xsession, .gnomerc). After poring over the startup scripts, I found the same culprit as Mr. Farrauto, but for a different reason. 'run_parts' is intended to actually execute the scripts in a given directory. However, /etc/X11/Xsession (and /etc/gdm/Xsession as well, BTW) want the scripts *enumerated*, not run. This is because Xsession sources the scripts so that they can pass information between each other via shell/environment variables. Thus, it would appear that run_parts should be passed the '--list' argument to get the desired behavior. Thus, in the files /etc/X11/Xsession and /etc/gdm/Xsession, the line: SESSIONFILES=$(run_parts $SYSSESSIONDIR) should probably be changed to: SESSIONFILES=$(run_parts --list $SYSSESSIONDIR) Schwab -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.12 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages x11-common depends on: ii debconf 1.4.51 Debian configuration management sy ii debianutils 2.15.1 Miscellaneous utilities specific t ii lsb-base 3.0-9 Linux Standard Base 3.0 init scrip -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
