From owner-freebsd-x11@freebsd.org Sat Oct 27 22:13:35 2018 Return-Path: Delivered-To: freebsd-x11@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 6B59410D5B91 for ; Sat, 27 Oct 2018 22:13:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 E5F1E7DD11 for ; Sat, 27 Oct 2018 22:13:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AAA6F10D5B90; Sat, 27 Oct 2018 22:13:34 +0000 (UTC) Delivered-To: x11@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 9969110D5B8F for ; Sat, 27 Oct 2018 22:13:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 352E27DD0C for ; Sat, 27 Oct 2018 22:13:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6CF0513E0F for ; Sat, 27 Oct 2018 22:13:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9RMDXVh080571 for ; Sat, 27 Oct 2018 22:13:33 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9RMDX2L080569 for x11@FreeBSD.org; Sat, 27 Oct 2018 22:13:33 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 230298] graphics/mesa-dri: update to 18.2.3 (VAAPI regression on Sandy Bridge) Date: Sat, 27 Oct 2018 22:13:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rkoberman@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2018 22:13:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230298 --- Comment #17 from rkoberman@gmail.com --- Created attachment 198698 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D198698&action= =3Dedit drm related error messages This was all a false positive. There is no issue with mesa-18.2.3 and VAAPI. There was a DRM or hardware or driver issue, but it is VERY fuzzy. I ran some tests on 18.1.9 and then re-installed 18.2.3. It ran almost identically to the old version. Low CPU. Smooth video. Moderate decline in glxgears FPS. Went back and forth a couple of time with no problems seen. A= fter some head scratching, I took a look at my logs and I suspect that I see a b= ig clue. (See attachment.) I can assure you that I was not doing anything at 4= :04 and nothing special was scheduled at that time. Looks like something hiccuped and left the GPU or the software in a conditi= on that acceleration with VAAPI did not work. Maybe most or all all graphics = was being handed in software, though that is really a guess. I am unable to find the dump referenced in the log. And, maybe these errors are not related to = the problem at all. These were all logged after my initial testing, which seeme= d to go well, and the problem I saw this week. If I should open a ticket for the issue logged, let me know and also let me know what, if anything, I should attach or try. I'll admit cluelessness. --=20 You are receiving this mail because: You are the assignee for the bug.=