From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ted Phelps <phelps@gnusto.com>
Subject: Re: On SNB: Hangcheck timer elapsed... GPU hung
Date: Tue, 15 Feb 2011 11:46:58 +1000
Message-ID: <2131.1297734418@orpheus.gnusto.com>
References: <201102141318.p1EDIr2l006067@gnusto.com>
	<m2d3mue1a2.fsf@firstfloor.org>
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 laika.gnusto.com (laika.gnusto.com [207.44.178.75])
	by gabe.freedesktop.org (Postfix) with ESMTP id A068C9E794
	for <intel-gfx@lists.freedesktop.org>;
	Mon, 14 Feb 2011 17:47:13 -0800 (PST)
In-reply-to: Your message of Mon, 14 Feb 2011 13:47:49 PST.
	<m2d3mue1a2.fsf@firstfloor.org>
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: Andi Kleen <andi@firstfloor.org>
Cc: intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org


Hi Andy,

Andi Kleen writes:
> Ted Phelps <phelps@gnusto.com> writes:
> 
> > Apologies if this is a known issue, but I haven't been able to convince
> > myself that someone is looking after it.  I've been seeing this issue
> > with Linux kernel 2.6.37, 2.6.38-rc4 and the most recent merge of Linus's
> > git tree and drm-intel-fixes.  I'm happy to provide more information,
> > apply patches, run tools, read code, as requested.
> 
> Do you use displayport dual-head? I had this problem with dual head.
> No such issue with only a single monitor.

I'm using only one head attached to the DVI connector.

Thanks,
-Ted