<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [radeonsi] Serious Sam 3 lockup during its start" href="https://bugs.freedesktop.org/show_bug.cgi?id=83416#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [radeonsi] Serious Sam 3 lockup during its start" href="https://bugs.freedesktop.org/show_bug.cgi?id=83416">bug 83416</a> from <a class="email" href="mailto:smoki00790@gmail.com" title="smoki <smoki00790@gmail.com>"> smoki</a> <pre>(In reply to <a href="show_bug.cgi?id=83416#c2">comment #2</a>) > I get no lockup either, but I do see the same GPUVM protection faults: > > radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0FF00819 > > The FF bits make me suspect bits 32-4x of the GPUVM address are getting > clobbered, maybe because of the LLVM backend generating invalid shader code. For me nothing new in dmesg, but there is something very interesting here happen. When radeonsi.so is striped this trace segfault for me, if not striped it pass fine no segfault, what that can be? Hmm...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>