From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754099AbaEJIwe (ORCPT ); Sat, 10 May 2014 04:52:34 -0400 Received: from mail-oa0-f45.google.com ([209.85.219.45]:62651 "EHLO mail-oa0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752226AbaEJIwb convert rfc822-to-8bit (ORCPT ); Sat, 10 May 2014 04:52:31 -0400 MIME-Version: 1.0 In-Reply-To: <20140509170335.GZ18465@intel.com> References: <20140509161438.GH31479@strange.amr.corp.intel.com> <20140509170335.GZ18465@intel.com> Date: Sat, 10 May 2014 10:52:30 +0200 Message-ID: Subject: Re: [Intel-gfx] [3.14.0-rc4] regression: drm FIFO underruns From: =?UTF-8?Q?J=C3=B6rg_Otte?= To: =?UTF-8?B?VmlsbGUgU3lyasOkbMOk?= Cc: Damien Lespiau , David Airlie , Daniel Vetter , intel-gfx , Linux Kernel Mailing List , Dave Airlie , Linus Torvalds Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2014-05-09 19:03 GMT+02:00 Ville Syrjälä : > On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote: >> On Fri, May 09, 2014 at 06:11:37PM +0200, Jörg Otte wrote: >> > > Jörg, can you please boot with drm.debug=0xe, 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älä > Intel OTC It comes out on the boot-up screen which is normally clean. So it becomes highly visible for anyone. Thanks, Jörg