All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Håvar Nøvik" <havar.novik@gmail.com>
Cc: Kristoffer Eriksson <kristoffer.ericson@gmail.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	alan@linux.intel.com
Subject: Re: Bug reports on the psb-gfx driver
Date: Wed, 18 Apr 2012 22:21:37 +0100	[thread overview]
Message-ID: <20120418222137.0303fe47@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CAJqTQGFD=CCRQGFrhiVk5dEp0bCZ7KbSOsd0HSi_jeSQ4yd9bg@mail.gmail.com>

> 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

  reply	other threads:[~2012-04-18 21:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJqTQGEe6rGw4_f-7o2DUZs1J9a=pACuX4KYkLfA0_McMC2Ukg@mail.gmail.com>
2012-04-17 11:25 ` Bug reports on the psb-gfx driver Kristoffer Eriksson
2012-04-17 12:35   ` Håvar Nøvik
2012-04-18 21:21     ` Alan Cox [this message]
2012-04-26 19:22       ` Kristoffer Eriksson
2012-04-22  9:46 ` Kristoffer Eriksson
2012-04-23 10:23   ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120418222137.0303fe47@pyramind.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=alan@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=havar.novik@gmail.com \
    --cc=kristoffer.ericson@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.