From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: vsync + vaapi question
Date: Wed, 13 Jan 2016 14:12:10 +0100 [thread overview]
Message-ID: <20160113131210.GN1925@ics.muni.cz> (raw)
In-Reply-To: <20151224194201.GB1975@ics.muni.cz>
Hi,
On Thu, Dec 24, 2015 at 08:42:01PM +0100, Lukas Hejtmanek wrote:
> > Hard? The fault isn't in libva this time at least.
>
> applied patch results in hard lockup when playing a movie (short sound loop
> and even sysrq keys are not working). I thought that driver would reset gpu
> eventualy but it seems to be completely dead.
>
> So I reverted the patch and it seems lockups are gone.
For ubuntu, that vaapi sync patch just landed. Had to switch to xv from vaapi
to avoid frequent lockup. Anything out there I can try to fix lockups?
--
Lukáš Hejtmánek
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-01-13 13:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 18:08 vsync + vaapi question Lukas Hejtmanek
2015-12-22 20:54 ` Chris Wilson
2015-12-22 22:25 ` Lukas Hejtmanek
2015-12-23 12:01 ` Chris Wilson
2015-12-23 12:13 ` Lukas Hejtmanek
2015-12-23 13:38 ` Chris Wilson
2015-12-24 9:44 ` Lukas Hejtmanek
2015-12-24 15:50 ` Chris Wilson
2015-12-24 19:28 ` Lukas Hejtmanek
2015-12-24 19:37 ` Chris Wilson
2015-12-24 19:42 ` Lukas Hejtmanek
2015-12-24 19:55 ` Chris Wilson
2015-12-24 19:59 ` Lukas Hejtmanek
2015-12-24 20:05 ` Chris Wilson
2015-12-24 22:15 ` Lukas Hejtmanek
2015-12-24 22:22 ` Chris Wilson
2015-12-24 22:25 ` Lukas Hejtmanek
2015-12-24 23:54 ` Robert Hooker
2015-12-26 15:40 ` Lukas Hejtmanek
2016-01-13 13:12 ` Lukas Hejtmanek [this message]
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=20160113131210.GN1925@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox