From owner-freebsd-multimedia@freebsd.org Fri Oct 5 20:19:28 2018 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3DDAA10B57BF for ; Fri, 5 Oct 2018 20:19:28 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id CE18C8F192 for ; Fri, 5 Oct 2018 20:19:27 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9281910B57BD; Fri, 5 Oct 2018 20:19:27 +0000 (UTC) Delivered-To: multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5735C10B57BC for ; Fri, 5 Oct 2018 20:19:27 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E39CF8F18A for ; Fri, 5 Oct 2018 20:19:26 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ot1-x335.google.com with SMTP id l1so598065otj.5 for ; Fri, 05 Oct 2018 13:19:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xKieFUz2ZJ0iQmp/NIGbCwekCDIdsBFje5TsqxVVXJs=; b=Rp3j2Fbj6GmFugprkTnv5VW6e7QcTammGoowgULHY5i2B7MXoaXJlqCs9lh0z/pReA DyLHZAZLBgLM2Nq/7PjTTJgBobXpiVAxcvRROhsm8YrVc1x87GXzgSXQMBCYcNtFWoGV DdA07o8x29iNmVhK4Cs0bfcM9RAeR636LCov5md5y9LGFLErMVGIyV9j0v4qUEXgNG4l 5nymcJF7iZHEvd/TLrbQwsC3GElZ/EhZpYl9m9IIkBUd99dxYbN/lkmhydUp+yUR6SKx 3ZeJn7ZwO6KIQy+k8ezXtMeREPnEy3basRlqqVduGGBc/jc8c0z4WELcdB+mAngqHLPt s/3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xKieFUz2ZJ0iQmp/NIGbCwekCDIdsBFje5TsqxVVXJs=; b=WIuisN4LVmq3GXMxoCyANczJo6xNzdfoFHW2WVCqY1Va3aME+iX+TZZSApggd/bml6 5nD9pqUN6BCiX7sGnEr1dp6VF38+Fls7acMxRNhwUa8ZqRuHb7LPVeXfI1Y8/bp82eQ6 pdaMdrm4BvH56FQzOYwliWx9MC4FjfHDTAQVH1TWtlG+LvNfr71/6wkvSjJwF0jQ+UlA Et2QL+dEUbFjCQbIW7SO4de85zZL3FVouieHK/gJoSv+LhdMgl/uRrPXfp24TzaQTXQ4 Nsb6zGWGgvIlxwbcYLSxF65w7V47vclwRq0FHiBiVvVuq2gxUay5zaOlCb7flEsfEFqr IiAw== X-Gm-Message-State: ABuFfoiGjVVPo54uia6fREvJ348fAnimrOeyd5cm98jQHiCI99elWOOq mA/FWovSPfg+mS9fWicHns80dthFF7d5MsyN6Ov8A6bW X-Google-Smtp-Source: ACcGV60x8ZN4X6s/BOYsq/E4YMsJxbFGfDOw63TT9RytZDtXauh3WQskytjO6+J0yFynPVYRq9hH/B3ilDnfznUo3r4= X-Received: by 2002:a9d:5131:: with SMTP id c46mr7884978oth.302.1538770765678; Fri, 05 Oct 2018 13:19:25 -0700 (PDT) MIME-Version: 1.0 From: Kevin Oberman Date: Fri, 5 Oct 2018 13:19:08 -0700 Message-ID: Subject: VAAPI not working with latest updates To: multimedia@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2018 20:19:28 -0000 I'll start by admitting that I am not sure where to look about this, bu after the last week's massive updates, all of my video players are failing. I have tried mplayer, totem, mpv, xine and vlc. None work. vlc give the most detailed error message (more than one line): libva info: VA-API version 1.2.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/local/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 libva info: va_openDriver() returns 0 i965: Failed to submit batchbuffer: Input/output error QObject::~QObject: Timers cannot be stopped from another thread All others just show the i965 line. I am assuming that VAAPI is the problem as I can use avidemux3_qt4 without any problem and, as far as I can tell, it does not use VAAPI. Running 11.2-stable r338990 and drm-stable-kmod. All ports are current as of last night. GPU is Sandy Bridge. I have not tried to play a video since 28-Sept. and a LOT of ports have been touched since then, so VAPI may not be at issue, it just looks very suspicious. I have tried rolling back libva and libva-intel-driver, to 2.2.0 but that did not help. Any suggestions on what I might look at? I'm not happy about opening a PR with so little to go by. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683