From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Kaiser Subject: Re: Sandy Bridge (i7/H67) and connected screens Date: Fri, 29 Apr 2011 16:39:46 +0200 Message-ID: References: <1bdc18$jp5hb6@fmsmga002.fm.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by gabe.freedesktop.org (Postfix) with ESMTP id 907CB9E837 for ; Fri, 29 Apr 2011 07:40:03 -0700 (PDT) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QForQ-0000kr-Mx for intel-gfx@lists.freedesktop.org; Fri, 29 Apr 2011 16:40:00 +0200 Received: from 88-117-87-152.adsl.highway.telekom.at ([88.117.87.152]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 Apr 2011 16:40:00 +0200 Received: from kairo by 88-117-87-152.adsl.highway.telekom.at with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 Apr 2011 16:40:00 +0200 In-Reply-To: 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: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org Chris Wilson schrieb: > On Fri, 04 Mar 2011 22:09:42 +0100, Robert Kaiser wrote: >> Chris Wilson schrieb: >>> Let's start by looking at the dmesg and Xorg.log and then determine what's >>> wrong. If you add drm.debug=0xe to your grub kernel parameters, so much >>> the better. >> >> OK, I launched with that parameter and found by logging in from my N900 >> a way to drop dmesg into a file and take a copy of Xorg.0.log, so here >> they are in an attachment. >> Just if you might need it, when this ran, the newer 1920x1080 monitor >> was plugged in on the DVI port and I think I had the HDMI one not >> plugged in at all. > > This is the cause of the trouble: > > [ 3.042320] i915 GPIOB: SDA stuck high! > [ 3.045553] i915 GPIOA: SDA stuck low! > [ 3.045625] i915 GPIOC: SDA stuck high! > [ 3.049540] i915 GPIOD: SDA stuck low! > [ 3.049612] i915 GPIOE: SDA stuck high! > [ 3.049694] i915 GPIOF: SDA stuck high! > > First time I've ever seen that, though that is maybe because it is in a > non-default debugging path. > > However, failing the i2c bitbanging adapter being created, we would be > using the GMBUS interface. That appears to be failing as well. (Not too > surprising since it uses the same ports internally.) > > Not sure how to proceed, maybe someone else has a better idea? Any update? I just have changed to a different DH67CL board (now with "B3 stepping") and I'm running on 2.6.29-rc4 but the symptoms stay the same (didn't create another debug log to verify the exact error though). I doubt that two board would have the same hardware error to cause that and I also doubt that both my screens are busted (esp. as one works with this board with vesafb/nomodeset=1 mode at least), so I suspect there really is something in the drivers that goes wrong. It's a bit disappointing that with an all-Intel solution I end up like that, has anyone of you guys tried a DH67CL + i7-2600 yourself? I really hope you/we can find a solution to this! Robert Kaiser