Ubuntu
xorg package

Can't use hardware decoding (vaapi) with fglrx: Assertion `buffers' failed

Bug #1525721 reported by Ales on 2015-12-13

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xorg (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

mpv --hwdec=auto movie.mkv gives this:

  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_38
  libva info: va_openDriver() returns 0
  Using hardware decoding (vaapi).
  VO: [opengl] 1904x1036 vaapi
  mpv: dri2_util.c:132: dri2GetRenderingBuffer: Assertion `buffers' failed.
  (SIGABRT) (core dumped)

I have hybrid graphics Intel Haswell and AMD Radeon R5 M255.
I have installed fglrx-updates and in AMD Catalyst control center switched to dedicated GPU.
I seems to me that this setting is ignored and hardware decoding is tried on Intel instead.

fglrxinfo:
  display: :0 screen: 0
  OpenGL vendor string: Advanced Micro Devices, Inc.
  OpenGL renderer string: AMD Radeon R5 M255
  OpenGL version string: 4.5.13399 Compatibility Profile Context 15.201.1151

amdconfig --pxl :
PowerXpress: Discrete GPU is active (High-Performance mode).

lspci | grep VGA:
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)

vainfo:
libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64- libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.38 (libva 1.6.0)
vainfo: Driver version: Intel i965 driver for Intel(R) vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple VAProfileMPEG2Simple VAProfileMPEG2Main VAProfileMPEG2Main VAProfileH264ConstrainedH264ConstrainedH264Main VAProfileH264Main VAProfileH264High VAProfileH264High VAProfileH264MultiviewHiH264MultiviewHiH264StereoHigh VAProfileH264StereoHigh VAProfileVC1Simple VAProfileVC1Main VAProfileVC1Advanced VAProfileNone VAProfileJPEGBaseline VAProfileH264MultiviewHiH264MultiviewHiH264StereoHigh VAProfileH264StereoHigh />linux-gnu/dri/i965_drv_video.so
Haswell Mobile - 1.6.0
: VAEntrypointVLD
: VAEntrypointEncSlice
: VAEntrypointVLD
: VAEntrypointEncSlice
/>Baseline: VAEntrypointVLD
/>Baseline: VAEntrypointEncSlice
: VAEntrypointVLD
: VAEntrypointEncSlice
: VAEntrypointVLD
: VAEntrypointEncSlice
/>gh : VAEntrypointVLD
/>gh : VAEntrypointEncSlice
: VAEntrypointVLD
: VAEntrypointEncSlice
: VAEntrypointVLD
: VAEntrypointVLD
: VAEntrypointVLD
: VAEntrypointVideoProc
: VAEntrypointVLD
/>gh : VAEntrypointVLD
/>gh : VAEntrypointEncSlice
: VAEntrypointVLD
: VAEntrypointEncSlice

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sun Dec 13 23:04:06 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: kubuntu
DkmsStatus: fglrx-updates-core, 15.201, 4.2.0-19-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:2248]
Subsystem: Hewlett-Packard Company Device [103c:224a]
InstallationDate: Installed on 2015-10-23 (51 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Hewlett-Packard HP ProBook 450 G2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=c9e0c6ee-c8a4-4d1a-a46e-a3b79c38f774 ro
SourcePackage: xorg
UdevLog: Error: [Errno 2] Adresář nebo soubor neexistuje: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/20/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M74 Ver. 01.05
dmi.board.name: 2248
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 67.22
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrM74Ver.01.05:bd09/20/2014:svnHewlett-Packard:pnHPProBook450G2:pvrA3008CD10003:rvnHewlett-Packard:rn2248:rvrKBCVersion67.22:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 450 G2
dmi.product.version: A3008CD10003
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sun Dec 13 00:32:49 2015
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
Screen 1 deleted because of no matching config section.
AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
fglrx(0): XMM: Fail to unregister UVDFWVIRQ! (EE) fglrx(0):
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1
xserver.video_driver: fglrx

Tags:

Revision history for this message

Ales (w-ales) wrote on 2015-12-13:

BootLog.txt Edit (11.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (75.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.5 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (205.7 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (17.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (12.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (544 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.9 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (325 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.4 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (171.4 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (749 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (92.3 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (118.4 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.9 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (13.8 KiB, text/plain; charset="utf-8")
xserver.devices.txt Edit (706 bytes, text/plain; charset="utf-8")
xserver.outputs.txt Edit (1.0 KiB, text/plain; charset="utf-8")

penalvch (penalvch) on 2016-01-09

tags:	added: bios-outdated-1.16
Changed in xorg (Ubuntu):
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

Ales (w-ales) wrote on 2016-01-11:

Thank you for your replay. After BIOS update:

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date says:

M74 Ver. 01.16
11/26/2015

Unfortunately no improvement, it doesn't work anyway. The only change is, that mpv doesn't give "SIGABRT" but "Aborted".

Whole message:

libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_38
libva info: va_openDriver() returns 0
AO: [pulse] 48000Hz 5.1(side) 6ch float
Using hardware decoding (vaapi).
VO: [opengl] 1920x796 vaapi
mpv: dri2_util.c:132: dri2GetRenderingBuffer: Assertion `buffers' failed.
Aborted (core dumped)

Changed in xorg (Ubuntu):
status:	Incomplete → New

Revision history for this message

penalvch (penalvch) wrote on 2016-01-11:

Ales, to clarify, after the core dump, is there a crash file in /var/crash?

tags:	added: latest-bios-1.16 removed: bios-outdated-1.16
Changed in xorg (Ubuntu):
importance:	Low → Medium
status:	New → Incomplete

Revision history for this message

Ales (w-ales) wrote on 2016-01-11:

Yes, it is. Looks like this:

:/var/crash$ l -l

-rw-r----- 1 ales whoopsie 4134330 Jan 11 10:20 _usr_bin_mpv.1000.crash
-rw-rw-r-- 1 ales whoopsie 0 Jan 11 10:20 _usr_bin_mpv.1000.upload
-rw------- 1 whoopsie whoopsie 0 Jan 11 10:20 _usr_bin_mpv.1000.uploaded

Revision history for this message

penalvch (penalvch) wrote on 2016-01-11:

Ales, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing.

Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

However, this report is being closed since the process outlined above will deal with this issue more efficiently. Also, please do not attach your crash report manually to this report and reopen it. Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in xorg (Ubuntu):
importance:	Medium → Undecided
status:	Incomplete → Invalid

Revision history for this message

Ales (w-ales) wrote on 2016-01-11:

Done. Thank you for your help.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntuxorg package

Can't use hardware decoding (vaapi) with fglrx: Assertion `buffers' failed

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
xorg package