From: Chris Wilson Subject: Re: KMS broken from 2.6.33 up to 2.6.35-rc5???? Date: Sun, 18 Jul 2010 13:57:27 +0100 Message-ID: <8u3s94$fvmkvd@orsmga002.jf.intel.com> References: <4C42F3AE.6010906@mmmm.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by gabe.freedesktop.org (Postfix) with ESMTP id ED6DC9E7FF for ; Sun, 18 Jul 2010 05:57:30 -0700 (PDT) In-Reply-To: <4C42F3AE.6010906@mmmm.it> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Massimo Maggi , intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Sun, 18 Jul 2010 14:29:34 +0200, Massimo Maggi wrote: > I've set up a very minimal kernel config (the resulting kernel is not > useful for anything except showing the problem), and built versions: > 2.6.32.16 > 2.6.33.6 > 2.6.34.1 > 2.6.35-rc5 > Only 2.6.32.16 is able to correctly initialize the framebuffer. Excellent, as you have managed to reproduce this with a minimal kernel, can you do a bisect between 2.6.33.16 and 2.6.33.6 and see which patch causes the regression? It should only take a couple of hours. My bet is one of the Arrandale enabling patches... -- Chris Wilson, Intel Open Source Technology Centre