Bug 75959 - [abrt] libva-utils: object_heap_destroy(): vainfo killed by SIGFPE
Summary: [abrt] libva-utils: object_heap_destroy(): vainfo killed by SIGFPE
Status: NEW
Alias: None
Product: libva
Classification: Unclassified
Component: vdpau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Gwenole Beauchesne
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-09 21:50 UTC by Arcadiy Ivanov
Modified: 2018-10-31 05:01 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
backtrace (11.68 KB, text/plain)
2014-03-09 21:53 UTC, Arcadiy Ivanov
Details
core_backtrace (3.11 KB, text/plain)
2014-03-09 21:55 UTC, Arcadiy Ivanov
Details
sigfpe-crash.patch (742 bytes, patch)
2018-10-31 05:01 UTC, Daniel Drake
Details | Splinter Review

Description Arcadiy Ivanov 2014-03-09 21:50:40 UTC
Description of problem:
$ export LIBVA_DRIVER_NAME=vdpau
$ export VDPAU_DRIVER=radeonsi
$ vainfo
libva info: VA-API version 0.34.0
libva info: va_getDriverName() returns 0
libva info: User requested driver 'vdpau'
libva info: Trying to open /usr/lib64/dri/vdpau_drv_video.so
libva info: Found init function __vaDriverInit_0_34
do_winsys_init: DRM version is 1.6.0 but this driver is only compatible with 2.3.x (kernel 2.6.34) or later.
Floating point exception (core dumped)

00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])
        Subsystem: Dell Device 05cc
        Flags: bus master, fast devsel, latency 0, IRQ 45
        Memory at f5800000 (64-bit, non-prefetchable) [size=4M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f000 [size=64]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: i915

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M] (prog-if 00 [VGA controller])
        Subsystem: Dell Device 05cc
        Flags: bus master, fast devsel, latency 0, IRQ 46
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Memory at f7e00000 (64-bit, non-prefetchable) [size=256K]
        I/O ports at e000 [size=256]
        Expansion ROM at f7e40000 [disabled] [size=128K]
        Capabilities: [48] Vendor Specific Information: Len=08 <?>
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Capabilities: [150] Advanced Error Reporting
        Capabilities: [270] #19
        Kernel driver in use: radeon


Version-Release number of selected component:
libva-utils-1.2.1-2.fc20

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        vainfo
crash_function: object_heap_destroy
executable:     /usr/bin/vainfo
kernel:         3.13.5-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 object_heap_destroy at object_heap.c:275
 #1 destroy_heap at vdpau_driver.c:138
 #3 vdpau_common_Terminate at vdpau_driver.c:159
 #4 vdpau_Terminate_Current at vdpau_driver_template.h:537
 #5 vdpau_Initialize_Current at vdpau_driver_template.h:563
 #6 __vaDriverInit_0_34 at vdpau_driver.c:317
 #7 va_openDriver at va.c:292
 #8 vaInitialize at va.c:475
Comment 1 Arcadiy Ivanov 2014-03-09 21:53:49 UTC
Created attachment 95472 [details]
backtrace
Comment 2 Arcadiy Ivanov 2014-03-09 21:55:27 UTC
Created attachment 95473 [details]
core_backtrace
Comment 3 code 2016-01-03 01:17:56 UTC
I am observing this on Fedora 23 with an NVIDIA Corporation G84 [GeForce 8600 GT] card using the open-source (nouveau) driver. When the mesa-vdpau-drivers package is not installed (as it is not by default on that distribution), running vainfo gives me this output:

libva info: VA-API version 0.38.1
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so
libva info: Found init function __vaDriverInit_0_38
Failed to open VDPAU backend libvdpau_nouveau.so: cannot open shared object file: No such file or directory
Floating point exception (core dumped)

The backtrace matches that reported here. Installing the mesa-vdpau-drivers package solves the problem:

libva info: VA-API version 0.38.1
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so
libva info: Found init function __vaDriverInit_0_38
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.38 (libva 1.6.2)
vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 0.7.4
vainfo: Supported profile and entrypoints

However, this is still a pretty serious bug, because the mesa-vdpau-drivers are not installed by default, the workaround of installing that package is not obvious at first, and the consequences are system-wide: multiple applications, including tracker, Totem, and Shotwell, crash on startup or when processing most or all video files. A missing driver should be handled gracefully.

https://bugzilla.redhat.com/show_bug.cgi?id=1286365
Comment 4 Daniel Drake 2018-10-31 05:01:54 UTC
Created attachment 142295 [details] [review]
sigfpe-crash.patch

Here is the patch shipped by Debian to solve this issue.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.