Bug 111838 - [DRM-INTEL] linux kernel dmesg-warn CPU pipe A FIFO underrun
Summary: [DRM-INTEL] linux kernel dmesg-warn CPU pipe A FIFO underrun
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-27 07:18 UTC by xiao sheng wen
Modified: 2019-11-29 19:35 UTC (History)
2 users (show)

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


Attachments
dmesg (44.59 KB, text/plain)
2019-09-27 07:18 UTC, xiao sheng wen
no flags Details
lspci (7.45 KB, text/plain)
2019-09-27 07:19 UTC, xiao sheng wen
no flags Details
dmidecode (6.21 KB, text/plain)
2019-09-27 07:20 UTC, xiao sheng wen
no flags Details
the dmesg of add drm.debug=14 module parameter (89.60 KB, text/plain)
2019-09-27 10:47 UTC, xiao sheng wen
no flags Details
the 5.3.0 kernel debug dmesg (84.87 KB, text/plain)
2019-09-28 01:57 UTC, xiao sheng wen
no flags Details

Description xiao sheng wen 2019-09-27 07:18:04 UTC
Created attachment 145542 [details]
dmesg

On computer boot,the linux kernel dmesg has the following error info:

[    4.477187] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[    4.477272] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* pipe B underrun
[    4.477348] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
[    4.477187] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[    4.477272] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* pipe B underrun
[    4.477348] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun

I had report this bug on Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941197

-- system architecture: ("uname -m")  i686
-- kernel version: ("uname -r") 4.19.0-6-686
4.19.0-6-686 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) i686 GNU/Linux

-- Linux distribution:Debian 10.1 
-- Machine or mother board model:

dmidecode info about machine type:

BIOS Information
        Vendor: Phoenix Technologies LTD
        Version: R0042G9
        Release Date: 01/19/2005

System Information
        Manufacturer: Sony Corporation
        Product Name: VGN-B99C
        Version: C2004ZYP
        Serial Number: 28194290-9106065
        UUID: e7fb2880-4b65-11c6-8c2a-00014a075a9a
