Bug 102759 - 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...
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Paviluf
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-14 20:31 UTC by Paviluf
Modified: 2018-03-28 16:06 UTC (History)
4 users (show)

See Also:
i915 platform: HSW
i915 features:


Attachments

Description Paviluf 2017-09-14 20:31:21 UTC
Hello,

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.

Happen with kernel 4.13.2 from repos.fedorapeople.org/repos/thl/kernel-vanilla.repo too. Doesn't happen with kernel 4.11.8.

Thanks !
Comment 1 Paviluf 2017-09-16 17:26:54 UTC
I tried the John Lewis firmware and there is no error message.
Comment 2 Elizabeth 2017-09-20 15:52:10 UTC
(In reply to Paviluf from comment #1)
> I tried the John Lewis firmware and there is no error message.
Hello Paviluf,
Based on your last comment this problem seems to be related to the firmware used, directly MattDevo firmware, which we don't support. If possible it would be better to file a new issue in the MattDevo Repo so the developer(s) can work on a solution: https://github.com/MattDevo/firmware/issues
Thank you.

Closing as not our bug.
Comment 3 Paviluf 2017-09-20 17:07:39 UTC
Hello Elizabeth,
 
I already reported the bug on MattDevo github and it's him that said to me that it's a kernel bug :

https://github.com/MattDevo/firmware/issues/74

The bug is not present with John Lewis firmware because it is a legacy bios whereas the MattDevo one is a UEFI firmware.
Comment 4 Elizabeth 2017-09-21 16:27:03 UTC
Hello again,
Thanks for the information, in that case can you share a full dmesg from boot till the error message with the parameters drm.debug=0x1e log_bug_len=2M on grub, also a clean kern.log could help. How this occurs? At booting or logging? After any application is running? With some specific event? How frequent it happens? Are you using an external display besides your laptop display?
Comment 5 Paviluf 2017-09-25 11:15:31 UTC
I can't reinstall the MattDevo firmware for now but MattDevo will provide you the infos required !
Comment 6 Ricardo 2017-09-25 14:27:18 UTC
once logs are included with details to reproduce and extra information please change the status back to Reopen and assign the bug to default.

this bug is now please under needinfo
Comment 7 Jani Nikula 2018-01-22 11:59:14 UTC
No response in months, closing.

It's hard enough with stock firmware, we can't support combos with random firmwares. Please reopen if you can reproduce with the stock firmware in the boot mode (UEFI vs. legacy) the original operating system shipped in.
Comment 8 Paviluf 2018-01-22 14:34:51 UTC
Well it seem that MattDevo didn't found the time to provide the requested infos. I informed him that the bug is closed for now. Thanks.
Comment 9 Jani Saarinen 2018-03-28 16:06:36 UTC
Closing.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.