From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kristoffer Eriksson Subject: Re: Bug reports on the psb-gfx driver Date: Thu, 26 Apr 2012 21:22:21 +0200 Message-ID: <4F99A06D.6070401@gmail.com> References: <4F8D532E.4000305@gmail.com> <20120418222137.0303fe47@pyramind.ukuu.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20120418222137.0303fe47@pyramind.ukuu.org.uk> Sender: linux-kernel-owner@vger.kernel.org To: Alan Cox Cc: =?ISO-8859-1?Q?H=E5var_N=F8vik?= , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, alan@linux.intel.com List-Id: dri-devel@lists.freedesktop.org Alan Cox skrev 2012-04-18 23:21: >> That frequency seems about the same as the one I'm experiences. All = though >> some times it's more often, but I can't say I've done anything speci= al at >> the same time. >> >> 3.3.2-1-ARCH >> Intel(R) Atom(TM) CPU Z520 @ 1.33GHz >> >> Attachment: dmesg ouput >> > What X display server are you using (fbdev or other ?). Also I see a = few > writes to the brightness in the log - did you fiddle with the brightn= ess > by hand at all ? Alan, Without looking at the code I can say that those brightness commands ar= e=20 not related to this issue since Ive been having them since the first working kernel version= =2E Havent had time to look at the code but Ive understod them to happen=20 simply when you press a key to return from backlight suspend. Something like the defaul= t=20 brightness setting that gets invoked after return from suspend. H=E5var see [ 7659.177126] gma500 0000:00:02.0: Backlight lvds set brightness 186a1= 86a while I see [....] gma500 0000:00:02.0: Backlight lvds set brightness 7a127a12 > > Either way I suspect the only way to find this is to verify a > configuration it occurs on, go back a kernel, verify it doesn't happe= n > there and then build a kernel to the point in the git tree before the > gma500 patches were changed (to check its not caused by something els= e > such as an ACPI change), then try and find which one caused it. Will do further fresh builds to see if I can reproduce the blanking=20 issue and also test out the patch. > That will be tedious but unfortunately I've got no documentation or o= ther > good ways to chase this down. > > Alan >