[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#601997: marked as done ([i915] Irregular sync flashes on gm45)



Your message dated Sun, 12 Jun 2011 20:56:40 -0500
with message-id <20110613015640.GA2995@elie>
and subject line Re: [drm/i915] flickering and artifacts on (some?) gm45 with powersave
has caused the Debian Bug report #580601,
regarding [i915] Irregular sync flashes on gm45
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
580601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580601
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: base
Severity: normal


A report was filed on Launchpad against Ubuntu Lucid reporting that the kernel upgrade from Karmic to Lucid
introduced irregular sync flashes on the screen.  cf.
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/538648.

The problem reported there is also seeming to affect Debian Squeeze.

The upgrade to Ubuntu Maverick has caused the problem to go away when using that OS.  Sadly though the
problem still afflicts Debian Squeeze.  Is there any way the information from the Ubuntu-oriented
investigation can be applied to Debian Squeeze?

The flashes are really, really irritating.

Thanks.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
found 580601 linux-2.6/2.6.36-1~experimental.1
quit
Version: 2.6.37-1~experimental.1

Fernando Lemos wrote:

> I can no longer reproduce this in 2.6.37. After the update to 2.6.37,
> I commented out "options i915 powersave=0" from modprobe.d and used
> update-initramfs -k all -u. That was more than a week ago (probably
> two weeks ago), and so far I haven't seen any corruption at all. I've
> been switching between 2.6.36 and 2.6.37 recently so that I can use
> VirtualBox (linux-kbuild-2.6.37 isn't released yet, so I can't compile
> virtualbox-ose-dkms for 2.6.37), and every time I'm booted into 2.6.36
> I can see the corruption every now and then

Thanks!  Marking accordingly.

Maybe something in the "drm/i915: use GMBUS to manage i2c links"
series or something like "drm/i915: Disable FBC on Ironlake to save
1W" or "drm/i915: Fix updating FBC" did the trick.  If someone has
time to bisect the fix to track down what patches to backport, that
would be nice.


--- End Message ---

Reply to: