Bug 106538 - [CI][GLK] drm:intel_cpu_fifo_underrun_irq_handler [i915] *ERROR* CPU pipe B FIFO underrun
Summary: [CI][GLK] drm:intel_cpu_fifo_underrun_irq_handler [i915] *ERROR* CPU pipe B F...
Status: RESOLVED MOVED
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:
Keywords:
Depends on:
Blocks: 105980
  Show dependency treegraph
 
Reported: 2018-05-16 07:25 UTC by Tomi Sarvela
Modified: 2019-11-29 17:47 UTC (History)
2 users (show)

See Also:
i915 platform: GLK
i915 features: display/atomic


Attachments
dmesg (64.07 KB, text/plain)
2019-04-27 08:33 UTC, Behrang Saeedzadeh
no flags Details

Description Tomi Sarvela 2018-05-16 07:25:00 UTC
FIFO underruns made an appearance on Gemini Lake NUCs. Examples of tests it hits:

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4182/shard-glk4/igt@kms_cursor_legacy@cursorb-vs-flipb-toggle.html

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4182/shard-glk4/igt@kms_cursor_legacy@flip-vs-cursor-crc-atomic.html

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4182/shard-glk4/igt@kms_busy@extended-pageflip-modeset-hang-oldfb-render-b.html

This might be residual issues from 4.17-rc5 pull, and happened only on one run on host, so we'll follow if it happens again.
Comment 2 Martin Peres 2018-09-11 13:53:15 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1821/shard-glk5/igt@kms_rotation_crc@sprite-rotation-270.html

<3> [58.669164] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
<3> [58.852204] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Comment 3 Vít Ondruch 2018-09-18 12:29:13 UTC
I observer similar error. Actually my computer typically freezes due to this :/ It typically happens when my computer is a sleep and some gnome nofitication appears on the lock screen. I also suspect it has something to do with my external monitory, which has from time to time hard time to wake up. Also, I suspect it started to happen with Kernel 4.17. 4.16 was almost rock stable for me.

I am running Lenovo t470s

~~~
$ uname -a
Linux localhost.localdomain 4.18.5-300.fc29.x86_64 #1 SMP Fri Aug 24 17:16:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

$ rpm -q kernel
kernel-4.17.6-200.fc28.x86_64
kernel-4.17.14-200.fc28.x86_64
kernel-4.18.5-300.fc29.x86_64
~~~
Comment 4 Behrang Saeedzadeh 2019-04-27 08:33:55 UTC
Created attachment 144100 [details]
dmesg

I think this issue has been affecting me for a few years now but i just recently started to look into it.

my current system is ubuntu 19.04 but this issue was present even when i was using 18.04 and 18.10 and even before that.

os: ubuntu 19.04
cpu: intel core i7 6700
graphics (integrated only): hd graphics 530 (skylake gt2)

anyway, from time to time only one of my monitors turn on. when that happens `dmesg | grep i915` prints this:

```
➜  ~ dmesg -e | grep i915
[  +0.000545] i915 0000:00:02.0: vgaarb: changed vga decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[  +0.000627] [drm] finished loading dmc firmware i915/skl_dmc_ver1_27.bin (v1.27)
[  +0.003052] [drm] initialized i915 1.6.0 20181204 for 0000:00:02.0 on minor 0
[  +0.000036] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[  +0.000047] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[  +0.249846] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *error* cpu pipe a fifo underrun

➜  ~ dmesg -t | grep i915
[sat apr 27 17:47:08 2019] i915 0000:00:02.0: vgaarb: changed vga decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[sat apr 27 17:47:08 2019] [drm] finished loading dmc firmware i915/skl_dmc_ver1_27.bin (v1.27)
[sat apr 27 17:47:09 2019] [drm] initialized i915 1.6.0 20181204 for 0000:00:02.0 on minor 0
[sat apr 27 17:47:09 2019] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[sat apr 27 17:47:09 2019] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[sat apr 27 17:47:09 2019] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *error* cpu pipe a fifo underrun
```

when i switch to wayland, sometimes none of my monitors turn on at all. once when both turned on, i turned off one
and tried to turn it back on again, but it went into energy saving mode. then `dmesg` was showing this:


```
➜  ~ dmesg -t | grep i915
[sat apr 27 18:14:17 2019] i915 0000:00:02.0: vgaarb: changed vga decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[sat apr 27 18:14:17 2019] [drm] finished loading dmc firmware i915/skl_dmc_ver1_27.bin (v1.27)
[sat apr 27 18:14:18 2019] [drm] initialized i915 1.6.0 20181204 for 0000:00:02.0 on minor 0
[sat apr 27 18:14:18 2019] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[sat apr 27 18:14:18 2019] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[sat apr 27 18:14:56 2019] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *error* cpu pipe b fifo underrun

➜  ~ dmesg -e | grep i915
[  +0.000664] i915 0000:00:02.0: vgaarb: changed vga decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[  +0.000861] [drm] finished loading dmc firmware i915/skl_dmc_ver1_27.bin (v1.27)
[  +0.016298] [drm] initialized i915 1.6.0 20181204 for 0000:00:02.0 on minor 0
[  +0.000047] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[  +0.000047] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ +23.689059] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *error* cpu pipe b fifo underrun

```
Comment 5 Martin Peres 2019-11-29 17:47:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/118.


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.