| Message ID | 20151223133826.GU5896@nuc-i3427.alporthouse.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Wed, Dec 23, 2015 at 01:38:26PM +0000, 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/dri2_util.c > +++ b/va/x11/dri2_util.c > @@ -95,8 +95,9 @@ dri2SwapBuffer(VADriverContextP ctx, struct dri_drawable *dri_drawable) > if (dri2_drawable->has_backbuffer) { > if (gsDRI2SwapAvailable) { > CARD64 ret; > - VA_DRI2SwapBuffers(ctx->native_dpy, dri_drawable->x_drawable, 0, 0, > - 0, &ret); > + VA_DRI2SwapBuffers(ctx->native_dpy, dri_drawable->x_drawable, > + 0, 1, 0, > + &ret); > } else { > xrect.x = 0; > xrect.y = 0; > > -- > Chris Wilson, Intel Open Source Technology Centre
On Thu, Dec 24, 2015 at 10:44:46AM +0100, Lukas Hejtmanek wrote: > On Wed, Dec 23, 2015 at 01:38:26PM +0000, 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 vblank there are a few more bit and pieces involved. > Thanks, hope you push it into mainstream. Patch sent. -Chris
On Thu, Dec 24, 2015 at 03:50:17PM +0000, 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 +0000, 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 > vblank there are a few more bit and pieces involved. > > > Thanks, hope you push it into mainstream. > > Patch sent. 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?
On Thu, Dec 24, 2015 at 08:28:25PM +0100, Lukas Hejtmanek wrote: > On Thu, Dec 24, 2015 at 03:50:17PM +0000, 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 +0000, 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 > > vblank there are a few more bit and pieces involved. > > > > > Thanks, hope you push it into mainstream. > > > > Patch sent. > > 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. -Chris
On Thu, Dec 24, 2015 at 07:37:18PM +0000, 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 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.
On Thu, Dec 24, 2015 at 08:42:01PM +0100, Lukas Hejtmanek wrote: > On Thu, Dec 24, 2015 at 07:37:18PM +0000, 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 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. 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. -Chris
On Thu, Dec 24, 2015 at 07:55:42PM +0000, 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.
On Thu, Dec 24, 2015 at 08:59:49PM +0100, Lukas Hejtmanek wrote: > On Thu, Dec 24, 2015 at 07:55:42PM +0000, 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. Keep going... Jump to about 3.19 -Chris
On Thu, Dec 24, 2015 at 08:05:33PM +0000, 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 +0000, 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. > > Keep going... Jump to about 3.19 tried 3.19.0-42 from ubuntu. lockup as well it just took more time..
On Thu, Dec 24, 2015 at 11:15:57PM +0100, Lukas Hejtmanek wrote: > On Thu, Dec 24, 2015 at 08:05:33PM +0000, 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 +0000, 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. > > > > Keep going... Jump to about 3.19 > > tried 3.19.0-42 from ubuntu. lockup as well it just took more time.. Hmm. What hardware? Baytrail? -Chris
On Thu, Dec 24, 2015 at 10:22:24PM +0000, 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)
On Thu, Dec 24, 2015 at 5:25 PM, Lukas Hejtmanek <xhejtman@ics.muni.cz> wrote: > On Thu, Dec 24, 2015 at 10:22:24PM +0000, 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 > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/intel-gfx 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.
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..
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?
diff --git a/va/x11/dri2_util.c b/va/x11/dri2_util.c index d076fb3..9ff5e95 100644 --- a/va/x11/dri2_util.c +++ b/va/x11/dri2_util.c @@ -95,8 +95,9 @@ dri2SwapBuffer(VADriverContextP ctx, struct dri_drawable *dri_drawable) if (dri2_drawable->has_backbuffer) { if (gsDRI2SwapAvailable) { CARD64 ret; - VA_DRI2SwapBuffers(ctx->native_dpy, dri_drawable->x_drawable, 0, 0, - 0, &ret); + VA_DRI2SwapBuffers(ctx->native_dpy, dri_drawable->x_drawable, + 0, 1, 0, + &ret); } else { xrect.x = 0; xrect.y = 0;