mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: Greg KH <greg@kroah.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-usb@vger.kernel.org, werner@guyane.dyn-o-saur.com,
	Marcus Meissner <meissner@suse.de>,
	linux-kernel@vger.kernel.org,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: 2.6.33 bugs (USBFS, Intel graphic)
Date: Sat, 27 Feb 2010 14:17:14 +0200	[thread overview]
Message-ID: <84144f021002270417j4d690ad2qf5db26b2b6dad232@mail.gmail.com> (raw)
In-Reply-To: <84144f021002270415r7c61236elb0208cd5d0821ab5@mail.gmail.com>

On Sat, Feb 27, 2010 at 2:15 PM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On Sat, Feb 27, 2010 at 1:00 PM, Markus Rechberger
> <mrechberger@gmail.com> wrote:
>>> Linus, I know you didn't want to do a kzalloc, but it looks like this is
>>> the easiest/simplest thing to do, unless you can think of something
>>> else?
>>
>> do you have any idea what to cherrypick in order to get rid of that
>> flickering with the intel GM45?
>> The flickering itself occures randomly, it was not there with the
>> original Ubuntu kernel (2.6.31 with alot patches)
>> This is pretty much a standard graphicchip nowadays....
>
> Yeah, same here. I tried to bisect the damn thing but didn't find any
> single commit. I think the problem was introduced in in the DRM merge
> between 2.6.31 and 2.6.32-rc1. Some people suggested privately that it
> might be related to frame buffer compression. Unfortunately I wasn't
> able to revert that particular patch.

Btw, after I reinstalled Ubuntu 9.10 from scratch for unrelated
reasons, I haven't seen the flicker effect. Dunno if that's just a
coincidence or if userspace has something to do with the bug.

  reply	other threads:[~2010-02-27 12:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27  3:42 Markus Rechberger
2010-02-27  3:56 ` Greg KH
2010-02-27  4:05   ` Markus Rechberger
2010-02-27  4:18     ` Greg KH
2010-02-27  4:29       ` Linus Torvalds
2010-02-27  4:34         ` Markus Rechberger
2010-02-27  5:17           ` Greg KH
2010-02-27  5:26             ` Greg KH
2010-02-27  5:38               ` Markus Rechberger
2010-02-27  5:48                 ` Greg KH
2010-02-27 11:00                   ` Markus Rechberger
2010-02-27 12:15                     ` Pekka Enberg
2010-02-27 12:17                       ` Pekka Enberg [this message]
2010-02-27 16:49                         ` Jesse Barnes
2010-02-27 18:08                           ` Markus Rechberger
2010-02-27 22:33                             ` Markus Rechberger
2010-02-27 17:20             ` Alan Stern
2010-03-03  0:09               ` Greg KH
2010-03-05 21:37                 ` Markus Rechberger
2010-03-06 16:30                 ` Markus Rechberger
2010-03-06 17:06                   ` Greg KH
2010-03-06 20:04                     ` Alan Stern
2010-02-27  4:11 ` Linus Torvalds

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=84144f021002270417j4d690ad2qf5db26b2b6dad232@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=greg@kroah.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=meissner@suse.de \
    --cc=mrechberger@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=werner@guyane.dyn-o-saur.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®