Bug 106829 - Screen flicker in kernel 4.16, fine in 4.15
Summary: Screen flicker in kernel 4.16, fine in 4.15
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) 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: 2018-06-05 20:31 UTC by Henry Baldursson
Modified: 2018-06-08 09:30 UTC (History)
1 user (show)

See Also:
i915 platform: KBL
i915 features:


Attachments
dmesg (58.55 KB, text/plain)
2018-06-05 20:31 UTC, Henry Baldursson
no flags Details
attachment-5188-0.html (1.78 KB, text/html)
2018-06-06 01:21 UTC, Henry Baldursson
no flags Details

Description Henry Baldursson 2018-06-05 20:31:52 UTC
Created attachment 140036 [details]
dmesg

-- system architecture: x86_64
-- kernel version: Linux version 4.16.13-1-ARCH (builduser@heftig-15406) (gcc version 8.1.0 (GCC)) #1 SMP PREEMPT Thu May 31 23:29:29 UTC 2018
-- Linux distribution: Antergos (Arch clone)
-- Machine or mother board model: Lenovo Yoga 910, Core i7-7500U, HD Graphics 620
-- Display connector: Integral

-- Kernel command line params: quiet drm.debug=0x1e log_buf_len=1M i915.enable_rc6=0 i915.enable_psr=0 i915.enable_guc_loading=1 i915.enable_guc_submission=1
(most of those are as a result of me trying to fix this on my own)


I've waited for this to clear up, but it hasn't so either my system is misconfigured or I'm running into a bug.

The error logged is this: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

Here's a GIF of what I'm seeing: https://gfycat.com/UnsightlyWellinformedAlligator

I'm running Wayland 1.15.0, Gnome 3.28.2, GDM 3.28.1.

As soon as I boot a 4.16 kernel the screen starts flickering. Downgrading to 4.15.11 fixes it right up.

I can't dump vbios as I get an Input/Output error. Never messed with that before so no idea if related.

== dmesg (also attached): https://pastebin.com/JkQsCmLs
== intel_reg dump: https://pastebin.com/PjQsYQFp

Any ideas?
Comment 1 Chris Wilson 2018-06-05 23:24:35 UTC
Did you try intel_iommu=igfx_off? Of the options you set, the only vaguely relevant one is i915.enable_psr=0 which is the default.
Comment 2 Henry Baldursson 2018-06-06 01:21:56 UTC
Created attachment 140040 [details]
attachment-5188-0.html

Hey thanks for the reply.

I tried that param just now to no avail.

On Tue, 5 Jun 2018 at 23:26, <bugzilla-daemon@freedesktop.org> wrote:

> *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=106829#c1> on
> bug 106829 <https://bugs.freedesktop.org/show_bug.cgi?id=106829> from Chris
> Wilson <chris@chris-wilson.co.uk> *
>
> Did you try intel_iommu=igfx_off? Of the options you set, the only vaguely
> relevant one is i915.enable_psr=0 which is the default.
>
> ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
>
Comment 3 Francesco Balestrieri 2018-06-06 04:13:03 UTC
Juat to be sure, can you try this with the latest drm-tip?
Comment 4 Henry Baldursson 2018-06-07 19:55:43 UTC
(In reply to Francesco Balestrieri from comment #3)
> Juat to be sure, can you try this with the latest drm-tip?

Well, this is awkward. I tried installing drm-tip with defaultconf. But it's been a long time since I've compiled a kernel. Anyway, I failed, bricked my root partition, and ended up having to reinstall. A fresh install of Antergos with kernel 4.16.13-2-ARCH is working fine without any flicker.



Sigh

Unneccessary embarrassing info:
(What I'd done was, I had a way too small /boot partition, 64mb. When I was trying to boot into the drm-tip I forgot that I'd need a driver module to access my ssd. So I didn't have a initramfs and no way to fit it, also I wasn't sure if using the other initramfs would work as I didn't know where the actual i915 driver was. Frustrated, I decided to resize my root so I could fit a bigger boot. Misjudged some calculations and ended up with a filesystem that thought it was slightly bigger than its partition, I couldn't get out of a fsck/resize2fs catch 22, so I just said f-it and reinstalled, since I have all my data on a separate /home partition.)
Comment 5 Francesco Balestrieri 2018-06-08 04:55:37 UTC
Sorry for having led you to a reinstall. The silver lining is that we can close this bug...


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.