Description of problem: I simply run clinfo on a system that has beignet.x86_64 installed as the provider. Version-Release number of selected component: clinfo-0.1-0.2.git20131001.7f44937.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: clinfo crash_function: drm_intel_bufmgr_gem_enable_reuse executable: /usr/bin/clinfo kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 drm_intel_bufmgr_gem_enable_reuse at intel_bufmgr_gem.c:2627 #1 intel_driver_memman_init at /usr/src/debug/beignet-48f8e5b/src/intel/intel_driver.c:138 #2 intel_driver_init at /usr/src/debug/beignet-48f8e5b/src/intel/intel_driver.c:152 #3 intel_driver_init_master at /usr/src/debug/beignet-48f8e5b/src/intel/intel_driver.c:303 #4 intel_driver_open at /usr/src/debug/beignet-48f8e5b/src/intel/intel_driver.c:211 #5 intel_get_device_id at /usr/src/debug/beignet-48f8e5b/src/intel/intel_driver.c:364 #6 cl_get_gt_device at /usr/src/debug/beignet-48f8e5b/src/cl_device_id.c:77 #7 cl_get_device_ids at /usr/src/debug/beignet-48f8e5b/src/cl_device_id.c:135 #8 clGetDeviceIDs at ocl_icd_loader_gen.c:51 #9 printPlatformInfo at src/clinfo.c:88
Created attachment 887543 [details] File: backtrace
Created attachment 887544 [details] File: cgroup
Created attachment 887545 [details] File: core_backtrace
Created attachment 887546 [details] File: dso_list
Created attachment 887547 [details] File: environ
Created attachment 887548 [details] File: exploitable
Created attachment 887549 [details] File: limits
Created attachment 887550 [details] File: maps
Created attachment 887551 [details] File: open_fds
Created attachment 887552 [details] File: proc_pid_status
Created attachment 887553 [details] File: var_log_messages
The following was the output of the program when it crashed in case its useful: # clinfo Number of platforms 1 Platform Name Experiment Intel Gen OCL Driver Platform Vendor Intel Platform Version OpenCL 1.1 beignet 0.3 Platform Profile FULL_PROFILE Platform Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_icd X server found. dri2 connection failed! Trying to open directly... DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 Segmentation fault (core dumped)
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.