Comment 1 xiao sheng wen 2019-09-27 07:19:31 UTC
Created attachment 145543 [details]
lspci
Comment 2 xiao sheng wen 2019-09-27 07:20:13 UTC
Created attachment 145544 [details]
dmidecode
Comment 3 Jani Nikula 2019-09-27 07:48:02 UTC
(In reply to xiao sheng wen from comment #0)
> Created attachment 145542 [details]
> dmesg

Please add drm.debug=14 module parameter, and do this again.

Is this reproducible on newer kernels? v5.3 or drm-tip branch of https://cgit.freedesktop.org/drm/drm-tip
Comment 4 xiao sheng wen 2019-09-27 10:47:51 UTC
Created attachment 145546 [details]
the dmesg of add drm.debug=14 module parameter

the dmesg of add drm.debug=14 module parameter is upload.

please see this new dmesg file first.

If need,I'll compile the newest kernel to test.
Comment 5 xiao sheng wen 2019-09-28 01:57:55 UTC
Created attachment 145561 [details]
the 5.3.0 kernel debug dmesg

It is reproducible on newer kernels.

I use  drm-tip branch of https://cgit.freedesktop.org/drm/drm-tip to compile the newest kernel to boot computer,the error info also exist.

The details info ,please see this  attachment(add drm.debug=14 module parameter already).
Comment 6 Lakshmi 2019-10-02 10:21:02 UTC
> I use  drm-tip branch of https://cgit.freedesktop.org/drm/drm-tip to compile
> the newest kernel to boot computer,the error info also exist.
> 
Can you please attach dmesg from drmtip? Which platform is this? I couldn't find it from the dmseg?
As a user, what is the impact of this issue other than the errors in the logs?
Comment 7 xiao sheng wen 2019-10-02 10:53:47 UTC

(In reply to Lakshmi from comment #6)
> > I use  drm-tip branch of https://cgit.freedesktop.org/drm/drm-tip to compile
> > the newest kernel to boot computer,the error info also exist.
> > 
> Can you please attach dmesg from drmtip? Which platform is this? I couldn't
> find it from the dmseg?
> As a user, what is the impact of this issue other than the errors in the
> logs?

https://bugs.freedesktop.org/attachment.cgi?id=145561 ,this is dmesg from drmtip .

The OS is Debian 10.1 32bit.

Only errors in the logs,No other impact for me.
Comment 8 Lakshmi 2019-10-02 12:04:51 UTC
(In reply to xiao sheng wen from comment #7)
> 
> (In reply to Lakshmi from comment #6)
> > > I use  drm-tip branch of https://cgit.freedesktop.org/drm/drm-tip to compile
> > > the newest kernel to boot computer,the error info also exist.
> > > 
> > Can you please attach dmesg from drmtip? Which platform is this? I couldn't
> > find it from the dmseg?
> > As a user, what is the impact of this issue other than the errors in the
> > logs?
> 
> https://bugs.freedesktop.org/attachment.cgi?id=145561 ,this is dmesg from
> drmtip .
> 
> The OS is Debian 10.1 32bit.
> 
> Only errors in the logs,No other impact for me.

Current drmtip version is 5.4-rc1+ and attached dmesg is from 5.3. Can you please verify with (https://cgit.freedesktop.org/drm-tip)?
Which platform is this?
Comment 9 xiao sheng wen 2019-10-02 14:29:20 UTC
(In reply to Lakshmi from comment #8)
> > 
> > https://bugs.freedesktop.org/attachment.cgi?id=145561 ,this is dmesg from
> > drmtip .
> > 
> > The OS is Debian 10.1 32bit.
> > 
> > Only errors in the logs,No other impact for me.
> 
> Current drmtip version is 5.4-rc1+ and attached dmesg is from 5.3. Can you
> please verify with (https://cgit.freedesktop.org/drm-tip)?
> Which platform is this?

I clone this drm-tip git version to compile kernel. 

commit e8ad7c465ad3be7dd16d8629b03165e06ed7acda
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Sep 27 13:06:16 2019 +0100

    drm-tip: 2019y-09m-27d-12h-05m-14s UTC integration manifest

git remote -vvv
origin	https://anongit.freedesktop.org/git/drm-tip.git/ (fetch)
origin	https://anongit.freedesktop.org/git/drm-tip.git/ (push)

My OS is Debian 10.1 ,i386. 
I use make bindeb-pkg to Kernel packaging. 
In drm-tip/debian/control file,kernel version is 5.3.0 .

At final,I get the following files:
-rw-r--r-- 1 root root     4373 9月  28 07:23 linux-5.3.0_5.3.0-1_i386.buildinfo
-rw-r--r-- 1 root root     1718 9月  28 07:23 linux-5.3.0_5.3.0-1_i386.changes
-rw-r--r-- 1 root root 11277144 9月  28 07:18 linux-headers-5.3.0_5.3.0-1_i386.deb
-rw-r--r-- 1 root root 41130092 9月  28 07:23 linux-image-5.3.0_5.3.0-1_i386.deb
-rw-r--r-- 1 root root  1061044 9月  28 07:18 linux-libc-dev_5.3.0-1_i386.deb

so,the kernel version 5.3.0 is right for drm-tip packageing by .deb.The source code is newest,don't worry please.
Comment 10 Lakshmi 2019-10-03 06:38:47 UTC
Xiao, what's the platform under use here? Strangely, I couldn't find that info from the dmesg.
Comment 11 xiao sheng wen 2019-10-04 01:02:08 UTC
(In reply to Lakshmi from comment #10)
> Xiao, what's the platform under use here? Strangely, I couldn't find that
> info from the dmesg.

What's the meaning about the word "platform"? Is OS or hardware ?

OS:
-- system architecture: ("uname -m")  i686
-- Linux distribution:Debian 10.1 
-- Machine or mother board model:

Hardware:
dmidecode info about machine type:

BIOS Information
        Vendor: Phoenix Technologies LTD
        Version: R0042G9
        Release Date: 01/19/2005

System Information
        Manufacturer: Sony Corporation
        Product Name: VGN-B99C
        Version: C2004ZYP
Comment 12 Martin Peres 2019-11-29 19:35:34 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/458.


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.