Bug 101868 - [KBL][drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Summary: [KBL][drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-21 08:55 UTC by Sven
Modified: 2018-04-11 11:21 UTC (History)
3 users (show)

See Also:
i915 platform: KBL
i915 features: power/Other


Attachments
dmesg with debug messages (94.21 KB, text/plain)
2017-08-11 16:08 UTC, andram
no flags Details

Description Sven 2017-07-21 08:55:44 UTC
On my Dell XPS 9560 with an Intel Core i7 7700HQ, the display is flickering occasionally. When the flickering occurs, the following message appears in dmesg:

[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun


If I work on Windows (which I rarely do), the flickering is absent. When I work with Linux, it appears a few times a day.

I believe I have the most current DMC firmware installed:
[drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1)


The flickering seems to happen especially often, if the laptop is running on battery.


I am using enable_rc6=0 right now, and it seems the problem with the FIFO underrun disappeared. No more display flickering.
Comment 1 Sven 2017-07-21 08:56:46 UTC
Kernel version: 4.11.7
Comment 2 Elizabeth 2017-07-21 15:03:38 UTC
Hello Sven,
Could you please try to replicate with latest mainline: https://www.kernel.org/,
and attach dmesg with drm.debug=0xe parameter on grub. 
Thanks.
Comment 3 Sven 2017-07-21 15:51:03 UTC
(In reply to Elizabeth from comment #2)
> Hello Sven,
> Could you please try to replicate with latest mainline:
> https://www.kernel.org/,
> and attach dmesg with drm.debug=0xe parameter on grub. 
> Thanks.

With latest mainline you mean 4.13-rc1? Or is 4.12 good enough as well?
I have data without backup on my laptop, and I'd rather avoid testing RCs.
Comment 4 Maderios 2017-07-24 10:56:03 UTC
I got same flickering screen bug with last kernel 4.12.3 I compiled myself
[driver intel i915 on asus x751 laptop]
dmesg
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Comment 5 Sven 2017-07-24 11:45:52 UTC
(In reply to Maderios from comment #4)
> I got same flickering screen bug with last kernel 4.12.3 I compiled myself
> [driver intel i915 on asus x751 laptop]

That Laptop actually has a Haswell CPU, right?
Comment 6 Maderios 2017-07-24 13:02:37 UTC
I think it's Broadwell cpu
https://ark.intel.com/products/85212/Intel-Core-i5-5200U-Processor-3M-Cache-up-to-2_70-GHz
https://www.notebookcheck.net/Intel-Core-i5-5200U-Notebook-Processor.127831.0.html

lshw
product: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
vendor: Intel Corp.
bus info: cpu@0
version: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
serial: NULL
slot: SOCKET 0
size: 1616MHz
capacity: 2700MHz
width: 64 bits
clock: 100MHz
Comment 7 Maderios 2017-07-24 20:54:45 UTC
I noticed display is flickering after I blank screen
Comment 8 andram 2017-08-11 15:11:48 UTC
Unfortunately I can confirm this bug on my Clevo NB240BU laptop. 

processor      Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz 
Kernel 4.12.4-1-ARCH



screen flicker happens two or three times a day and each time I get the message 

[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

Please let me know, how I can help with debugging.
Comment 9 andram 2017-08-11 16:08:28 UTC
Created attachment 133441 [details]
dmesg with debug messages

I have now booted with the "drm.debug=0xe" kernel parameter. Attached the resulting dmesg up to the first flicker.
Comment 10 Jani Nikula 2018-01-24 12:19:21 UTC
Is this reproducible when booting with nvme_core.default_ps_max_latency_us=0 module parameter?
Comment 11 Matthew Thode 2018-01-29 09:10:25 UTC
I've been able to reproduce this (see https://www.youtube.com/watch?v=VR-MiCo7Xbk ).

I think Bug 102803 is the same issue.

I'm running 4.14.15 very close to upstream (gentoo-sources).  I tested with your nvme_core option on the kernel command line and reproduced the issue (verified it was disabled via 'nvme get-feature -f 0x0c -H /dev/nvme0 | grep APSTE'.   So that's not a workaround.

Right now I'm booted with rc6 disabled to verify that 'fixes' it.
Comment 12 Matthew Thode 2018-01-29 09:13:40 UTC
huh, i915.edp_vswing=2 	Fix screen flickering is mentioned on https://wiki.archlinux.org/index.php/Dell_XPS_15_(9550) not sure if it's valid though
Comment 13 Matthew Thode 2018-01-30 18:31:31 UTC
can this be closed in preference to Bug 102803 until we know that the issue is different between the two?  iirc the graphics core between the two is nearly identical.  I've update the other bug with the features/platforms that seem to have the bug hit.
Comment 14 Elizabeth 2018-02-01 23:08:23 UTC
I(In reply to Matthew Thode from comment #13)
> can this be closed in preference to Bug 102803 until we know that the issue
> is different between the two?  iirc the graphics core between the two is
> nearly identical.  I've update the other bug with the features/platforms
> that seem to have the bug hit.
Maybe I skipped a comment, but they confirmed that rc6 disable fixes it as in this case? Also Harish mentioned that nvme parameter works for him, at least it seems so, and you still was able to reproduce, right? Other than that looks the same issue.
Comment 15 Jani Saarinen 2018-03-29 07:12:01 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 16 Matthew Thode 2018-03-29 16:01:23 UTC
as refrenced in https://bugs.freedesktop.org/show_bug.cgi?id=102803 I think we are good.

my kernel command line follows (for x1 carbon gen5 with a toshiba (iirc) screen).  It enables rc6

initrd=\early_ucode.cpio initrd=\initramfs-4.14.30-gentoo.img i915.enable_guc_loading=1 i915.enable_guc_submission=1 i915.semaphores=1 i915.nuclear_pageflip=1 i915.fastboot=1 psmouse.synaptics_intertouch=1 zfs.zfs_arc_max=3221225472 root=zfs:AUTO init=/usr/lib/systemd/systemd page_poison=1 slab_nomerge vsyscall=none slub_debug=P ro i915.enable_gvt=0 i915.enable_rc6=1 i915.enable_psr=2 kvm.ignore_msrs=1 intel_iommu=off log_buf_len=2M
Comment 17 Jani Saarinen 2018-03-30 06:51:17 UTC
OK, thanks for the feedback, resolving.
Comment 18 Maderios 2018-04-10 12:49:38 UTC
This bug is still present when I boot each kernel 4.14.x from first version.
Today, I tried 4.14.32:
Description: using only one screen, display is flickering after I blank screen.
Flickering screen, all computer becomes unusable. 
Apr 10 11:18:56 moi kernel: [ 4172.575784] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

I reboot on kernel 4.9.90 or 4.4.x all is OK...
hardware: Broadwell cpu
https://ark.intel.com/products/85212/Intel-Core-i5-5200U-Processor-3M-Cache-up-to-2_70-GHz
https://www.notebookcheck.net/Intel-Core-i5-5200U-Notebook-Processor.127831.0.html
Comment 19 Jani Saarinen 2018-04-10 13:05:40 UTC
Can you try with latest drm-tip: https://cgit.freedesktop.org/drm-tip?
Comment 20 Maderios 2018-04-11 11:21:50 UTC
I compiled this version yesterday. 
https://aur.archlinux.org/packages/linux-git/
4.16.0-gc698ca527893
I launched to X session from two tty in same time.
Now, it works: no flickering screen, no 'drm:intel_cpu_fifo_underrun_irq_handler [i915]]' in dmesg


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.