linux-kernel - Re: Bug reports on the psb-gfx driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 18 Apr 2012 22:21:37 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Håvar Nøvik <havar.novik@...il.com>
Cc:	Kristoffer Eriksson <kristoffer.ericson@...il.com>,
	linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
	alan@...ux.intel.com
Subject: Re: Bug reports on the psb-gfx driver

> 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 special 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 brightness
by hand at all ?

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 happen
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 else
such as an ACPI change), then try and find which one caused it.

That will be tedious but unfortunately I've got no documentation or other
good ways to chase this down.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/