public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Dieter Mummenschanz <mummenschanz@gmx.net>
Cc: intel-gfx@lists.freedesktop.org, libva@lists.freedesktop.org
Subject: Re: frequent x crashes with gen6/sna
Date: Mon, 24 Oct 2011 09:22:18 +0200	[thread overview]
Message-ID: <20111024072218.GB2908@phenom.ffwll.local> (raw)
In-Reply-To: <20111018184704.GA2914@phenom.ffwll.local>

On Tue, Oct 18, 2011 at 08:47:04PM +0200, Daniel Vetter wrote:
> On Tue, Oct 18, 2011 at 09:52:32AM +0200, Dieter Mummenschanz wrote:
> > In this special case the gpu was successfully reset and continued normally. 
> > 
> > Any other ideas?
> 
> Not at the moment, unfortunately. Can you please report a bug against
> libva with a small summary of all the things we've already discussed here?
> Also please add a error_state with my patches applied. And don't forget to
> put me on cc and post the bug # here in this thread.

Any update on this? I've got other reports of libva related gpu hangs, but
you seem to be the only one who can grab the error_state ...

Yours, Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2011-10-24  7:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 20:20 frequent x crashes with gen6/sna Dieter Mummenschanz
     [not found] ` <20111017202009.183480-hi6Y0CQ0nG0@public.gmane.org>
2011-10-17 20:46   ` [Intel-gfx] " Daniel Vetter
     [not found]     ` <20111017204632.GL2971-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2011-10-18  7:52       ` Dieter Mummenschanz
2011-10-18 18:47         ` Daniel Vetter
2011-10-24  7:22           ` Daniel Vetter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-17 12:37 Dieter Mummenschanz
2011-10-17 13:16 ` [Intel-gfx] " Daniel Vetter
2011-10-17 13:54   ` Dieter Mummenschanz
2011-10-17 14:50     ` [Intel-gfx] " Daniel Vetter
2011-10-17 15:13       ` Dieter Mummenschanz
2011-10-17 15:48         ` Daniel Vetter
2011-10-17 16:01           ` Dieter Mummenschanz
2011-10-16  9:22 Dieter Mummenschanz
2011-10-16 16:18 ` Daniel Vetter
2011-10-16 17:06   ` Daniel Vetter
2011-10-17 11:45   ` Dieter Mummenschanz
2011-10-17 11:58     ` Daniel Vetter
2011-10-17 11:59       ` Daniel Vetter
2011-10-14 12:52 Dieter Mummenschanz
2011-10-14 16:01 ` Daniel Vetter
2011-10-14 16:03   ` Daniel Vetter
2011-10-14 19:27     ` Dieter Mummenschanz
2011-10-14 20:00       ` Daniel Vetter
2011-10-13 17:00 Dieter Mummenschanz
2011-10-13 16:36 Nicolas Kalkhof
2011-10-13 14:55 Dieter Mummenschanz
2011-10-13 16:24 ` Daniel Vetter
2011-10-13 13:45 Dieter Mummenschanz
2011-10-13 14:00 ` Daniel Vetter

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=20111024072218.GB2908@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=libva@lists.freedesktop.org \
    --cc=mummenschanz@gmx.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox