From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= Subject: Re: [PATCH 1/4] drm/i915: promote FIFO underruns to DRM_ERROR Date: Fri, 20 Sep 2013 09:32:37 +0300 Message-ID: <20130920063237.GK4531@intel.com> References: <1379620838-1491-1-git-send-email-przanoni@gmail.com> <1379620838-1491-2-git-send-email-przanoni@gmail.com> <20130919201602.GA7745@nuc-i3427.alporthouse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mga14.intel.com (mga14.intel.com [143.182.124.37]) by gabe.freedesktop.org (Postfix) with ESMTP id 64360E5C2F for ; Thu, 19 Sep 2013 23:32:42 -0700 (PDT) Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Paulo Zanoni Cc: Intel Graphics Development , Paulo Zanoni List-Id: intel-gfx@lists.freedesktop.org On Thu, Sep 19, 2013 at 05:20:49PM -0300, Paulo Zanoni wrote: > 2013/9/19 Chris Wilson : > > On Thu, Sep 19, 2013 at 05:00:35PM -0300, Paulo Zanoni wrote: > >> From: Paulo Zanoni > >> > >> Linus recently complained about screen corruption when coming out of > >> DPMS on his Haswell machine, and he also mentioned there were no error > >> messages on the log. I think I can reproduce this problem, and when it > >> happens I get a "FIFO underrun" message, but since it's just > >> DRM_DEBUG_DRIVER it's hard to notice. So promote underruns to error > >> messages because reports containing "I'm getting a FIFO underrun on > >> pipe A" are way much better than "I'm getting a screen corruption". > > > > Sadly FIFO underruns on quite a few platforms are expected and > > unfixable. Others they are just expected. We reduced the error level > > because they are too noisy, and we were not in a position where the > > underrun was actionable. As we do not yet have the underrun feedback in > > place, I do not think we are ready for the onslaught of errors. > > > > At minimum, you should only set the error message for the platforms you > > intend to fix. > = > Hmmmm, yeah, I should have thought about this a little bit more. Sorry :( > = > At least on ILK/SNB/IVB/HSW we have the code to stop flooding dmesg > and the code to ignore the expected underruns, so I guess a patch > touching just these platforms would be ok? I would limit it to HSW before my ILK/SNB/IVB conversion to HSW watermark code gets in. The current code apparently produces somewhat incorrect results since according to Imre it even fixes some kind of rare hang on ILK. -- = Ville Syrj=E4l=E4 Intel OTC