Bug 14869 - kernel/intel: [drm:intel_* FIFO underrun
Summary: kernel/intel: [drm:intel_* FIFO underrun
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard: 5beta2 5rc
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2014-12-21 20:48 CET by Marja Van Waes
Modified: 2016-08-28 10:02 CEST (History)
6 users (show)

See Also:
Source RPM: kernel-desktop-4.1.7-1.mga5
CVE:
Status comment:


Attachments
journalctl -b output (117.59 KB, text/plain)
2014-12-21 20:48 CET, Marja Van Waes
Details
testing h/w (4.02 KB, text/plain)
2014-12-25 07:22 CET, Ben McMonagle
Details
dmesg | grep drm (1.11 KB, text/plain)
2015-01-07 22:11 CET, Rémi Verschelde
Details
journalctl -a | grep underrun (14.39 KB, text/plain)
2015-04-16 18:55 CEST, Marja Van Waes
Details
File sections that have errors in the same functions (1.29 KB, text/plain)
2015-05-07 17:28 CEST, Mauricio Andrés Bustamante Viveros
Details

Description Marja Van Waes 2014-12-21 20:48:07 CET
Created attachment 5750 [details]
journalctl -b output

+++ This bug was initially created as a clone of Bug #14867 +++

Similar issue as bug 14867, now on
https://wiki.mageia.org/en/User:Marja/QA/Hardware#Lenovo_ThinkPad_L530 

The error messages are different:

[root@5beta2_64bits u]# journalctl -b | grep underrun
Dec 21 20:36:54 5beta2_64bits kernel: [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A
Dec 21 20:36:54 5beta2_64bits kernel: [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun
[root@5beta2_64bits u]#

I just did a fresh install with the 2nd 4th round pre-5beta2 classical 64bits iso, chose all DEs and Grub2, but other than that everything was default and I didn't change any settings.
Marja Van Waes 2014-12-21 20:48:19 CET

Whiteboard: (none) => 5beta2

Comment 1 Ben McMonagle 2014-12-25 07:22:41 CET
Created attachment 5760 [details]
testing h/w

CC: (none) => westel

Comment 2 Ben McMonagle 2014-12-25 07:24:25 CET
Mageia-5-beta2-i586-DVD, Sat Dec 20 22:13:39 CET 2014

same on my hardware , see comment #1 for hardware
Marja Van Waes 2014-12-26 12:16:28 CET

Attachment 5760 mime type: application/octet-stream => text/plain

Comment 3 Marja Van Waes 2014-12-26 12:20:28 CET
(In reply to ben mcmonagle from comment #2)
> Mageia-5-beta2-i586-DVD, Sat Dec 20 22:13:39 CET 2014
> 
> same on my hardware , see comment #1 for hardware

@ Ben

That's an Intel 810 and later card, too, but you don't seem to have a ThinkPad, correct? (I was wondering whether it was ThinkPad-related)
Comment 4 Marja Van Waes 2014-12-26 12:25:42 CET
Btw, I've been having hard crashes (not even alt+sysrq keycombinations work any more, there is nothing in the logs) can they be related?

They did at least happen several times when moving the mouse and clicking (or about to click) on something. It maybe even be that I was always doing that when the system froze. It did at least happen in FF and TB, but also outside those applications.
 
This never happened with 3.17* kernels.
Comment 5 Ben McMonagle 2014-12-27 04:27:01 CET
I have this problem on 2 desktop systems, both are i5 quad core units, 
both with asus M/b, 8G, using onboard video.
the older unit is my home one, the undrerun text only occurs when booting on the Mga5 32+64  systems, 
Mga4 32+64 does not display the underrun, there appear to be no operation issues during normal use, except that dbus startup problem.

my other newer unit is Mga4-64 only, no operation issues with it at all.
Comment 6 Marja Van Waes 2014-12-28 19:16:01 CET
(In reply to Marja van Waes from comment #4)
> Btw, I've been having hard crashes (not even alt+sysrq keycombinations work
> any more, there is nothing in the logs) can they be related?
> 

Happened again after I had started "mgasync" in a konsole (that does nothing but sync my local mirror on a USB disk with a public Mageia mirror), and walked away to do some other things.

This time, I see a screen full of text, ending with:
Kernel panic - not syncing: Fatal exception in interrupt
Kernel Offset: (can't read all that follows)
drm_kms_helper: panic occurred, switching back to text console

Well, drm does sound related to drm, to me ;-)

Again not even Alt+SysRq keycombinations didn't work and there is nothing in the logs at all. 

Sorry for the bad screenshot, I won't make it worse by compressing it to be able to attach it:

http://waesvanm.home.xs4all.nl/Mageia/screenshots/Bug_14869_20141228_184854.jpg
Marja Van Waes 2014-12-28 19:59:38 CET

Source RPM: kernel-desktop-3.18.1-1.mga5 => kernel-desktop-3.18.1-2.mga5

Comment 7 Marja Van Waes 2014-12-31 15:15:05 CET
same error messages still there, don't know yet about the crashes.

Source RPM: kernel-desktop-3.18.1-2.mga5 => kernel-desktop-3.18.1-3.mga5

Comment 8 Rémi Verschelde 2015-01-07 22:08:20 CET
Same issue here, it's been there for a while. It doesn't seem to have much impact on the boot, but it breaks plymouth for some seconds and that's not pretty to have such a huge "ERROR" on a black screen when booting :-)

I get:
[    2.361951] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A
[    2.361953] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun

(see attached dmesg | grep drm for context)


Seems to be related to this kernel.org report: https://bugzilla.kernel.org/show_bug.cgi?id=79261

Also: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=86478

CC: (none) => remi

Rémi Verschelde 2015-01-07 22:10:48 CET

Summary: kernel: [drm:cpt_* underruns => kernel/intel: [drm:cpt_* FIFO underrun

Comment 9 Rémi Verschelde 2015-01-07 22:11:49 CET
Created attachment 5793 [details]
dmesg | grep drm
Comment 10 Rémi Verschelde 2015-01-07 22:12:21 CET
CC'ing Thierry since it seems to be a bug with the intel driver.

CC: (none) => thierry.vignaud

Comment 11 Thomas Backlund 2015-01-08 10:38:42 CET
It is a kernel drm issue where it cant properly filter underruns, somtheing that got more exposed in 3.18 series kernels.

There is a patchset upstream 3.19... to fix this but it changes a lot of code, so I did a stripped down version that fixed the issue for Marja.

I need to either backport the filtering code or extend the stripped down version to cover more underruns or maybe switch the error to debug level...

The error should otherwise be harmless, it's more of an "informal nature"
Comment 12 Rémi Verschelde 2015-01-08 10:48:26 CET
Thanks for the update Thomas.

So maybe the "flickering" I see with plymouth is not related to this issue at all, even if it's the one displayed when it flickers? I explain:
- At boot, it starts with this FIFO underrun error (two lines on black screen), then the graphical plymouth boot starts. After two bubbles of the animation, it flickers back to the black screen with the two error lines for a couple of seconds, and then the graphical boot goes on.

If you can confirm that it's just a coincidence that we see the error message from this bug during the flickering, I'll open another bug report against plymouth or mageia-theme.
Comment 13 Marja Van Waes 2015-01-08 10:59:26 CET
(In reply to Thomas Backlund from comment #11)

> 
> There is a patchset upstream 3.19... to fix this but it changes a lot of
> code, so I did a stripped down version that fixed the issue for Marja.
> 

It fixed a similar issue - bug 14867 - on a different laptop, this error on this laptop did not get fixed ;-)
Comment 14 Marja Van Waes 2015-01-08 11:02:44 CET
@ Rémi

On this laptop, I've been having hard freezes (± daily until a few days ago) of which I was wondering whether they were related. Nothing in the logs.
Did you get any hard crashes?
Comment 15 Rémi Verschelde 2015-01-08 11:09:21 CET
@ Marja

Nope, I think what you describe in comment 4 is a symptom of another bug (that I don't experience here).
Marja Van Waes 2015-01-08 12:01:52 CET

Source RPM: kernel-desktop-3.18.1-3.mga5 => 3.18.1-desktop-4.mga5

Marja Van Waes 2015-01-08 12:04:22 CET

Source RPM: 3.18.1-desktop-4.mga5 => kernel-desktop-3.18.1-4.mga5

Thierry Vignaud 2015-01-09 07:52:03 CET

CC: thierry.vignaud => (none)

Marja Van Waes 2015-01-14 09:25:43 CET

Source RPM: kernel-desktop-3.18.1-4.mga5 => kernel-desktop-3.18.2-1.mga5

Comment 16 Marja Van Waes 2015-02-03 17:11:54 CET
Sorry, Thomas, got different but similar underruns in return :-( 


[root@DenkBlok3Cauldron5a1 marja]# uname -r
3.19.0-desktop-0.rc7.2.mga5
[root@DenkBlok3Cauldron5a1 marja]# journalctl -b | grep underrun
Feb 03 17:00:04 DenkBlok3Cauldron5a1 kernel: [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
Feb 03 17:00:04 DenkBlok3Cauldron5a1 kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
[root@DenkBlok3Cauldron5a1 marja]#

Changing the summary because I think it changed from "cpt..." to "intel..." for all, please complain if I'm wrong!!


(In reply to Rémi Verschelde from comment #15)
> @ Marja
> 
> Nope, I think what you describe in comment 4 is a symptom of another bug
> (that I don't experience here).

Yeah, you're right, it doesn't happen anymore since several weeks.

Source RPM: kernel-desktop-3.18.2-1.mga5 => kernel-desktop-3.19.0-0.rc7.2.mga5
Summary: kernel/intel: [drm:cpt_* FIFO underrun => kernel/intel: [drm:intel_* FIFO underrun

Marja Van Waes 2015-02-09 17:59:47 CET

Source RPM: kernel-desktop-3.19.0-0.rc7.2.mga5 => kernel-desktop-3.19.0-1.mga5

Comment 17 Mauricio Andrés Bustamante Viveros 2015-02-15 05:46:12 CET
I have a Compaq Presario V2030US

Intel 855GME Integrated controller
In the Mageia 5beta2 only show :

feb 09 19:05:25 sarasofia.sanpedrovalle kernel: [drm:i8xx_irq_handler] *ERROR* pipe B underrun

But i upgrade to Mageia 5beta3 this day feb 14 using the urpmi.removemedia and addmedia and after reboot i look in the journal and I get two: 

feb 14 23:11:33 sarasofia.sanpedrovalle kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
feb 14 23:11:33 sarasofia.sanpedrovalle kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

I don't know if I updated the intel driver in the febrary 9 or 10, only tonight i gets again these errors....

I think the maintainer again switch this to the debug mode

CC: (none) => neoser10

Comment 18 Marja Van Waes 2015-04-14 20:52:50 CEST
fixed since kernel-3.19.2-2.mga5

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 19 Rémi Verschelde 2015-04-14 21:04:16 CEST
Not for me:

# journalctl -b | grep underrun
avril 14 18:05:51 localhost kernel: [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
avril 14 18:05:51 localhost kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun

# uname -r
3.19.3-desktop-1.mga5

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 20 Ben McMonagle 2015-04-14 21:49:30 CEST
or for me
Comment 21 Marja Van Waes 2015-04-16 18:49:44 CEST
this is weird, I cannot imagine it is related, but after I had switched to 16bpp for bug 15493, the underruns returned... I hadn't had them since March 25


......
mrt 25 17:05:55 Mga5RC_EFI kernel: [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
mrt 25 17:05:55 Mga5RC_EFI kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
apr 16 17:57:38 Mga5RC_EFI kernel: [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
apr 16 17:57:38 Mga5RC_EFI kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
apr 16 17:57:38 Mga5RC_EFI kernel: [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
apr 16 17:57:38 Mga5RC_EFI kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
<more of the same as above, until I swtiched back to 24bpp>

tty2-6 had gone crazy, but there was nothing odd in tty1 with KDE 

I'll switch back to 16bpp again, to see whether I can reproduce it
Comment 22 Marja Van Waes 2015-04-16 18:55:57 CEST
Created attachment 6297 [details]
journalctl -a | grep underrun

with 16bpp, tty2-6 are crazy and completely unusable again

and the underruns are back
Comment 23 Mauricio Andrés Bustamante Viveros 2015-04-30 07:59:34 CEST
In the MGA4 release kernel, this fifo underrun does not shown, but in the updated kernel (installed in the MGA5RC public available) this message is again, I will try install the MGA4 release kernel (3.12.21) in a clean install, test for this message and post results
Comment 24 Rémi Verschelde 2015-04-30 09:16:56 CEST
(In reply to Mauricio Andrés Bustamante Viveros from comment #23)
> In the MGA4 release kernel, this fifo underrun does not shown, but in the
> updated kernel (installed in the MGA5RC public available) this message is
> again, I will try install the MGA4 release kernel (3.12.21) in a clean
> install, test for this message and post results

Thanks for the proposal but it's not really needed AFAICT, as per comment 11 it is established that this error shows since kernel 3.18.
Comment 25 Mauricio Andrés Bustamante Viveros 2015-05-07 17:27:12 CEST
Hello QA

This comment is informational only
I found that kernel 3.16.1 downloaded from kernel.org, configured with the .config file from 3.14 MGA4 release kernel, show the fifo underrun issue, diffing the 3.15.10 kernel files (the last kernel without problems) and the 3.16.1, see a little error in an static void function that refers to GEN2 intel graphics (attachment) because in the same file i found the same section but with boolean value false, not true as stated in the refered line, edited that boolean to false too, and only I have the set underrun reporting.
Comment 26 Mauricio Andrés Bustamante Viveros 2015-05-07 17:28:12 CEST
Created attachment 6468 [details]
File sections that have errors in the same functions
Comment 27 Samuel Verschelde 2015-05-15 17:45:54 CEST
tmb, what about patch from comment #25?

Whiteboard: 5beta2 => 5beta2 5rc

Samuel Verschelde 2015-05-15 17:46:09 CEST

Keywords: (none) => PATCH

Comment 28 Thomas Backlund 2015-05-15 21:16:35 CEST
It's not a fix, it only hides the issue
Comment 29 Mauricio Andrés Bustamante Viveros 2015-05-15 23:05:06 CEST
Really this is not a fix, the fifo underruns exist time ago, but, the kernel module maintainer, decided enable the reporting in the info level not in debug level, and this is breaking bootsplash (Plymouth), I think he want finding hardware glitches and freezes, but leave as is in a production kernel, mageia kernel maintainer must hide this fifo underrun and how??? or we must wait to upstream repair this ???
Comment 30 Thomas Backlund 2015-05-16 21:31:44 CEST
I will switch the messages to debug level so they can be accessed when needed without rebuilding kernel
Comment 31 Thomas Backlund 2015-05-27 15:03:30 CEST
Should be "fixed" / hidden as of: kernel-3.19.8-2.mga5

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

Comment 32 Rémi Verschelde 2015-09-19 12:56:59 CEST
Those are back in kernel-4.1.7-1.mga5 in Core Updates Testing.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)
Source RPM: kernel-desktop-3.19.0-1.mga5 => kernel-desktop-4.1.7-1.mga5

claire robinson 2015-11-13 11:59:53 CET

CC: (none) => eeeemail, fredjame

Comment 33 claire robinson 2015-11-13 12:00:47 CET
Reported by Fred James on QA Discuss ML. Adding him to CC.

These messages flashes by in terminal window during boot, just before login dialog screen.

[    1.012968] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
[    1.012982] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
Comment 34 Mauricio Andrés Bustamante Viveros 2015-11-14 01:46:15 CET
Hello again

I have the Compaq Presario V2030US PM064UA#ABA (that was used to test MGA5 Gnome) and a Latitude Dell 6430 (Used in my work, propietary of my work) but i can use that machine with other SATA disk to test MGA6, this Lati 6430 is Intel HD Graphics (i do not remember the model exactly) but i propose this core i5 4th gen to MGA6.

This lappy contains a intel HD Graphics, Broadcom WIFI, EFI capabilities (unknown specification) & TPM but is not used

Tomorrow i will install MGA6 from NET and report in the MGA6 QA team mailing list
Comment 35 Marja Van Waes 2016-06-24 21:03:40 CEST
Does anyone still see those underrun messages?

I haven't in a long time

[root@cldrn_64 marja]# journalctl -a | grep underrun
[root@cldrn_64 marja]# rpm -qa | grep kernel-desktop-latest
kernel-desktop-latest-4.6.2-2.mga6
[root@cldrn_64 marja]#
Comment 36 Ben McMonagle 2016-06-24 23:43:06 CEST
(In reply to Marja van Waes from comment #35)
> Does anyone still see those underrun messages?
> 
> I haven't in a long time
> 
> [root@cldrn_64 marja]# journalctl -a | grep underrun
> [root@cldrn_64 marja]# rpm -qa | grep kernel-desktop-latest
> kernel-desktop-latest-4.6.2-2.mga6
> [root@cldrn_64 marja]#

:( 

every boot up for Mga5. - UEFI, intel 810 or later, latest kernel
Comment 37 Otto Leipälä 2016-07-23 17:19:18 CEST
No errors here i assume it's fixed in newer Mageia 5 kernel builds.

journalctl -a | grep underrun
[root@localhost ozky]# rpm -qa | grep kernel-desktop-latest
kernel-desktop-latest-4.4.13-1.mga5

CC: (none) => ozkyster

Comment 38 Marja Van Waes 2016-08-26 11:42:55 CEST
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.

Assignee: tmb => kernel

Comment 39 Marja Van Waes 2016-08-28 10:02:06 CEST
(In reply to Otto Leipälä from comment #37)
> No errors here i assume it's fixed in newer Mageia 5 kernel builds.
> 
> journalctl -a | grep underrun
> [root@localhost ozky]# rpm -qa | grep kernel-desktop-latest
> kernel-desktop-latest-4.4.13-1.mga5

fixed in cauldron, too:

[root@cldrn_64 marja]# journalctl -ab | grep underrun
[root@cldrn_64 marja]# 

Closing

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.