[Bug 79261] [Samsung NP530U3C-A02CL] [drm:ilk_display_irq_handler] *ERROR* Pipe A FIFO underrun

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Wed Aug 13 04:05:51 PDT 2014


https://bugzilla.kernel.org/show_bug.cgi?id=79261

Claire Farron <diesal3 at googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |diesal3 at googlemail.com

--- Comment #2 from Claire Farron <diesal3 at googlemail.com> ---
Created attachment 146431
  --> https://bugzilla.kernel.org/attachment.cgi?id=146431&action=edit
Toshiba Satellite Pro C850

I have these messages with the 3.16 kernel, but not any kernel before it.

archtesting ~ % dmesg | grep drm
[   13.173536] [drm] Initialized drm 1.1.0 20060810
[   13.757851] [drm] Memory usable by graphics device = 2048M
[   13.757855] [drm] Replacing VGA console driver
[   13.757860] fb: switching to inteldrmfb from VESA VGA
[   13.777947] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   13.777948] [drm] Driver supports precise vblank timestamp query.
[   13.796673] [drm] Wrong MCH_SSKPD value: 0x16040307
[   13.796677] [drm] This can cause pipe underruns and display issues.
[   13.796679] [drm] Please upgrade your BIOS to fix this.
[   13.809484] fbcon: inteldrmfb (fb0) is primary device
[   14.119255] [drm:ilk_display_irq_handler] *ERROR* Pipe A FIFO underrun
[   14.120929] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo
underrun on pch transcoder A
[   14.120931] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO
underrun
[   14.605499] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[   14.670491] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor
0
[   15.346402] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
archtesting ~ % 

There is also this thread on the ArchLinux BBS:
https://bbs.archlinux.org/viewtopic.php?id=184857

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the intel-gfx-bugs mailing list