From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Martin Peres <martin.peres@free.fr>
Cc: nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH 5/5] drm/nouveau: gpu lockup recovery
Date: Tue, 24 Apr 2012 21:31:50 +0200 [thread overview]
Message-ID: <20120424193150.GC2857@joi.lan> (raw)
In-Reply-To: <4F9589CC.1030909@free.fr>
On Mon, Apr 23, 2012 at 06:56:44PM +0200, Martin Peres wrote:
> Le 23/04/2012 18:32, Marcin Slusarz a écrit :
> >
> > Just run piglit. Even "quick" tests can cause ~5 lockups (it eventually messes
> > up DDX channel, but this patchset can't fix this case).
> > You can run fs-discard-exit-2 test first - for me it causes instant GPU lockup.
> >
> > Marcin
> Great, Thanks.
>
> Did you have a look at
> https://bugs.freedesktop.org/show_bug.cgi?id=40886 and
> http://xorg.freedesktop.org/wiki/SummerOfCodeIdeas ?
Yeah, I've seen them some time ago.
> The Ubuntu xorg devs were looking for something like this, but they also
> wanted a lockup report. Are you also interested on working on it ?
Yes, when this patchset will be applied, I'm going to work on improving
error reporting.
Marcin
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-04-24 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 22:18 [RFC PATCH 5/5] drm/nouveau: gpu lockup recovery Marcin Slusarz
2012-04-23 8:43 ` Martin Peres
2012-04-23 16:32 ` Marcin Slusarz
[not found] ` <20120423163257.GA2886-OI9uyE9O0yo@public.gmane.org>
2012-04-23 16:56 ` Martin Peres
2012-04-24 19:31 ` Marcin Slusarz [this message]
[not found] ` <20120424193150.GC2857-OI9uyE9O0yo@public.gmane.org>
2012-04-25 0:32 ` Ben Skeggs
2012-04-25 11:06 ` [Nouveau] " Christoph Bumiller
2012-04-23 16:46 ` Martin Peres
2012-04-23 17:33 ` Marcin Slusarz
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=20120424193150.GC2857@joi.lan \
--to=marcin.slusarz@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=martin.peres@free.fr \
--cc=nouveau@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox