After booting into 4.4.13-desktop-1.mga5 screen starts flickering/going blank for second when switching mouse from one monitor to second monitor. Sometimes screen stays black after leaving it with mouse and moving mouse back restores screen. This is NOT happening with 4.1.15-2.mga5 kernel *** ENV ***: Mageia: Mageia release 5 (Official) for x86_64 Kernel: 4.4.13-desktop-1.mga5 #1 SMP Fri Jun 10 12:16:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux GUI:mate-desktop-1.8.1-4.mga5 MB: ASUS P7H55-M PRO CPU: Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz X: x11-server-xorg-1.16.4-2.1.mga5 #lspci -s 00:02.0 -v 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 8383 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at f7800000 (64-bit, non-prefetchable) [size=4M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at dc00 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 #cat /etc/X11/xorg.conf Section "Module" Load "v4l" # Video for Linux EndSection Section "Monitor" Identifier "VGA" VendorName "LG" ModelName "E2240" HorizSync 30-83 VertRefresh 56-75 # Monitor preferred modeline (60.0 Hz vsync, 67.5 kHz hsync, ratio 16/9, 102 dpi) ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync EndSection Section "Monitor" Identifier "HDMI" VendorName "ViewSonic" ModelName "VX2245wm" HorizSync 30-82 VertRefresh 50-75 Option "RightOf" "VGA" # Monitor preferred modeline (60.0 Hz vsync, 65.3 kHz hsync, ratio 16/10, 90 dpi) ModeLine "1680x1050" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 +hsync -vsync EndSection Section "Device" Identifier "IntelHD" VendorName "Intel Corporation" BoardName "i915" Driver "intel" BusID "PCI:0:2:0" Option "Monitor-HDMI1" "HDMI" Option "Monitor-VGA1" "VGA" EndSection Section "Screen" Identifier "screen0" Device "IntelHD" Monitor "VGA" EndSection Section "ServerLayout" Identifier "DualScreen" Screen "screen0" EndSection *** Related Logs entries*** dmesg: [ 23.253059] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [ 23.253192] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [ 24.185645] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun [ 24.185676] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder B FIFO underrun [ 43.650849] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun [ 43.650985] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder B FIFO underrun Steps to Reproduce: Boot to 4.4.13-desktop-1.mga5 kernel
Do you not have this problem when booting into a previous kernel?
Keywords: (none) => NEEDINFOCC: (none) => marja11Assignee: bugsquad => tmb
This is NOT happening with (previous) 4.1.15-2.mga5 kernel (I am actually using this kernel since flickering is quite anoying with new kernel)
This is actually kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=95461 They are suggesting that all drm/i915 bug tracking happens at http://bugs.freedesktop.org/ Here is relevant post: https://bugs.freedesktop.org/show_bug.cgi?id=94605 Will continue following bug there but this listing can serve as reference for others. Once fixed I will mark as RESOLVED here.
Keywords: NEEDINFO => UPSTREAM
Mass-reassigning all bugs with "kernel" in the summary that are still assigned to tmb (or wrongly assigned to someone with "tmb" in his e-mail address) to the kernel packagers group, but without adding "kernel" to the SRPM field. Please reassign if needed, or add kernel to the SRPM field if this is correct.
Assignee: tmb => kernel
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=14867
Hi Spicer, Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja
Component: Release (media or process) => RPM Packages
@ Spricer: No reply, so closing as OLD since Mageia 5 is no longer maintained. ==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==
Resolution: (none) => OLDStatus: NEW => RESOLVED