From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= Subject: Re: [3.14.0-rc4] regression: drm FIFO underruns Date: Fri, 9 May 2014 20:03:35 +0300 Message-ID: <20140509170335.GZ18465@intel.com> References: <20140509161438.GH31479@strange.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by gabe.freedesktop.org (Postfix) with ESMTP id CCA906E00C for ; Fri, 9 May 2014 10:05:26 -0700 (PDT) Content-Disposition: inline In-Reply-To: <20140509161438.GH31479@strange.amr.corp.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Damien Lespiau Cc: David Airlie , Daniel Vetter , intel-gfx , Linux Kernel Mailing List , =?iso-8859-1?Q?J=F6rg?= Otte , Dave Airlie , Linus Torvalds List-Id: intel-gfx@lists.freedesktop.org On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote: > On Fri, May 09, 2014 at 06:11:37PM +0200, J=F6rg Otte wrote: > > > J=F6rg, can you please boot with drm.debug=3D0xe, reproduce the issue= and > > > then attach the complete dmesg? Please make sure that the dmesg > > > contains the boot-up stuff too. > > > > > > Thanks, Daniel > > Here it is. I should mention it only happens at boot-up. > = > [ 0.374095] [drm] Wrong MCH_SSKPD value: 0x20100406 > [ 0.374096] [drm] This can cause pipe underruns and display issues. > [ 0.374097] [drm] Please upgrade your BIOS to fix this. That can be a factor, but I think we may have some more general issue in the modeset sequence which causes these to get reported. I'm getting some on my machine as well where SSKPD looks more sane. Maybe we turn on the error reporting too early or something. But I'm not going to spend time worrying about these before my previous watermark stuff gets merged. Also the underrun reporting code itself would need some kind of rewrite to be really useful. If the display doesn't blank out during use everything is more or less fine and you can ignore these errors. It's quite likely that the errors were always present and you didn't know it. We just made them more prominent recently. -- = Ville Syrj=E4l=E4 Intel OTC