FS#42866 - [linux] DRM pipe underrun error when booting up

Attached to Project: Arch Linux
Opened by mandragore (mandragore) - Friday, 21 November 2014, 16:10 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 31 July 2016, 02:54 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:


When booting up some errors will appear releated to a pipe A underrun

[drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe A underrun

pc will continue like nothing happened.

This does not happen all the time and only happens when i am prompted for login and password

Additional info:
[ 11.011192] [drm] Initialized drm 1.1.0 20060810
[ 11.878522] [drm] Memory usable by graphics device = 128M
[ 11.878529] [drm] Replacing VGA console driver
[ 11.878541] fb: switching to inteldrmfb from VESA VGA
[ 11.883989] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 11.883995] [drm] Driver supports precise vblank timestamp query.
[ 11.889431] [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe A underrun
[ 11.905158] [drm] initialized overlay support
[ 11.928581] [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe A underrun
[ 11.970207] fbcon: inteldrmfb (fb0) is primary device
[ 12.537787] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 12.550090] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 151.657028] [drm:i8xx_irq_handler] *ERROR* pipe B underrun
[ 454.307833] [drm:i8xx_irq_handler] *ERROR* pipe B underrun
[ 581.861236] [drm:i8xx_irq_handler] *ERROR* pipe B underrun
[ 1201.219191] [drm:i8xx_irq_handler] *ERROR* pipe B underrun
[ 1235.365497] [drm:i8xx_irq_handler] *ERROR* pipe B underrun


This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 31 July 2016, 02:54 GMT
Reason for closing:  No response
Comment by Samantha McVey (samcv) - Friday, 10 June 2016, 04:02 GMT
Hoping this issue has been fixed in the intel i915 kernel drivers since 2014. I remember I used to get these errors on my previous laptop, but that was on an older kernel before some things in intel drm were fixed. Can the original poster please reply back and give an update to whether they still receive this error or not? Thank you.

Edit:
This kernel bug report which is currently closed may be related: https://bugzilla.kernel.org/show_bug.cgi?id=79261

Loading...