You are not logged in.

#1 2016-01-10 23:50:51

Fullmetal5
Member
Registered: 2015-05-02
Posts: 7

Display driver causing crashes

Recently I built a new computer and after installing Arch Linux on it I got a few error messages on boot that looked something like this:

[drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun

These error messages would appear just after systemd starts when it refreshes and syncs my two monitors.
At first I just ignored the errors but I discovered that when I locked my computer (ctrl-alt-L) and let it sit for a while that it would crash back out to my desktop with the KDE error handling window.
If I continued to use the computer after that and moved windows between the monitors plasma would entirely crash and all my open windows would loose their look and feel but remain open.
When this happened in dmesg I would get:

[29775.171267] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
[29775.205020] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B
[29775.205026] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
[29799.060726] kscreen_backend[13242]: segfault at 10 ip 00007f87cae54490 sp 00007ffea2e3f710 error 4 in KSC_XRandR.so[7f87cae3a000+24000]
[29799.063853] kactivitymanage[13247]: segfault at 7fe27aaa0cd0 ip 00007fe260064291 sp 00007fffd7958ce8 error 4 in libQt5Sql.so.5.5.1[7fe260050000+3f000]
[29799.297837] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
[29799.356606] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B
[29799.356610] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun

Using ctrl-alt-del and logging out and back in would fix everything until I locked the computer again and let it sit.
My initial solution to this was to build the latest kernel version, so I went and built the kernel from commit 751e5f5c753e8d447bcf89f9e96b9616ac081628 and applied it.
This caused the errors I saw when systemd refreshed the screen to no longer appear, but apart from that though nothing else changed.
At this time I discovered that if I unplugged my second monitor [VGA] that the errors would no longer appear.

System Specs:
CPU: i7-4790K
Motherboard: MSI H97 PC MATE ATX
1st Monitor: ASUS VS248H-P [HDMI]
2nd Monitor: Generic Dell Monitor [VGA]

EDIT: formatting of error messages

Thanks in advance.

Last edited by Fullmetal5 (2016-01-10 23:54:10)

Offline

#2 2016-02-11 10:37:18

Wilco
Member
Registered: 2008-11-09
Posts: 440

Re: Display driver causing crashes

Seeing the same problems. After locking the screen in KDE after a few minutes it crashes. Also seeing the kactivitymanage crash and I'm also using the intel drivers, but with only one monitor.

Not sure if this is a KDE or Intel drivers problem because I saw similar errors before in dmesg, without a crash.

Offline

Board footer

Powered by FluxBB