Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967707Ab0B0MPK (ORCPT ); Sat, 27 Feb 2010 07:15:10 -0500 Received: from mail-fx0-f219.google.com ([209.85.220.219]:40699 "EHLO mail-fx0-f219.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966055Ab0B0MPH (ORCPT ); Sat, 27 Feb 2010 07:15:07 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=CEkB4SprF6Hnm/gC09ROIFAZA8+H/XpOWP7JHNA3HgaRDWjzJ9cW0vgZuWjdHYJkeF 41piWsDkQHQAhIR92OroW3NQ1wq4ogwXtNlEg+rdNNTEUvq+uZlQp4/voA51QyDZatMB 9g3on+0ogqKoisstqV2Lo4RmHjg6w5X3EBOgI= MIME-Version: 1.0 In-Reply-To: References: <20100227041815.GA12956@kroah.com> <20100227051737.GA14976@kroah.com> <20100227052648.GA31418@kroah.com> <20100227054808.GA32225@kroah.com> Date: Sat, 27 Feb 2010 14:15:06 +0200 X-Google-Sender-Auth: 11628e85955743dc Message-ID: <84144f021002270415r7c61236elb0208cd5d0821ab5@mail.gmail.com> Subject: Re: 2.6.33 bugs (USBFS, Intel graphic) From: Pekka Enberg To: Markus Rechberger Cc: Greg KH , Linus Torvalds , linux-usb@vger.kernel.org, werner@guyane.dyn-o-saur.com, Marcus Meissner , linux-kernel@vger.kernel.org, Jesse Barnes Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1117 Lines: 24 On Sat, Feb 27, 2010 at 1:00 PM, Markus Rechberger 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. Pekka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/