From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alexey Fisher <bug-track@fisher-privat.net>
Subject: Re: xrandr "DP2 unknown connection"
Date: Sat, 23 Oct 2010 11:59:53 +0200
Message-ID: <1287827993.5454.9.camel@zwerg>
References: <1287821397.5515.13.camel@zwerg>
	<b9dded$gsedkb@orsmga002.jf.intel.com>
	<0d30dc$jv1ib9@orsmga001.jf.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22])
	by gabe.freedesktop.org (Postfix) with SMTP id E35839E841
	for <intel-gfx@lists.freedesktop.org>;
	Sat, 23 Oct 2010 02:59:55 -0700 (PDT)
In-Reply-To: <0d30dc$jv1ib9@orsmga001.jf.intel.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=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: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

Am Samstag, den 23.10.2010, 10:40 +0100 schrieb Chris Wilson:
> On Sat, 23 Oct 2010 10:34:38 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > On Sat, 23 Oct 2010 10:09:57 +0200, Alexey Fisher <bug-track@fisher-privat.net> wrote:
> > > Hi,
> > > xrandr report me new connection i never seen before 
> > > "DP2 unknown connection". There is only DVI monitor attached to this
> > > board. kernel 2.6.36-rc8-01148-g3c17fe4 from intel_drm_next
> > 
> > So unknown connection is only reported for DP if the structure does not
> > match one of the known registers. Sounds like we bailed during
> > initialisation, but after hooking the structure into the drm connector
> > list.
> 
> 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=?