Date: Sat, 27 Oct 2018 22:13:33 +0000 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) Message-ID: <bug-230298-7141-FSoRNZEkht@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230298-7141@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230298 --- Comment #17 from rkoberman@gmail.com --- Created attachment 198698 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=198698&action=edit 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. After some head scratching, I took a look at my logs and I suspect that I see a big 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 condition 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 seemed 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. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230298-7141-FSoRNZEkht>