All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Phelps <phelps@gnusto.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: On SNB: Hangcheck timer elapsed... GPU hung
Date: Tue, 15 Feb 2011 11:46:58 +1000	[thread overview]
Message-ID: <2131.1297734418@orpheus.gnusto.com> (raw)
In-Reply-To: Your message of Mon, 14 Feb 2011 13:47:49 PST. <m2d3mue1a2.fsf@firstfloor.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

  parent reply	other threads:[~2011-02-15  1:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 13:18 On SNB: Hangcheck timer elapsed... GPU hung Ted Phelps
     [not found] ` <m2d3mue1a2.fsf@firstfloor.org>
2011-02-15  1:46   ` Ted Phelps [this message]
2011-02-16 13:13     ` Ivan Bulatovic
2011-02-16 13:20       ` Andrew Lutomirski
2011-02-16 13:33         ` Ivan Bulatovic
2011-02-16 13:45           ` Andrew Lutomirski
2011-02-16 14:02             ` Ivan Bulatovic
     [not found]               ` <19567.1297946336@orpheus.gnusto.com>
2011-02-22 17:26                 ` Ivan Bulatovic
2011-02-22 18:23                   ` Ivan Bulatovic
2011-02-21  5:12         ` Andrew Lutomirski
2011-02-15  9:32 ` Jin, Gordon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2131.1297734418@orpheus.gnusto.com \
    --to=phelps@gnusto.com \
    --cc=andi@firstfloor.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.