https://bugs.freedesktop.org/show_bug.cgi?id=76223
Vladimir Ysikov changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #25 from Michel Dänzer ---
(In reply to Vladimir Ysikov from comment #24)
> And little bonus, Xorg crash after star t firefox.
See bug 89034.
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #24 from Vladimir Ysikov ---
Created attachment 113293
--> https://bugs.freedesktop.org/attachment.cgi?id=113293&action=edit
Xorg.0.log
I forgot about lib32-llvm. llvm-svn > lib32-llvm-svn > mesa.
drm-next, llvm-svn, mesa-git
#0
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #23 from Michel Dänzer ---
> (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/swrast_dri.so failed
> (libLLVM-3.5.so: cannot open shared object file: No such file or directory)
Looks like the dynamic linker can't find libLLVM-
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #22 from Vladimir Ysikov ---
Created attachment 113266
--> https://bugs.freedesktop.org/attachment.cgi?id=113266&action=edit
Xorg.0.log
It happen after update llvm, not mesa.
--
You are receiving this mail because:
You are the as
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #21 from Michel Dänzer ---
(In reply to Vladimir Ysikov from comment #20)
> I rebuild llvm-svn, mesa-git with debug symbols and get this:
>
> behem0th at ArchLinux ~ $ glxinfo
> name of display: :0
> Error: couldn't find RGB GLX v
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #20 from Vladimir Ysikov ---
>Is the crash the same? Can you get a backtrace?
I rebuild llvm-svn, mesa-git with debug symbols and get this:
behem0th at ArchLinux ~ $ glxinfo
name of display: :0
Error: couldn't find RGB GLX visual
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #19 from Tom Stellard ---
(In reply to Vladimir Ysikov from comment #18)
> I try latest llvm-svn+mesa-git+drm-next and luxmark still crash.
Is the crash the same? Can you get a backtrace?
--
You are receiving this mail because:
Yo
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #18 from Vladimir Ysikov ---
I try latest llvm-svn+mesa-git+drm-next and luxmark still crash.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was s
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #17 from Arek RuÅniak ---
On CapeVerde 10.4.3 + llvm 3.5.1 gives somethings like this:
LLVM ERROR: Cannot select: 0x7f73c55484d0: i64 = and 0x7f73c55487e8,
0x7f73c55406d8 [ORD=148] [ID=247]
0x7f73c55487e8: i64 = any_extend 0x7f73c
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #16 from Vladimir Ysikov ---
mesa 10.5-git, llvm 3.5.1, linux drm-next
behem0th at ArchLinux ~/AUR/KDE $ luxmark
LLVM ERROR: Cannot select: 0x7f45c9c4a518: i64 = and 0x7f45c9c4c290,
0x7f45c9c41ea8 [ORD=127] [ID=214]
0x7f45c9c4c290
https://bugs.freedesktop.org/show_bug.cgi?id=76223
Vladimir Ysikov changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=76223
Laurent carlier changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #13 from Aaron Watry ---
Created attachment 102163
--> https://bugs.freedesktop.org/attachment.cgi?id=102163&action=edit
Possible fix for luxmark segfault
The luxrays kernels used an __attribute__(work_group_size_hint(64,1,1)) on
s
https://bugs.freedesktop.org/show_bug.cgi?id=76223
Aaron Watry changed:
What|Removed |Added
Attachment #101243|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #11 from joshua.r.marshall.1991 at gmail.com ---
Exact same back trace with and without luxrays. This also working off of this
morning's mesa-git build.
sorry I can't be of more help.
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #10 from joshua.r.marshall.1991 at gmail.com ---
this was obtained by "gdb luxmark" and then entering "run" at the prompt.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part ---
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #9 from joshua.r.marshall.1991 at gmail.com ---
Currently, I am using the luxmark packaged in arch linux's repo's. I'm not
seeing exactly what you are, so I'll include a BT:
Program received signal SIGSEGV, Segmentation fault.
0x
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #8 from Aaron Watry ---
Created attachment 101243
--> https://bugs.freedesktop.org/attachment.cgi?id=101243&action=edit
Test Case for SLG InitFrameBuffer Kernel
I've tracked down where slg4 is segfaulting on my machine currently. T
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #7 from Aaron Watry ---
I've sent a whole bunch of patches to the libclc dev list implementing quite a
few builtin CL functions that were missing. luxrays/slg4 is now able to
compile the CL kernels, but it now gets an LLVM Error at a
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #6 from Aaron Watry ---
If you're building from luxrays source, can you also try disabling image
support and seeing if the error changes?
For a source build, go to scenes/luxball/luxball.cfg, and add:
accelerator.imagestorage.enable
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #5 from Aaron Watry ---
Created attachment 100762
--> https://bugs.freedesktop.org/attachment.cgi?id=100762&action=edit
slg4 log with CEDAR
What command are you running this with? Is it just running bin/slg4 as built
from the luxr
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #4 from joshua.r.marshall.1991 at gmail.com ---
I have the exact same issue. Unfortunately, debug information is not easy to
do, especially without risking my whole desktop environment.
--
You are receiving this mail because:
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #3 from Vladimir Ysikov ---
Created attachment 96222
--> https://bugs.freedesktop.org/attachment.cgi?id=96222&action=edit
bt full
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part -
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #2 from Vladimir Ysikov ---
Created attachment 96194
--> https://bugs.freedesktop.org/attachment.cgi?id=96194&action=edit
New trace
I rebuild mesa, llvm, clang, libclc, luxmark with debug compilation flags.
https://wiki.archlinux.
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #1 from Tom Stellard ---
This back trace doesn't include any symbols from LLVM or Mesa. Were there any
errors printed to the console? Are there debugging flags or environment
variables you can enable to get more information?
--
Yo
26 matches
Mail list logo