From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99994] Unreal Tournament 2016 segfaults with sisched
Date: Mon, 27 Feb 2017 22:25:52 +0000 [thread overview]
Message-ID: <bug-99994-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4832 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99994
Bug ID: 99994
Summary: Unreal Tournament 2016 segfaults with sisched
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: ernstp@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
The free to play Unreal Tournament under development segfaults with
R600_DEBUG=sisched.
Fully playable, with rendering issues, without it.
It segfaults very early, before the first graphics.
FIJI Fury card.
LLVM: 5.0~svn295460-0~y~padoka0
Mesa: 17.1~git170226151200.5b5ffb7~y~padoka0
(gdb) bt
#0 llvm::SIInstrInfo::isLowLatencyInstruction(llvm::MachineInstr const&) const
() at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/include/llvm/CodeGen/MachineInstr.h:273
warning: (Internal error: pc 0x7fffdc4858cf in read in psymtab, but not in
symtab.)
warning: (Internal error: pc 0x7fffdc4858cf in read in psymtab, but not in
symtab.)
#1 0x00007fffdc4858d0 in llvm::SIScheduleDAGMI::moveLowLatencies() () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/Target/AMDGPU/SIMachineScheduler.cpp:1727
warning: (Internal error: pc 0x7fffdc48fc85 in read in psymtab, but not in
symtab.)
warning: (Internal error: pc 0x7fffdc48fc85 in read in psymtab, but not in
symtab.)
#2 0x00007fffdc48fc86 in llvm::SIScheduleDAGMI::schedule() () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/Target/AMDGPU/SIMachineScheduler.cpp:1871
#3 0x00007fffdb5f50ef in (anonymous
namespace)::MachineSchedulerBase::scheduleRegions(llvm::ScheduleDAGInstrs&,
bool) () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/CodeGen/MachineScheduler.cpp:480
#4 0x00007fffdb5fe789 in (anonymous
namespace)::MachineScheduler::runOnMachineFunction(llvm::MachineFunction&) ()
at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/CodeGen/MachineScheduler.cpp:344
#5 0x00007fffdb5a86a1 in
llvm::MachineFunctionPass::runOnFunction(llvm::Function&) () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/CodeGen/MachineFunctionPass.cpp:62
#6 0x00007fffdb430b22 in llvm::FPPassManager::runOnFunction(llvm::Function&)
() at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/IR/LegacyPassManager.cpp:1513
#7 0x00007fffdb430bc3 in llvm::FPPassManager::runOnModule(llvm::Module&) () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/IR/LegacyPassManager.cpp:1534
#8 0x00007fffdb431567 in llvm::legacy::PassManagerImpl::run(llvm::Module&) ()
at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/IR/LegacyPassManager.cpp:1590
#9 0x00007fffdc2b79c8 in LLVMTargetMachineEmit(LLVMOpaqueTargetMachine*,
LLVMOpaqueModule*, llvm::raw_pwrite_stream&, LLVMCodeGenFileType, char**) () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/Target/TargetMachineC.cpp:204
#10 0x00007fffdc2b7bc9 in LLVMTargetMachineEmitToMemoryBuffer () at
/build/llvm-toolchain-snapshot-jHu56_/llvm-toolchain-snapshot-5.0~svn295460/lib/Target/TargetMachineC.cpp:228
#11 0x00007fffdee3d8d5 in si_llvm_compile (M=0x7fffbc013db0,
binary=0x7fffbc009460, tm=0x75e140, debug=0x0) at
../../../../../../src/gallium/drivers/radeonsi/si_shader_tgsi_setup.c:224
#12 0x00007fffdee38528 in si_compile_llvm (sscreen=<optimized out>,
binary=0x7fffbc009460, conf=0x7fffbc0094c0, tm=0x75e140, mod=0x7fffbc013db0,
debug=0x0, processor=1, name=0x7fffdf001231 "TGSI shader")
at ../../../../../../src/gallium/drivers/radeonsi/si_shader.c:6159
#13 0x00007fffdee39389 in si_compile_tgsi_shader (sscreen=0x757480,
tm=0x75e140, shader=0x7fffbc009330, is_monolithic=<optimized out>, debug=0x0)
at ../../../../../../src/gallium/drivers/radeonsi/si_shader.c:7366
#14 0x00007fffdee4d39c in si_init_shader_selector_async (job=0x7fffa8b84d10,
thread_index=1) at
../../../../../../src/gallium/drivers/radeonsi/si_state_shaders.c:1416
#15 0x00007fffdeb77754 in util_queue_thread_func (input=<optimized out>) at
../../../../../src/gallium/auxiliary/util/u_queue.c:175
#16 0x00007fffdeb773d8 in impl_thrd_routine (p=<optimized out>) at
../../../../../include/c11/threads_posix.h:87
#17 0x00007ffff7bc16ca in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#18 0x00007ffff0f240af in clone () from /lib/x86_64-linux-gnu/libc.so.6
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6268 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-02-27 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 22:25 bugzilla-daemon [this message]
2017-02-27 22:28 ` [Bug 99994] Unreal Tournament 2016 segfaults with sisched bugzilla-daemon
2018-04-11 4:20 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99994-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.