[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-11-18 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 Laurent carlier changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-11-18 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #19 from Laurent carlier --- Fixed with current mesa trunk, so closing -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL:

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-04 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #18 from Laurent carlier --- (In reply to comment #17) > Does this Mesa patch help? > > https://bugs.freedesktop.org/attachment.cgi?id=105755 No, it doesn't help -- You are receiving this mail because: You are the assignee for

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-04 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #17 from Grigori Goronzy --- Does this Mesa patch help? https://bugs.freedesktop.org/attachment.cgi?id=105755 -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-04 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 Laurent carlier changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-04 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 Laurent carlier changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-04 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #14 from Laurent carlier --- (In reply to comment #12) > Created attachment 105709 [details] [review] > Fix suggested by Vadim > > Can you try this patch? It doesn't fix the lockup for me. I've tested mesa-git with llvm 3.4.3 both

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-04 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #13 from Michel D?nzer --- (In reply to comment #12) > Can you try this patch? The patch fixes the GPUVM faults for me while replaying the apitrace. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #12 from Tom Stellard --- Created attachment 105709 --> https://bugs.freedesktop.org/attachment.cgi?id=105709=edit Fix suggested by Vadim Can you try this patch? -- You are receiving this mail because: You are the assignee for

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #11 from Vadim Girlin --- (In reply to comment #2) > I get no lockup either, but I do see the same GPUVM protection faults: > > radeon :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0FF00819 > > The FF bits make me suspect

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #10 from Laurent carlier --- Just tried with mesa-10.2.6/llvm-3.4.2 and the trace works fine except the following from LLVM: LLVM ERROR: ran out of registers during register allocation Here are the flags used:

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #9 from smoki --- Try also some stable mesas if you can 10.2 or 10.3, i have very strange issues with 32bit mesa and apps, particulary build system in current git seems very broken for me. Make install, SSE41 macro compile needs

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #8 from smoki --- @Laurent carlier Is this new issue or regressions maybe? Don't have SSAM3 game, but i remember from earlier versions that Serios Sam have bunch of different settings, maybe you can try some different settings

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #7 from smoki --- Created attachment 105676 --> https://bugs.freedesktop.org/attachment.cgi?id=105676=edit segfault (In reply to comment #5) > For me nothing new in dmesg, but there is something very interesting here > happen.

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #6 from Laurent carlier --- Just to note that this trace is produced with apitrace 5.0 and with the following commandline: GALLIUM_HUD=num-bytes-moved apitrace32 trace %command% -- You are receiving this mail because: You are the

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #5 from smoki --- (In reply to comment #2) > I get no lockup either, but I do see the same GPUVM protection faults: > > radeon :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0FF00819 > > The FF bits make me suspect bits

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #4 from Laurent carlier --- Link to the trace in google drive: https://drive.google.com/file/d/0B1WCo3k21FK3dTZmaFFmU2wwQzQ/edit?usp=sharing -- You are receiving this mail because: You are the assignee for the bug. --

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #3 from Laurent carlier --- Created attachment 105674 --> https://bugs.freedesktop.org/attachment.cgi?id=105674=edit ouput of 'R600_DEBUG=ps,vs glretrace Sam3.trace' LLVM is 3.6svn r216889 -- You are receiving this mail because:

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #2 from Michel D?nzer --- I get no lockup either, but I do see the same GPUVM protection faults: radeon :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0FF00819 The FF bits make me suspect bits 32-4x of the GPUVM address are

[Bug 83416] [radeonsi] Serious Sam 3 lockup during its start

2014-09-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=83416 --- Comment #1 from smoki --- Can not reproduce it on Kabini, with same git version 021e84f. That with mesa builded against current llvm-3.6 svn just pass fine, and when i build mesa against 3.5 this this apitrace just segfault... in both