Arch Linux

Please confirm some information before closing:
- what is your graphic card?
- what is the mesa version?

What do I need to do? I'm on mesa intel drivers and it works just fine.

From the very short stacktrace it does indeed look like a mesa bug. I need you to rebuild blender on your machine please and test it. Also post details.

1. doesn't work on my two ati computers => graphic card version is not the problem
2. there is error message
Two passes with the same argument (-alloca-hoisting) attempted to be registered!

It's not related to mesa, because mesa doesn't dépends on llvm-3.3, except mesa-9.1.4-4, now fixed and replaced with mesa-9.1.4-5, so please answer to the previous question:
- what are your graphic cards?
- what is the mesa version?

blender doesn't compile. Here the error message:
In file included from /home/alex/prog/pkgbuilds/blender/src/blender-2.68.58183/source/blender/collada/AnimationImporter.cpp:50:
In file included from /home/alex/prog/pkgbuilds/blender/src/blender-2.68.58183/source/blender/collada/collada_utils.h:30:
In file included from /usr/include/opencollada/COLLADAFramework/COLLADAFWMeshPrimitive.h:18:
In file included from /usr/include/opencollada/COLLADAFramework/COLLADAFWEdge.h:16:
/usr/include/opencollada/COLLADABaseUtils/COLLADABUhash_map.h:67:18: fatal error:
'ext/hash_fun.h' file not found
#include <ext/hash_fun.h>
^
1 warning and 1 error generated.
make[2]: *** [source/blender/collada/CMakeFiles/bf_collada.dir/AnimationImporter.cpp.o] Fehler 1
make[1]: *** [source/blender/collada/CMakeFiles/bf_collada.dir/all] Fehler 2
make: *** [all] Fehler 2

I use mesa 9.1.4-5 and ati 4200 onboard and an ati apu (I don't know the version exactly, but it's a thinkpad x121e)

I use mesa 9.1.4-5 and ati 4200 onboard and an ati apu (I don't know the version exactly, but it's a thinkpad x121e)

sorry for the duplicate.
Building blender-svn works and the result is runnable.
Don't know if it is the recompiling or the other svn-version

Same error here on:

- ATI RadeonHD 4890
- mesa 9.1.4-5
- blender 8:2.68.58182-1
- llvm-amdgpu-lib-snapshot 20130403-3

And I think ATI drivers for some rendering modes (GL_SELECT) use software code path (llvm backend) and aren't hardware accelerated, no idea about other usages.

Please test the rebuild I just pushed.

Same error with blender 8:2.68.58224-1

have to confirm: the rebuild doesn't changed anything.
But blender-svn works flawless. (svn version 58228)

Hello,

same here. I use Arch Linux (linux 3.9.9-1) for x86_64 with Open Source driver xf86-video-nouveau (1.0.8-1) for nvidia GT 630. As UI I use Gnome Desktop (3.8.3-2).

[xyz@xyz ~]$ blender
Two passes with the same argument (-alloca-hoisting) attempted to be registered!
Writing: /tmp/blender.crash.txt
Speicherzugriffsfehler (Speicherabzug geschrieben)

blender.crash.txt:

# Blender 2.67 (sub 1), Revision: 58224

# backtrace
blender() [0xbca38b]
/usr/lib/libc.so.6(+0x35240) [0x7f994c579240]
/usr/lib/libLLVM-3.3.so(+0x52a300) [0x7f9942609300]
/usr/lib/libLLVM-3.3.so(_ZN4llvm1XE+0) [0x7f9943992980]

pacman -Qs blender:

local/blender 8:2.68.58224-1
A fully integrated 3D graphics creation suite

After installation there is a folder "2.67" under "/usr/share/blender/".

pacman -Qs mesa:

local/glu 9.0.0-2
Mesa OpenGL Utility library
local/lib32-glu 9.0.0-2
Mesa OpenGL utility library (32 bits)
local/lib32-mesa 9.1.4-1
an open-source implementation of the OpenGL specification (32-bit)
local/lib32-mesa-libgl 9.1.4-1
Mesa 3-D graphics library (32-bit)
local/lib32-nouveau-dri 9.1.4-1
Mesa drivers for Nouveau (32-bit)
local/mesa 9.1.4-5
an open-source implementation of the OpenGL specification
local/mesa-libgl 9.1.4-5
Mesa 3-D graphics library
local/nouveau-dri 9.1.4-5
Mesa drivers for Nouveau

The reason for this is the llvm version mismatch in arch currently. Some Mesa drivers are built with llvm 3.2 while osl is built with llvm 3.3. The best fix would be building the drivers with llvm 3.3 but I suppose it's not trivial.

Please test the new openshadinglanguage package and see whether blender still crashes for you.

no, I can start blender. Seems to fix the problem.

Good enough, thanks.