Bug 110613 - *ERROR* uncleared fifo underrun on pipe A
Summary: *ERROR* uncleared fifo underrun on pipe A
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged, ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-05 14:21 UTC by turanomario
Modified: 2019-08-19 13:16 UTC (History)
2 users (show)

See Also:
i915 platform: IVB
i915 features: display/watermark


Attachments
dmesg (1.01 MB, text/plain)
2019-05-08 11:21 UTC, turanomario
no flags Details
dmesg output (76.69 KB, text/x-log)
2019-07-23 00:17 UTC, Malcolm Lewis
no flags Details
5.3.1.rc dmesg output (64.38 KB, text/plain)
2019-07-23 18:02 UTC, Malcolm Lewis
no flags Details
rdsosreport (91.90 KB, text/plain)
2019-07-23 18:03 UTC, Malcolm Lewis
no flags Details
dmesg output 08191 (91.94 KB, text/plain)
2019-08-19 13:15 UTC, Malcolm Lewis
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description turanomario 2019-05-05 14:21:17 UTC
[drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
[drm:cpt_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
Comment 1 turanomario 2019-05-05 14:26:02 UTC
Intel i5vPro 3437U GPU Intel HD 4000

Fedora 30 kernel 5.0.11

Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) Ivybridge Mobile (0x166)
Version: 19.0.3
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.2
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0

server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
Max core profile version: 4.2
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL core profile version string: 4.2 (Core Profile) Mesa 19.0.3
OpenGL core profile shading language version string: 4.20
OpenGL version string: 3.0 Mesa 19.0.3
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
Comment 2 Jani Saarinen 2019-05-06 05:41:04 UTC
I see similar messages on following bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=105586
https://bugs.freedesktop.org/show_bug.cgi?id=109479

Maybe duplicate of those? 

If you think no, then please try to reproduce the error using drm-tip (https://cgit.freedesktop.org/drm-tip) and kernel parameters drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full dmesg from boot.

Build instructions: https://01.org/linuxgraphics/documentation/build-guide-0
Comment 3 turanomario 2019-05-08 11:21:21 UTC
Created attachment 144195 [details]
dmesg

dmesg log 

kernel 5.1
Comment 4 Lakshmi 2019-05-29 12:54:01 UTC
(In reply to turanomario from comment #3)
> Created attachment 144195 [details]
> dmesg
> 
> dmesg log 
> 
> kernel 5.1

Can you please attach the log from boot?
In this attachment I don't find below error
[drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
[drm:cpt_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun

Is this still occurring on drmtip?

Other than the error in the log, is there any other impact to you?
Comment 5 Lakshmi 2019-06-14 09:49:14 UTC
Reporter, can you answer to the above queries?
Comment 6 Malcolm Lewis 2019-07-23 00:17:46 UTC
Created attachment 144849 [details]
dmesg output

Hi
I'm seeing the same error;

cat /etc/os-release 
NAME="openSUSE Tumbleweed"
# VERSION="20190721"
ID="opensuse-tumbleweed"

CPU: Intel i5-3470S Intel Ivybridge HD 2500

Graphics:  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:0152 
           Device-2: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: nvidia v: 430.34 bus ID: 01:00.0 chip ID: 10de:128b 
           Device-3: NVIDIA GK208B [GeForce GT 710] vendor: ZOTAC driver: vfio-pci v: 0.2 bus ID: 02:00.0 chip ID: 10de:128b 
           Display: server: X.Org 1.20.5 driver: fbdev,modesetting,nvidia,vesa alternate: nouveau,nv compositor: gnome-shell 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ivybridge Desktop v: 4.2 Mesa 19.1.2 compat-v: 3.0 direct render: Yes 

Kernel: Linux grover 5.1.16-1-default #1 SMP Wed Jul 3 12:37:47 UTC 2019 (2af8a22) x86_64 x86_64 x86_64 GNU/Linux

Jul 22 15:49:27 grover kernel: [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
Jul 22 15:49:27 grover kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Jul 22 15:49:27 grover kernel: [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
Jul 22 15:49:27 grover kernel: [drm:cpt_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun

No openGL libs installed for the nvidia driver, one card is for cuda cores, the other for gpu passthrough.
Comment 7 Lakshmi 2019-07-23 07:20:29 UTC
Can you please verify the issue with drmtip (https://cgit.freedesktop.org/drm-tip)? Attach dmesg if the issue persists with drmtip. This information will be helpful during investigation.
Comment 8 Malcolm Lewis 2019-07-23 13:49:25 UTC
(In reply to Lakshmi from comment #7)
> Can you please verify the issue with drmtip
> (https://cgit.freedesktop.org/drm-tip)? Attach dmesg if the issue persists
> with drmtip. This information will be helpful during investigation.
Hi
During make of drm-tip I'm hitting the following error?

make V=1
...

mkdir -p ./tools
make LDFLAGS= MAKEFLAGS=" " O=/data/repositories/fdo#110613/drm-tip subdir=tools -C ./tools/ objtool
mkdir -p /data/repositories/fdo#110613/drm-tip/tools/objtool && make O=/data/repositories/fdo#110613/drm-tip subdir=tools/objtool --no-print-directory -C objtool 
make -C /data/repositories/fdo#110613/drm-tip/tools/build CFLAGS= LDFLAGS= /data/repositories/fdo#110613/drm-tip/tools/objtool/fixdep
make -f /data/repositories/fdo#110613/drm-tip/tools/build/Makefile.build dir=. obj=fixdep
/data/repositories/fdo#110613/drm-tip/tools/objtool/.fixdep-in.o.cmd:1: *** missing separator.  Stop.
make[3]: *** [Makefile:43: /data/repositories/fdo#110613/drm-tip/tools/objtool/fixdep-in.o] Error 2
make[2]: *** [/data/repositories/fdo#110613/drm-tip/tools/build/Makefile.include:5: fixdep] Error 2
make[1]: *** [Makefile:67: objtool] Error 2
make: *** [Makefile:1743: tools/objtool] Error 2
Comment 9 Malcolm Lewis 2019-07-23 17:11:03 UTC
(In reply to Malcolm Lewis from comment #8)
> (In reply to Lakshmi from comment #7)
> > Can you please verify the issue with drmtip
> > (https://cgit.freedesktop.org/drm-tip)? Attach dmesg if the issue persists
> > with drmtip. This information will be helpful during investigation.
> Hi
> During make of drm-tip I'm hitting the following error?
> 
> make V=1
> ...
> 
> mkdir -p ./tools
> make LDFLAGS= MAKEFLAGS=" " O=/data/repositories/fdo#110613/drm-tip
> subdir=tools -C ./tools/ objtool
> mkdir -p /data/repositories/fdo#110613/drm-tip/tools/objtool && make
> O=/data/repositories/fdo#110613/drm-tip subdir=tools/objtool
> --no-print-directory -C objtool 
> make -C /data/repositories/fdo#110613/drm-tip/tools/build CFLAGS= LDFLAGS=
> /data/repositories/fdo#110613/drm-tip/tools/objtool/fixdep
> make -f /data/repositories/fdo#110613/drm-tip/tools/build/Makefile.build
> dir=. obj=fixdep
> /data/repositories/fdo#110613/drm-tip/tools/objtool/.fixdep-in.o.cmd:1: ***
> missing separator.  Stop.
> make[3]: *** [Makefile:43:
> /data/repositories/fdo#110613/drm-tip/tools/objtool/fixdep-in.o] Error 2
> make[2]: ***
> [/data/repositories/fdo#110613/drm-tip/tools/build/Makefile.include:5:
> fixdep] Error 2
> make[1]: *** [Makefile:67: objtool] Error 2
> make: *** [Makefile:1743: tools/objtool] Error 2
Hi
OK, my bad, didn't like the # in my directory name... building now
Comment 10 Malcolm Lewis 2019-07-23 18:02:34 UTC
Created attachment 144860 [details]
5.3.1.rc dmesg output

Hi
Well it booted into emergency mode, but still see the error in dmesg output with the 5.3.1rc+ kernel.
Comment 11 Malcolm Lewis 2019-07-23 18:03:47 UTC
Created attachment 144861 [details]
rdsosreport
Comment 12 Lakshmi 2019-07-25 08:26:09 UTC
(In reply to Malcolm Lewis from comment #10)
> Created attachment 144860 [details]
> 5.3.1.rc dmesg output
> 
> Hi
> Well it booted into emergency mode, but still see the error in dmesg output
> with the 5.3.1rc+ kernel.

Thanks for the logs from drm-tip. 
Apart from the error in the log, is there any other impact due to this error?
Comment 13 Malcolm Lewis 2019-07-25 11:36:44 UTC
(In reply to Lakshmi from comment #12)
> (In reply to Malcolm Lewis from comment #10)
> > Created attachment 144860 [details]
> > 5.3.1.rc dmesg output
> > 
> > Hi
> > Well it booted into emergency mode, but still see the error in dmesg output
> > with the 5.3.1rc+ kernel.
> 
> Thanks for the logs from drm-tip. 
> Apart from the error in the log, is there any other impact due to this error?
Hi
Not that I'm aware of, system functions fine even across multiple monitors when connected.
Comment 14 Anshuman Gupta 2019-08-18 14:51:09 UTC
Hi Lewis ,
As i see your provided dmesg logs this underrun observed while boot up before modeset.

Have u observed this underrun error while normal display use case active cases.
If it is just observed at boot time before modeset, it can also be a issue of BIOS settings too.  

Thanks ,
Anshuman Gupta.
Comment 15 Anshuman Gupta 2019-08-18 14:51:41 UTC
Hi Lewis ,
As i see your provided dmesg logs this underrun observed while boot up before modeset.

Have u observed this underrun error while normal display use case active cases.
If it is just observed at boot time before modeset, it can also be a issue of BIOS settings too.  

Thanks ,
Anshuman Gupta.
Comment 16 Malcolm Lewis 2019-08-18 15:16:07 UTC
Hi
No, just during boot, not during normal operation. I've just upgraded the system CPU to a E3-1245 V2 and still see the same error (now on Tumbleweed 5.2.8 kernel).

I also reduced the IGD to 32MB and upto 1GB, normally have it set to 512MB and still see the same error.
Comment 17 Anshuman Gupta 2019-08-19 06:14:21 UTC
Hi ,
Before suspecting BIOS, we wanted to make sure that this issue happens before modeset, i do not see any drm/modeset logs in your dmesg have u appended the drm.debug=0xe to your kernel command line parameter, as it is not appears from you drmeg log.

Ex. GRUB_CMDLINE_LINUX_DEFAULT="quiet 3 splash drm.debug=0x3" to your /etc/default/grub

Thanks ,
Anshuman Gupta.
Comment 18 Malcolm Lewis 2019-08-19 13:15:17 UTC
Created attachment 145097 [details]
dmesg output 08191
Comment 19 Malcolm Lewis 2019-08-19 13:16:31 UTC
Hi
Latest dmesg output as requested with drm.debug=0x3 and booting to multi-user target.


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.