FS#44779 - [linux] Login screen flashes after upgrading to linux 4.0.1-1, drm errors
Attached to Project:
Arch Linux
Opened by Nybble (wuxb45) - Wednesday, 29 April 2015, 16:06 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 02 August 2015, 16:48 GMT
Opened by Nybble (wuxb45) - Wednesday, 29 April 2015, 16:06 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 02 August 2015, 16:48 GMT
|
Details
Description:
After upgrading linux 4.0.1(x86_64) kernel. The bottom half of the login screen flashes (gdm). However the problem disappeared after successful logged in. The screen does not flash before or after the login screen. dmesg show such error messages: [ 5.954975] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [ 5.955019] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [ 5.955043] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun Additional info: * package version(s) linux 4.0.1-1 gnome-shell 3.16.1-2 gdm 3.16.1.1-1 * config and/or log files etc. thinkpad x220 Steps to reproduce: |
This task depends upon
With GDM 3.16, Wayland is used as the display server, the actual user session
is still backed by X. That may explain the disappearance of the problem after login.
On LKML I found this one https://lkml.org/lkml/2015/2/11/78 , which, by the log,
is also on a Sandy Bridge system.
same packages / kernel.
Related with patch FS# https://bugs.archlinux.org/task/43848
uncomment in /etc/gdm/custom.conf the line
WaylandEnable=false
Details:
https://bugzilla.redhat.com/show_bug.cgi?id=1199890
FS#44636Else I have issues under Chome, which sometimes have flickerings on forms while load webpages (very rare).
https://lkml.org/lkml/2015/4/11/202
linux 4.0.4-2
wayland 1.8.0-1
gdm 3.16.1.1-2
xorg-server 1.17.1-5
By the way, it doesn't occur if the machine is connected to a dock with a second monitor.
Temporally solved by installing lts kernel.
I'm using a self compiled vanilla-kernel kernel and upgraded on 4.1.0 during the weekend, the problem is fixed and everything works. So I assume this will be fixed, as soons as "linux >= 4.1.0-1" becomes stable for Archlinux.