Bug 1491521 - Errors: drm:intel_set_cpu_fifo_underrun_reporting [i915] - drm:intel_cpu_fifo_underrun_irq_handler [i915]
Summary: Errors: drm:intel_set_cpu_fifo_underrun_reporting [i915] - drm:intel_cpu_fifo...
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 26
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-09-14 05:16 UTC by jeremy9856
Modified: 2019-12-20 06:42 UTC (History)
24 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-05-29 12:13:48 UTC
Type: Bug

Attachments (Terms of Use)

Description jeremy9856 2017-09-14 05:16:24 UTC

I get these errors at boot since kernel 4.12

sept. 12 00:56:19 hp kernel: [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
sept. 12 00:56:19 hp kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

Can it be fixed please ?

Fedora 26, Chromebook HP 14 (Falco) w/ MattDevo firmware.

Thanks !

Comment 1 jeremy9856 2017-09-14 05:39:04 UTC
Happen with kernel 4.13.1 from epos.fedorapeople.org/repos/thl/kernel-vanilla.repo too. Doesn't happen with kernel 4.11.8.

Comment 2 jeremy9856 2017-09-14 05:39:59 UTC
I meant repos.fedorapeople.org/repos/thl/kernel-vanilla.repo

Comment 3 jeremy9856 2017-09-16 17:26:43 UTC
I tried the John Lewis firmware and there is no error message.

Comment 4 jeremy9856 2017-09-17 22:19:55 UTC
I reported here too https://bugs.freedesktop.org/show_bug.cgi?id=102759

Comment 5 Laura Abbott 2018-02-28 03:56:35 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs.
Fedora 26 has now been rebased to 4.15.4-200.fc26.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27.
If you experience different issues, please open a new bug report for those.

Comment 6 Fedora End Of Life 2018-05-03 07:51:30 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 7 Fedora End Of Life 2018-05-29 12:13:48 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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

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

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