Bug 89101

Summary: [SKL]clean boot system report *ERROR* CPU pipe A FIFO underrun
Product: DRI Reporter: lu hua <huax.lu>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED INVALID QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: high CC: intel-gfx-bugs
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg none

Description lu hua 2015-02-12 08:35:53 UTC 
Created attachment 113395 [details]
dmesg

System Environment:
--------------------------
Regression: not sure

no-working platforms: SKL

==kernel==
--------------------------
drm-intel-nightly/2a579576e4c01799ec67264c9169e5adeadcc3ff
commit 2a579576e4c01799ec67264c9169e5adeadcc3ff
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Wed Feb 11 17:16:34 2015 +0100

    drm-intel-nightly: 2015y-02m-11d-16h-11m-28s UTC integration manifest

==Bug detailed description==
-----------------------------
clean boot system with drm-intel-nightly kernel., report *ERROR* CPU pipe A FIFO underrun 

root@x-skly06:/GFX/Test/Piglit/piglit# dmesg -r|egrep "<[1-4]>"|grep drm
<3>[    3.297286] [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

==Reproduce steps==
---------------------------- 
1. clean boot system
2. dmesg -r|egrep "<[1-4]>"|grep drm
Comment 1 Jani Nikula 2015-02-12 08:59:12 UTC 
What is this, all of a sudden plenty of reports with the INCORRECT i915.debug=0xe module parameter. It should be drm.debug=0xe as always. Please attach new dmesg.
Comment 2 lu hua 2015-02-13 02:56:30 UTC 
(In reply to Jani Nikula from comment #1)
> What is this, all of a sudden plenty of reports with the INCORRECT
> i915.debug=0xe module parameter. It should be drm.debug=0xe as always.
> Please attach new dmesg.

Sorry, incorrect parameter. add drm.debug=0xe, I don't meet this error.
Comment 3 Jari Tahvanainen 2016-10-10 10:36:27 UTC 
Closing verified+invalid

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.