Bug 95367 - Screen suddenly goes black, [drm:valleyview_pipestat_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Summary: Screen suddenly goes black, [drm:valleyview_pipestat_irq_handler [i915]] *ERR...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-12 18:15 UTC by shdownnine
Modified: 2017-07-24 22:41 UTC (History)
1 user (show)

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


Attachments
dmesg after the black screen, when is not preceded by another *ERROR* message (918.63 KB, text/plain)
2016-05-12 18:15 UTC, shdownnine
no flags Details
dmesg after the black screen, when is preceded by another *ERROR* message (1001.14 KB, text/plain)
2016-05-12 18:16 UTC, shdownnine
no flags Details
output of lspci -vvv (27.50 KB, text/plain)
2016-05-12 18:17 UTC, shdownnine
no flags Details
[PATCH for v4.5] drm/i915: Fix watermarks for VLV/CHV (4.93 KB, patch)
2016-05-25 19:41 UTC, Ville Syrjala
no flags Details | Splinter Review
[PATCH for v4.6] drm/i915: Fix watermarks for VLV/CHV (5.35 KB, patch)
2016-05-25 19:42 UTC, Ville Syrjala
no flags Details | Splinter Review

Description shdownnine 2016-05-12 18:15:21 UTC
Created attachment 123650 [details]
dmesg after the black screen, when is not preceded by another *ERROR* message

I have the following issue on my Asus X751MJ laptop, with Linux kernels 4.5.0, 4.5.1 and 4.6-rc6 (does not happen on 4.4.0): at random moments the screen goes black (that is, the backlight gets turned off) and only goes unblack when I move a mouse attached to the laptop or touch the touchpad; this is not a usual pover-saving thing because it usually occurs when I switch between workspaces (I use i3wm). With 4.5.0 and 4.5.1 kernels a reliable way to reproduce it is to open two workspaces and run

    while true; do i3-msg workspace back_and_forth >/dev/null; done

In a few seconds the screen will go black; with 4.6-rc6 kernel the script does not reproduce the issue, and it generally occurs rarer, but still does.

The same thing happens if I run

    xset dpms force off

(but in this case it also goes unblack if I press a key).

When it goes black at the first time after the boot or a suspend, the following lines appear in dmesg:

[drm:valleyview_pipestat_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

Sometimes it is preceded by the following line:

[drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* pipe A underrun

The laptop has hybrid graphics, and Intel card plus an NVIDIA one. Initially nouveau was installed, then I tried installing the proprietary NVIDIA driver, but that did not help. Now I removed it, configured X11 to use the Intel card only and even blacklisted the nouveau module, but I didn't help either.
Comment 1 shdownnine 2016-05-12 18:16:40 UTC
Created attachment 123651 [details]
dmesg after the black screen, when is preceded by another *ERROR* message
Comment 2 shdownnine 2016-05-12 18:17:20 UTC
Created attachment 123652 [details]
output of lspci -vvv
Comment 3 Ville Syrjala 2016-05-25 19:41:34 UTC
Created attachment 124090 [details] [review]
[PATCH for v4.5] drm/i915: Fix watermarks for VLV/CHV

Backport of VLV/CHV watermark fix for 4.5. Please test.
Comment 4 Ville Syrjala 2016-05-25 19:42:17 UTC
Created attachment 124091 [details] [review]
[PATCH for v4.6] drm/i915: Fix watermarks for VLV/CHV

Backport of VLV/CHV watermark fix for 4.6. Please test.
Comment 5 shdownnine 2016-05-26 18:41:45 UTC
(In reply to Ville Syrjala from comment #3)
> Created attachment 124090 [details] [review] [review]
> [PATCH for v4.5] drm/i915: Fix watermarks for VLV/CHV
> 
> Backport of VLV/CHV watermark fix for 4.5. Please test.

Yep, it fixes the issue — switching workspaces in loop does not reproduce it anymore. As for the patch for 4.6, I built a kernel with it applied and so far it’s OK, but since I don’t know a reliable way to reproduce it, I can’t say for sure. I’ll reopen if I notice it again.

Thanks!


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.