mesa llvmpipe tests fail on Skylake

Bug #1553174 reported by Timo Aaltonen
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
llvm-toolchain-3.8 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

While migrating mesa to dh I noticed that gallium llvmpipe driver tests get enabled. They run fine on Debian which is still on 3.6, but the ubuntu branch fails to run the tests with 3.8. Building on Broadwell succeeds fine.

make[7]: Entering directory '/<<PKGBUILDDIR>>/build/src/gallium/drivers/llvmpipe'
../../../../../bin/test-driver: line 107: 8363 Illegal instruction (core dumped) "$@" > $log_file 2>&1
FAIL: lp_test_format
../../../../../bin/test-driver: line 107: 8394 Illegal instruction (core dumped) "$@" > $log_file 2>&1
FAIL: lp_test_arit
../../../../../bin/test-driver: line 107: 8401 Illegal instruction (core dumped) "$@" > $log_file 2>&1
FAIL: lp_test_blend
../../../../../bin/test-driver: line 107: 8408 Illegal instruction (core dumped) "$@" > $log_file 2>&1
FAIL: lp_test_conv
PASS: lp_test_printf

I haven't debugged it in detail, so no idea what causes this.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

(gdb) run
Starting program: /home/tjaalton/src/pkg-xorg/lib/mesa.git/build/src/gallium/drivers/llvmpipe/lp_test_format
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Testing PIPE_FORMAT_B8G8R8A8_UNORM (float) ...

Program received signal SIGILL, Illegal instruction.
0x00007ffff7ff5004 in ?? ()
(gdb) bt
#0 0x00007ffff7ff5004 in ?? ()
#1 0x0000000000000000 in ?? ()
(gdb) bt full
#0 0x00007ffff7ff5004 in ?? ()
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.

huh

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in llvm-toolchain-3.8 (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.