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
On Thu, Dec 24, 2015 at 06:54:44PM -0500, Robert Hooker wrote:
> The 3.19 distro kernel in ubuntu is using 4.2-ish drm backported on broadwell,
> try http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-ckt12-vivid/
> instead which is stock upstream.
tried, lockup as well..
--
Lukáš Hejtmánek
_
On Thu, Dec 24, 2015 at 5:25 PM, Lukas Hejtmanek wrote:
> On Thu, Dec 24, 2015 at 10:22:24PM +, Chris Wilson wrote:
>> > tried 3.19.0-42 from ubuntu. lockup as well it just took more time..
>>
>> Hmm. What hardware? Baytrail?
>
> Lenovo X1 Carbon 2015. Intel(R) HD Graphics 5500 (according to l
On Thu, Dec 24, 2015 at 10:22:24PM +, Chris Wilson wrote:
> > tried 3.19.0-42 from ubuntu. lockup as well it just took more time..
>
> Hmm. What hardware? Baytrail?
Lenovo X1 Carbon 2015. Intel(R) HD Graphics 5500 (according to log)
pci id 8086:1616 (rev 09)
--
Lukáš Hejtmánek
On Thu, Dec 24, 2015 at 11:15:57PM +0100, Lukas Hejtmanek wrote:
> On Thu, Dec 24, 2015 at 08:05:33PM +, Chris Wilson wrote:
> > On Thu, Dec 24, 2015 at 08:59:49PM +0100, Lukas Hejtmanek wrote:
> > > On Thu, Dec 24, 2015 at 07:55:42PM +, Chris Wilson wrote:
> > > > That's a kernel panic or
On Thu, Dec 24, 2015 at 08:05:33PM +, Chris Wilson wrote:
> On Thu, Dec 24, 2015 at 08:59:49PM +0100, Lukas Hejtmanek wrote:
> > On Thu, Dec 24, 2015 at 07:55:42PM +, Chris Wilson wrote:
> > > That's a kernel panic or total machine lockup. Do you have a few
> > > different kernels you can t
On Thu, Dec 24, 2015 at 08:59:49PM +0100, Lukas Hejtmanek wrote:
> On Thu, Dec 24, 2015 at 07:55:42PM +, Chris Wilson wrote:
> > That's a kernel panic or total machine lockup. Do you have a few
> > different kernels you can try? Hopefully it's a recent regression.
>
> the same for ubuntu's ker
On Thu, Dec 24, 2015 at 07:55:42PM +, Chris Wilson wrote:
> That's a kernel panic or total machine lockup. Do you have a few
> different kernels you can try? Hopefully it's a recent regression.
the same for ubuntu's kernel 4.2.0 and 4.3.0.
--
Lukáš Hejtmánek
On Thu, Dec 24, 2015 at 08:42:01PM +0100, Lukas Hejtmanek wrote:
> On Thu, Dec 24, 2015 at 07:37:18PM +, Chris Wilson wrote:
> > > huh, maybe it is not good idea. Had to revert it because of number of
> > > hard
> > > lockups :(
> > >
> > > or are there any patches I can try to fix those loc
On Thu, Dec 24, 2015 at 07:37:18PM +, Chris Wilson wrote:
> > huh, maybe it is not good idea. Had to revert it because of number of hard
> > lockups :(
> >
> > or are there any patches I can try to fix those lockups?
>
> Hard? The fault isn't in libva this time at least.
applied patch resul
On Thu, Dec 24, 2015 at 08:28:25PM +0100, Lukas Hejtmanek wrote:
> On Thu, Dec 24, 2015 at 03:50:17PM +, Chris Wilson wrote:
> > On Thu, Dec 24, 2015 at 10:44:46AM +0100, Lukas Hejtmanek wrote:
> > > On Wed, Dec 23, 2015 at 01:38:26PM +, Chris Wilson wrote:
> > > > Try (libva):
> > >
> > >
On Thu, Dec 24, 2015 at 03:50:17PM +, Chris Wilson wrote:
> On Thu, Dec 24, 2015 at 10:44:46AM +0100, Lukas Hejtmanek wrote:
> > On Wed, Dec 23, 2015 at 01:38:26PM +, Chris Wilson wrote:
> > > Try (libva):
> >
> > seems to be much better. I got one lockup though but it may be unrelated.
>
On Thu, Dec 24, 2015 at 10:44:46AM +0100, Lukas Hejtmanek wrote:
> On Wed, Dec 23, 2015 at 01:38:26PM +, Chris Wilson wrote:
> > Try (libva):
>
> seems to be much better. I got one lockup though but it may be unrelated.
Unfortunately probably related, since we now enforce synchronisation to
v
On Wed, Dec 23, 2015 at 01:38:26PM +, Chris Wilson wrote:
> Try (libva):
seems to be much better. I got one lockup though but it may be unrelated.
Thanks, hope you push it into mainstream.
> diff --git a/va/x11/dri2_util.c b/va/x11/dri2_util.c
> index d076fb3..9ff5e95 100644
> --- a/va/x11/d
On Wed, Dec 23, 2015 at 01:13:46PM +0100, Lukas Hejtmanek wrote:
> On Wed, Dec 23, 2015 at 12:01:44PM +, Chris Wilson wrote:
> > The clipped extents of the va-api Window is used to determine which CRTC
> > to use as the vblank source. Hmm, the Primary Output is used as the
> > preference (i.e.
On Wed, Dec 23, 2015 at 12:01:44PM +, Chris Wilson wrote:
> The clipped extents of the va-api Window is used to determine which CRTC
> to use as the vblank source. Hmm, the Primary Output is used as the
> preference (i.e. if any part of that Window is on the Primary, it is
> used as the CRTC -
On Tue, Dec 22, 2015 at 11:25:53PM +0100, Lukas Hejtmanek wrote:
> On Tue, Dec 22, 2015 at 08:54:08PM +, Chris Wilson wrote:
> > Not really. The Primary output will be used as the vsync so long as a
> > single pixel of the Window is upon it. Fundamentally, we need to use the
> > output that the
On Tue, Dec 22, 2015 at 08:54:08PM +, Chris Wilson wrote:
> Not really. The Primary output will be used as the vsync so long as a
> single pixel of the Window is upon it. Fundamentally, we need to use the
> output that the Window is on in order to driver the vblank update.
Which window? Any wi
On Fri, Dec 18, 2015 at 07:08:11PM +0100, Lukas Hejtmanek wrote:
> Hello,
>
> is it possible to switch vsync from internal LCD (laptop) to external monitor
> when playing movie via VA-API? I can drop vsync with internal LCD and keep
> vsync only with external monitor. I tried to use --primary for
Hello,
is it possible to switch vsync from internal LCD (laptop) to external monitor
when playing movie via VA-API? I can drop vsync with internal LCD and keep
vsync only with external monitor. I tried to use --primary for excernal
monitor when enabling output but no luck.
Is there any way to sy
20 matches
Mail list logo
