Some days ago linux-image-2.6.32-14 was released, and one of the entries in
the changelog says:

* Add drm changes from stable 2.6.33.5:
- i915: Disable FBC on 915GM and 945GM (Closes: #582427)

I think that's the patch:

https://patchwork.kernel.org/patch/86999/

#582427 could be related to this issue. However, I just booted into 2.6.32-15
with powersave=1 commented out (this time I'm using modprobe.d instead of
defaults/grub, and I re-ran update-grub afterwards to make sure I really was
not setting powersave=0 or powersave=1) and the problem is still there (the
screen flickered several times in just a few minutes).



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: AANLkTim0zLgy3Oufi7I-fr4-qppPQmbXw_-fz92x1UGE@mail.gmail.com">http://lists.debian.org/AANLkTim0zLgy3Oufi7I-fr4-qppPQmbXw_-fz92x1UGE@mail.gmail.com

On Wed, Jun 2, 2010 at 20:04:21 -0300, Fernando Lemos wrote:

> Some days ago linux-image-2.6.32-14 was released, and one of the entries in
> the changelog says:
>
> * Add drm changes from stable 2.6.33.5:
> - i915: Disable FBC on 915GM and 945GM (Closes: #582427)
>
> I think that's the patch:
>
> https://patchwork.kernel.org/patch/86999/
>
> #582427 could be related to this issue. However, I just booted into 2.6.32-15
> with powersave=1 commented out (this time I'm using modprobe.d instead of
> defaults/grub, and I re-ran update-grub afterwards to make sure I really was
> not setting powersave=0 or powersave=1) and the problem is still there (the
> screen flickered several times in just a few minutes).
>
#582427 was about a different chip generation than this bug.

Cheers,
Julien