Bug 1131914

Summary: Kernel > 3.15.x [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun
Product: [Fedora] Fedora Reporter: Benjamin Masse <bmasse>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: 504636613, ajax, bkorb, cn6uw7d02, diooktput97, gansalmon, hugh, itamar, jdennis, jonathan, kernel-maint, madhu.chinakonda, mchehab, mihai, pachoramos1, rflribeirojr, rodd, rvokal, sharlatanus, stepglenn, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 03:26:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1119868    
Attachments:
Description Flags
dmesg output none

Description Benjamin Masse 2014-08-20 09:41:39 UTC
Description of problem:
On  kernel upgrade > 3.15.3, [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun error message displays at boot time

Version-Release number of selected component (if applicable):
Any version released post 3.15.3

How reproducible:
Every boot 

Steps to Reproduce:
1. Upgrade to kernel version > 3.15.3
2. Look at boot up or sudo journalctl --this-boot | grep FIFO

Actual results:
Error message [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun

Expected results:
No error message/silent boot
Either the underlying problem is solved and the message should not display, or actually be fully addressed

Additional info:

Comment 1 Josh Boyer 2014-08-20 11:50:25 UTC
Please attach the output of dmesg.

Comment 2 Benjamin Masse 2014-08-20 11:59:52 UTC
Created attachment 928776 [details]
dmesg output

Comment 3 Benjamin Masse 2014-09-09 07:43:32 UTC
Update: kernel-3.16.2-200.fc20 adds an extra drm/i915 related error message
[drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A
[drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun

Comment 4 Reginaldo Ribeiro 2014-09-25 21:40:45 UTC
Same situation.

[18:40:19 oracle@latitude-e6430 ~]$ journalctl --this-boot | grep -i fifo
Sep 25 18:35:17 latitude-e6430 kernel: [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A
Sep 25 18:35:17 latitude-e6430 kernel: [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun

Comment 5 D. Hugh Redelmeier 2014-10-07 16:18:28 UTC
I have these messages too.

Zotac Zbox-ID18,
CPU Celeron 1007u (Ivy Bridge)
BIOS B211P011 (AMI) (latest, I think)
Fedora 20
Kernel 3.16.3-200.fc20.x86_64

dmsg | grep drm
[    1.411169] [drm] Initialized drm 1.1.0 20060810
[    1.446125] [drm] Memory usable by graphics device = 2048M
[    1.446129] [drm] Replacing VGA console driver
[    1.454769] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.454771] [drm] Driver supports precise vblank timestamp query.
[    1.551466] fbcon: inteldrmfb (fb0) is primary device
[    1.587988] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A
[    1.587989] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun
[    1.597629] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    1.611070] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[    2.722617] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[    4.070361] SELinux: initialized (dev drm, type drm), not configured for labeling

See also
https://lkml.org/lkml/2014/5/5/56
https://bugs.archlinux.org/task/40952
https://bugzilla.kernel.org/show_bug.cgi?id=79261

Comment 6 japa-fi 2014-10-12 09:15:19 UTC
Lenovo T430, integrated intel graphics.
3.16.4-200.fc20.x86_64


[bash]:~$>dmesg | grep drm
[    1.600404] [drm] Initialized drm 1.1.0 20060810
[    1.619725] [drm] Memory usable by graphics device = 2048M
[    1.619727] [drm] Replacing VGA console driver
[    1.619731] fb: switching to inteldrmfb from VESA VGA
[    1.625759] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.625761] [drm] Driver supports precise vblank timestamp query.
[    1.694932] fbcon: inteldrmfb (fb0) is primary device
[    1.723563] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    1.732419] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[    1.733993] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A
[    1.734053] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun
[    2.713673] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off

Comment 7 Rodd Clarkson 2014-10-15 00:37:55 UTC
I've got a lab of 26 computers, with most of them having the same hardware.  I'm seeing this on just on of the computers consistently, and I've seen it on a few others just once.

All the machines are running Fedora 20 and they are all current.

On the one that it's consistent on, pressing CTRL-D  continues the boot and the machine seems to run fine (I haven't noticed any problems).

I've booted fedora 21 alpha and it boots fine, so whatever it is in the current kernel, it's not in the fedora 21 alpha workstation livecd.

If someone is interested I could have a look through the bios of both the affected machine and another machine to see if it's a setting.  I've updated the bios on the affected machine but the problem still exists.

Comment 8 Bruce Korb 2015-01-02 23:27:17 UTC
Ubuntu has a workaround.  It is disappointing this did not make it into the Fedora 21 release:

http://askubuntu.com/questions/542576/resolve-these-startup-errors

Comment 9 Josh Boyer 2015-01-06 14:07:22 UTC
(In reply to Bruce Korb from comment #8)
> Ubuntu has a workaround.  It is disappointing this did not make it into the
> Fedora 21 release:
> 
> http://askubuntu.com/questions/542576/resolve-these-startup-errors

Um, there's nothing at that link that actually indicates what the workaround is nor if the suggested answer actually worked.  Did you have a different link with more information?

As far as we're aware, this is still an open upstream issue with multiple possible causes.

Comment 10 Bruce Korb 2015-01-07 02:18:54 UTC
Um, well, since I didn't have an Ubuntu installation, I confess I knew it would be useless to follow the link.  Sorry about my laziness.  #-(  I was about to try an Ubuntu install, but you just saved me :)  Thank you.

Comment 12 sharlatanus 2015-04-11 13:41:48 UTC
Hello,

I've got the same on machine:
Intel(R) Core(TM) i7-3770S CPU @ 3.10GHz

When I try to boot under GNOME shell, after a while it take ma back to login menu.

[bash]:~$>dmesg | grep drm
[    1.034916] [drm] Initialized drm 1.1.0 20060810
[    1.083165] [drm] Memory usable by graphics device = 2048M
[    1.083168] [drm] Replacing VGA console driver
[    1.090561] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.090563] [drm] Driver supports precise vblank timestamp query.
[    1.096148] [drm] Initialized i915 1.6.0 20141121 for 0000:00:02.0 on minor 0
[    1.196467] [drm] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4
[    1.206629] fbcon: inteldrmfb (fb0) is primary device
[    1.233704] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
[    1.233736] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
[    1.239381] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[   16.481231] SELinux: initialized (dev drm, type drm), not configured for labeling
[   20.839584] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder B


But there is no any problem with GNOME on Wayland

Comment 13 Dio Putra 2015-04-18 22:31:12 UTC
I've got the machine:
Intel(R) Core(TM) 1007U CPU

Here's the error message.
[pdo_fn14@ASMDT-TN14 ~]$ dmesg | grep drm
[    1.765431] [drm] Initialized drm 1.1.0 20060810
[    1.900571] [drm] Memory usable by graphics device = 2048M
[    1.900577] [drm] Replacing VGA console driver
[    1.908014] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.908018] [drm] Driver supports precise vblank timestamp query.
[    1.935931] [drm] failed to retrieve link info, disabling eDP
[    1.944857] [drm] Initialized i915 1.6.0 20150130 for 0000:00:02.0 on minor 0
[    1.954568] fbcon: inteldrmfb (fb0) is primary device
[    2.337311] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
[    2.337364] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
[    2.825846] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device

Comment 14 Fedora End Of Life 2015-05-29 12:41:04 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 John Dennis 2015-06-12 21:17:20 UTC
Still happening in F21. Bug 1231319 may be related.

Comment 16 Fedora End Of Life 2015-11-04 10:13:18 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 17 Fedora End Of Life 2015-12-02 03:26:51 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.