Bug#887437: x11-common: When I attempt any resolution over 1920x1200 text is unreadable
Package: x11-common Version: 1:7.7+19 Severity: important Dear Maintainer, Trying to use a 4K monitor gets garbled text etc. Tried 3 different graphics cards that handles over 1920x1200 all with valid drivers. Any attempts at a resolution over 1920x1200 (such as 2560x1440 or 3840x2180) garbles text and other finer details. The instant the resolution is below it is chrystal clear. -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-4-amd64 (SMP w/3 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages x11-common depends on: ii lsb-base 9.20161125 x11-common recommends no packages. x11-common suggests no packages. -- no debconf information
Bug#887444: mesa: Please build with optimization level -O1 on sh3 and sh4
Source: mesa Version: 17.3.2-1 Severity: normal Tags: patch User: debian-sup...@lists.debian.org Usertags: sh3 sh4 Hello! mesa currently FTBFS on sh4 (and consequently sh3) due to a bug in upstream gcc which hasn't been resolved yet [1]. To work around this bug, it's enough to add "-O1" to the extra C/C++ build flags on sh3/sh4 which sets "-freorder-blocks-algorithm=simple" Just passing "-freorder-blocks-algorithm=simple" doesn't unfor- tunately work as gcc would just crash the qemu buildd. This might be a bug in qemu. For the time being, we will be happy with just passing "-O1" to fix the FTBFS. Patch attached. Thanks, Adrian > [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83143 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 diff -Nru old/mesa-17.3.2/debian/rules new/mesa-17.3.2/debian/rules --- old/mesa-17.3.2/debian/rules2018-01-16 16:00:16.0 +0100 +++ new/mesa-17.3.2/debian/rules2018-01-16 16:50:14.789910395 +0100 @@ -10,13 +10,19 @@ DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS) DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU) -ifeq (,$(filter $(DEB_HOST_ARCH), armhf)) +ifeq (,$(filter $(DEB_HOST_ARCH), armhf sh3 sh4)) buildflags = \ $(shell DEB_CFLAGS_MAINT_APPEND=-Wall DEB_CXXFLAGS_MAINT_APPEND=-Wall dpkg-buildflags --export=configure) else -# Workaround for a variant of LP: #725126 -buildflags = \ + ifneq (,$(filter $(DEB_HOST_ARCH), armhf)) + # Workaround for a variant of LP: #725126 + buildflags = \ $(shell DEB_CFLAGS_MAINT_APPEND="-Wall -fno-optimize-sibling-calls" DEB_CXXFLAGS_MAINT_APPEND="-Wall -fno-optimize-sibling-calls" dpkg-buildflags --export=configure) + else + # Workaround for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83143 + buildflags = \ + $(shell DEB_CFLAGS_MAINT_APPEND="-Wall -O1" DEB_CXXFLAGS_MAINT_APPEND="-Wall -O1" dpkg-buildflags --export=configure) + endif endif # keep a list of files we don't install (yet), but since it's a bit
Bug#879857: marked as done (xserver-xorg-video-intel: [i915] GPU hang after every suspend or hibernate on Debian 9 stretch)
Your message dated Wed, 17 Jan 2018 09:43:20 +0200 with message-id <72e548a2-a773-ae39-c741-b5eedd2ba...@debian.org> and subject line Re: Bug#879857: xserver-xorg-video-intel: [i915] GPU hang after every suspend or hibernate on Debian 9 stretch has caused the Debian Bug report #879857, regarding xserver-xorg-video-intel: [i915] GPU hang after every suspend or hibernate on Debian 9 stretch to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 879857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-intel Version: 2:2.99.917+git20161206-1 Severity: grave Justification: causes non-serious data loss Dear Maintainer, I am affected by this issue on a Wortmann/Terra Mobile N360-11 notebook computer with an Intel i915 graphics chipset. Every time I use the suspend or hibernate sleep states, the system boots and resumes as expected (I can see the screen exactly the way before I pressed the hibernate button). After one or two seconds, however, the display manager is restarted and I am presented with a blac screen briefly, followed by the regular login screen. I use Xfce4 with lightdm, btw. On the login screen, I can immediately log in as the same user that triggered the hibernation, and use the computer just fine. After logging in, however, all applications are closed and all unsaved data is lost. The consoles (TTY1, TTY2) are not affected. The behaviour is reproducible every time I suspend or hibernate, also when hibernation is triggered automatically, e.g. by a low battery level. After such a "failed" resume, I can find the following error message in the output of dmesg: > [drm] GPU HANG: ecode 8:0:0x5fa3bf07, in Xorg [641], reason: Hang on render > ring, action: reset > [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, > including userspace. > [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> > DRM/Intel > [drm] drm/i915 developers can then reassign to the right component if it's > not a kernel issue. > [drm] The gpu crash dump is required to analyze gpu hangs, so please always > attach it. > [drm] GPU crash dump saved to /sys/class/drm/card0/error > drm/i915: Resetting chip after gpu hang > drm/i915: Resetting chip after gpu hang uname -a: > Linux N360-11 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 > GNU/Linux Further information: Note that I have a Debian testing live CD at hand, running kernel 4.11. The live CD is not affected by this issue. I have read the description of bug #637511 and while this is an old bug, it is similar in the way that the system is not affected at all after a display manager restart. Also, the error message reported here ist very similar to what I see: https://bugs.freedesktop.org/show_bug.cgi?id=93510 Please let me know what further information you require to investigate this issue, if any. Best regards, Ferdinand -- 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 Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) /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.9.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28) Xorg X server log files on system: -- -rw-r--r-- 1 root root 32263 Oct 22 02:55 /var/log/Xorg.1.log -rw-r--r-- 1 root root 38483 Oct 26 16:06 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 1688.281] X.Org X Server 1.19.2 Release Date: 2017-03-02 [ 1688.281] X Protocol Version 11, Revision 0 [ 1688.281] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian [ 1688.281] Current Operating System: Linux N360-11 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 [ 1688.281] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 root=/dev/sda2 ro quiet [ 1688.281] Build Date: 16 October 2017 08:19:45AM [ 1688.281] xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support) [ 1688.281] Current version of pixman: 0.34.0 [ 1688.281]Before repo
Bug#877736: marked as done (xserver-xorg-video-intel: Xorg crashes with hardware acceleration on)
Your message dated Wed, 17 Jan 2018 09:48:04 +0200 with message-id and subject line Re: Bug#877736: xserver-xorg-video-intel: Xorg crashes with hardware acceleration on has caused the Debian Bug report #877736, regarding xserver-xorg-video-intel: Xorg crashes with hardware acceleration on to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 877736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-intel Version: 2:2.99.917+git20161206-1 Severity: critical Justification: breaks the whole system Dear Maintainer, After upgrading to sid, GDM was not able to start. The boot process stopped with the message: ``` [FAILED] Failed to start User Manager for UID 117. See 'systemctl status user@117.service' for details. ``` The output of the recommented command was not very useful, though. Neither was `journalct -xb`. I managed to get a shell by starting in recovery mode and installed lightdm. This time, the error was easier to find in the Xorg logs. Unfortunatelly I didn't copy the contents of the file, but the relevant lines were: ``` (WW) glamor0: Failed to get GLSL version (EE) modeset(0): Failed to initialize glamor at ScreenInit() time. ``` If it is really important, I can try to reproduce the error again and copy the logs. I managed to work around this issue by creating a new xorg.conf file, disabling acceleration: ``` Section "Device" Identifier "Intel Graphics" Driver "intel" Option "NoAccel" "True" EndSection ``` With that, the computer booted up fine using lightdm and I could use it again. I didn't confirm if GDM is working, but lightdm and slim are, for sure. Please let me know if there's any other information I can give to help track this down. -- 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 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) Xorg X server configuration file status: -rw-r--r-- 1 root root 105 Oct 5 00:41 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section "Device" Identifier "Intel Graphics" Driver "intel" Option "NoAccel" "True" EndSection /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.13.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 6.4.0 20170920 (Debian 6.4.0-7)) #1 SMP Debian 4.13.4-1 (2017-10-01) Xorg X server log files on system: -- -rw-r--r-- 1 amieiro amieiro 151197 Oct 4 21:08 /home/amieiro/.local/share/xorg/Xorg.0.log -rw-r--r-- 1 rootroot 24583 Oct 5 00:48 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [56.352] X.Org X Server 1.19.3 Release Date: 2017-03-15 [56.428] X Protocol Version 11, Revision 0 [56.428] Build Operating System: Linux 4.9.0-3-amd64 x86_64 Debian [56.428] Current Operating System: Linux stallman 4.13.0-1-amd64 #1 SMP Debian 4.13.4-1 (2017-10-01) x86_64 [56.428] Kernel command line: BOOT_IMAGE=/vmlinuz-4.13.0-1-amd64 root=/dev/mapper/stallman--vg-root ro quiet [56.428] Build Date: 07 July 2017 06:22:09AM [56.428] xorg-server 2:1.19.3-2 (https://www.debian.org/support) [56.428] Current version of pixman: 0.34.0 [56.428]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [56.428] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [56.429] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 5 00:44:57 2017 [56.824] (==) Using config file: "/etc/X11/xorg.conf" [56.824] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [57.100] (==) No Layout section. Using the first Screen section. [57.100] (==) No screen section available. Using defaults. [57.100] (**) |-->Screen "Default Screen Section" (0) [57.100] (**) | |-->Monitor "" [57.108] (==) No device specified for screen "Default Screen Section". Using the first device s
