All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Zdenek Kabelac <zdenek.kabelac@gmail.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: SNA crashes
Date: Thu, 24 May 2012 15:21:54 +0100	[thread overview]
Message-ID: <1337869332_225389@CP5-2952> (raw)
In-Reply-To: <CAJJYPdn7zf=XK=s0x+qb7bmfawrgwk7hWTsbbME5nC+p7SfD+A@mail.gmail.com>

On Thu, 24 May 2012 16:15:41 +0200, Zdenek Kabelac <zdenek.kabelac@gmail.com> wrote:
> Hi
> 
> Since I've started to use  SNA driver (when UXA appeared to be very
> slow), I'm  facing higher number of Xorg crashes.
> SNA is faster, but less stable then UXA is.

They are all debugging assertions caused by the earlier GPU hang, to
catch instances were we are losing commands and thus potentially
corrupting the output due to the loss of the GPU. Tip, don't hang the
GPU or don't ask for the bt.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-05-24 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 14:15 SNA crashes Zdenek Kabelac
2012-05-24 14:21 ` Chris Wilson [this message]
2012-05-27 11:25   ` Zdenek Kabelac
2012-05-27 15:22     ` Zdenek Kabelac

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=1337869332_225389@CP5-2952 \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=zdenek.kabelac@gmail.com \
    /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.