dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Petko Manolov <petkan@mip-labs.com>
To: Daniel Vetter <daniel.vetter@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [drm:intel_set_cpu_fifo_underrun_reporting]
Date: Fri, 24 Jun 2016 11:25:56 +0300	[thread overview]
Message-ID: <20160624082556.GC19933@p310> (raw)
In-Reply-To: <20160613123551.GA3026@localhost>

On 16-06-13 15:35:51, Petko Manolov wrote:
> On 16-06-13 13:29:46, Petko Manolov wrote:
> > 	Hello guys,
> > 
> > Running xorg on my Lenovo Yoga 2 Pro (MY2013) on recent kernels turn into a 
> > major PITA.  After a couple of minutes the screen starts to flicker and only 
> > killing xorg or reboot fixes the problem.  This is what i typically see in 
> > dmesg:
> > 
> > 
> > [    0.000000] microcode: microcode updated early to revision 0x1d, date = 2015-08-13
> > [    0.000000] Linux version 4.7.0-rc3 (petkan@yoga) (gcc version 6.1.1 20160519 (Debian 6.1.1-4) ) #5 SMP Mon Jun 13 12:41:31 EEST 2016
> > [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc3 root=/dev/sda1 ro quiet
> > ...
> > [    0.104213] smpboot: CPU0: Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz (family: 0x6, model: 0x45, stepping: 0x1)
> > ...
> > [    1.033691] [drm] Initialized drm 1.1.0 20060810
> > [    1.034106] [drm] Memory usable by graphics device = 2048M
> > [    1.034108] [drm] Replacing VGA console driver
> > [    1.040787] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> > [    1.040788] [drm] Driver supports precise vblank timestamp query.
> > [    1.066820] [drm] Initialized i915 1.6.0 20160425 for 0000:00:02.0 on minor 0
> > [    1.231007] fbcon: inteldrmfb (fb0) is primary device
> > [    2.524538] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
> > ...
> > [   92.825302] [drm:intel_set_cpu_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe A
> > [   92.825312] [drm:ironlake_irq_handler] *ERROR* CPU pipe A FIFO underrun
> > 
> > 
> > This is going on for all v4.6 kernel releases as well as v4.7-rcX.  Older, 
> > v4.4 and v4.5, kernels are running fine.  I'm using Debian testing updated to 
> > 2016-06-13.
> > 
> > I'd be happy to help with testing so please let me know if there's anything i 
> > can do for you.
> 
> It seems that James (Bottomley) has similar problem and it was suggested to him 
> to try drm-intel-nightly.  Which i did, but it didn't help much.  Admittedly, 
> the flicker issue showed up after about an hour instead of a couple of minutes.
> 
> The 'dmesg' output seems very much like what i posted above.

It does not look like you guys care, but just for completeness and in case 
anybody is reading the thread: i915.enable_psr=0 did the trick for me.


		Petko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-06-24  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 10:29 [drm:intel_set_cpu_fifo_underrun_reporting] Petko Manolov
2016-06-13 12:35 ` [drm:intel_set_cpu_fifo_underrun_reporting] Petko Manolov
2016-06-24  8:25   ` Petko Manolov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160624082556.GC19933@p310 \
    --to=petkan@mip-labs.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).