Hi, I am unsure which bug report is correct for this as there is similar
one #898033 and #954849 but I could confirm the problem is back since
approximately May 2020 up to today:
It could be basically any program using opencl, I've picked the clinfo as
an example:
$ clinfo
: CommandLine Error: Opt
Control: reopen -1
Control: reassign -1 libllvm6.0
Control: found -1 1:6.0.1-9.2
Control: affects -1 src:pocl mesa-opencl-icd
Control: retitle -1 crash if multiple ICDs dynamically linked to LLVM
X-Debbugs-CC: pkg-opencl-de...@alioth-lists.debian.net
This bug still exists in LLVM 6.0 (and given t
Control: tags -1 - patch
Control: tags -1 upstream
Control: reassign -1 libllvm3.9
The real bug here is that libllvm is a shared library with global state,
and that loading it twice from the same application (the process of
checking which OpenCL driver works on the available hardware involves
Control: retitle -1 beignet+mesa-opencl-icd crash if installed together and
linked dynamically against LLVM
Control: severity -1 important
On 2017-02-18 23:11, Rebecca N. Palmer wrote:
> Statically linking to LLVM (see attached) fixes this bug, but I'm not
> sure yet whether we want to do that.
On Mon, Feb 20, 2017 at 09:47:50AM +0100, Andreas Beckmann wrote:
> Dear security team,
>
> we plan to switch the OpenCL ICD beignet (and perhaps other ICDs if
> neccessary) to link statically instead of dynamically against LLVM, to
> work around #852746.
>
> Currently OpenCL applications crash i
Dear security team,
we plan to switch the OpenCL ICD beignet (and perhaps other ICDs if
neccessary) to link statically instead of dynamically against LLVM, to
work around #852746.
Currently OpenCL applications crash if both mesa-opencl-icd and
beignet-opencl-icd are installed - both link dynamica
All OpenCL ICDs with shared LLVM are useless if they can't be used
in real programs, so my opinion for whats its worth is that they link
statically with LLVM until the issue is resolved in another way allowing
shared LLVM (probably Stretch+1 material).
Of course this is just my opinion
Control: tags -1 patch
Statically linking to LLVM (see attached) fixes this bug, but I'm not
sure yet whether we want to do that.
diff --git a/debian/control b/debian/control
index cb2623c..a04fa1e 100644
--- a/debian/control
+++ b/debian/control
@@ -26,7 +26,10 @@ Build-Depends:
libxext-dev,
Control: forwarded -1 https://bugs.llvm.org/show_bug.cgi?id=30587
(They actually found it independently, but it's clearly the same bug.)
They don't have a fix for this one; they do have fixes for
https://bugs.llvm.org/show_bug.cgi?id=31571 /
https://bugs.llvm.org/show_bug.cgi?id=28127 (similar
This bug goes away on rebuilding beignet with LLVM 3.8 (but that isn't a
good solution as it can trigger #848368, and also disables some of
beignet's functionality).
Debug backtraces show mesa-opencl-icd being loaded first, and the crash
happening when beignet-opencl-icd is loaded, suggesting
Control: retitle -1 beignet+mesa-opencl-icd crash if installed together
The lack of hardware isn't the trigger - having beignet-opencl-icd and
mesa-opencl-icd installed at the same time is. (beignet+pocl or
mesa+pocl is OK.)
Looks like some kind of "seeing the other ICD's copy of libllvm ins
Package: beignet-opencl-icd
Version: 1.2.1-1+b1
Severity: important
Hello.
Every application that uses OpenCL crashes in this way:
$ clinfo
X server found. dri2 connection failed!
/dev/dri/card0 not authenticated
: CommandLine Error: Option 'enable-value-profiling' registered more than once!
LLVM
12 matches
Mail list logo
