From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: xrandr "DP2 unknown connection" Date: Sat, 23 Oct 2010 11:05:11 +0100 Message-ID: <5b55a1$ierq76@fmsmga002.fm.intel.com> References: <1287821397.5515.13.camel@zwerg> <0d30dc$jv1ib9@orsmga001.jf.intel.com> <1287827993.5454.9.camel@zwerg> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by gabe.freedesktop.org (Postfix) with ESMTP id 4CE179E841 for ; Sat, 23 Oct 2010 03:05:14 -0700 (PDT) In-Reply-To: <1287827993.5454.9.camel@zwerg> 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: Alexey Fisher Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Sat, 23 Oct 2010 11:59:53 +0200, Alexey Fisher wrote: > Am Samstag, den 23.10.2010, 10:40 +0100 schrieb Chris Wilson: > > Which does not seem likely given that we only fail intel_dp_init for the > > memory allocation failure at the start. Some other form of memory > > corruption or bogosity? > > Tools to use? memtest86? memory_corruption_check_size=? The starting point would be to add drm.debug=0xf to your boot line and lets have a close look at what is going on during boot + discovery [dmesg]. -Chris -- Chris Wilson, Intel Open Source Technology Centre