https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #86 from Shmerl ---
(In reply to Dmitry from comment #85)
> This problem is still there on the new Mesa 18.3.1. On AMDLK there is no
> such problem, but I would not like to use it.
This bug was about radeonsi, not about Vulkan drive
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #85 from Dmitry ---
This problem is still there on the new Mesa 18.3.1. On AMDLK there is no such
problem, but I would not like to use it.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=101731
Christian König changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #84 from Christian
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #83 from Samuel Pitoiset ---
I do agree with Jozef, it's really a different issue that the one initially
filled here. Thanks again for fixing this!
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=101731
mirh changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #81 from Józef Kucia ---
(In reply to mirh from comment #80)
> I also agree with Fabian.
> Application going crazy with its own business is totally not a "problem of
> the driver"..
> But compromising system stability definitively
https://bugs.freedesktop.org/show_bug.cgi?id=101731
mirh changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|NOTOURBUG
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #79 from Fabian Maurer ---
Nice to hear the bug is fixed in wine, but the mesa bug still exists, so the
resolution is wrong. It's simply not acceptable for a driver to freeze the
system if an application misbehaves.
--
You are rece
https://bugs.freedesktop.org/show_bug.cgi?id=101731
Józef Kucia changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=101731
Józef Kucia changed:
What|Removed |Added
See Also||https://bugs.winehq.org/sho
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #76 from Shmerl ---
Unlike the previous one, it's minimal and doesn't conflict with various staging
patches that are also useful for TW3.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #75 from Shmerl ---
I made a variant of this hack for Wine itself:
https://bugs.winehq.org/attachment.cgi?id=59387
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #74 from mirh ---
Wine's role should just be that of avoiding their.. stuff, to misbehave.
But as for the freeze itself, I'd be expecting a bug in amdgpu, if the user
level bug was *allowed* to escalate to kernel one.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #73 from Shmerl ---
Józef Kucia made a hack patch for Wine to prevent the freeze:
https://bugs.winehq.org/show_bug.cgi?id=43273#c43
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #72 from Shmerl ---
(In reply to Samuel Pitoiset from comment #68)
> Thanks for confirming that the hack actually works.
>
> Yeah, it would be better to not hang in such situation but that's
> complicated.
Would that require change
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #71 from Lukas Jirkovsky ---
Created attachment 134411
--> https://bugs.freedesktop.org/attachment.cgi?id=134411&action=edit
special varying hack backport 17.2.1
Backported the patch to apply on 17.2.1
aidan: you can use this pat
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #70 from Samuel Pitoiset ---
(In reply to aidan from comment #69)
> (In reply to Samuel Pitoiset from comment #61)
> > Created attachment 134356 [details] [review] [review]
> > updated special varying hack
> >
> > What about this up
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #69 from ai...@jmad.org ---
(In reply to Samuel Pitoiset from comment #61)
> Created attachment 134356 [details] [review]
> updated special varying hack
>
> What about this updated patch? (the previous has to be reverted).
What comm
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #68 from Samuel Pitoiset ---
Thanks for confirming that the hack actually works.
Yeah, it would be better to not hang in such situation but that's complicated.
Though, you can try to boot with amdgpu.lockup_timeout=3000 (ie. wait 3s
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #67 from Lukas Jirkovsky ---
I can confirm that it works fine here after applying the hack, too.
Anyway, I'm with Shmerl here. In my opinion a user process should never be able
to make system unusable no matter what kind of stupid s
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #66 from Shmerl ---
(In reply to Samuel Pitoiset from comment #64)
>
> The attached patches should workaround both issues (TW3 and Superposition),
> but wine has to be fixed here.
>
> Please, let the bug open until it's really fixe
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #65 from Shmerl ---
(In reply to Samuel Pitoiset from comment #61)
> Created attachment 134356 [details] [review]
> updated special varying hack
>
> What about this updated patch? (the previous has to be reverted).
Great! I can con
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #64 from Samuel Pitoiset ---
See the attached trace from
https://bugs.freedesktop.org/show_bug.cgi?id=102797, it reproduces the same
issue.
So, basically the issue is that wine fails to set the transform feedback
varyings in some si
https://bugs.freedesktop.org/show_bug.cgi?id=101731
Samuel Pitoiset changed:
What|Removed |Added
CC||dark.shad...@web.de
--- Comment #63 f
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #62 from Shmerl ---
I'll give a try. May be game settings affect what's going on too. For the
reference, I set all to max, except hairworks off. Ambient occlusion: HBAO+.
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #61 from Samuel Pitoiset ---
Created attachment 134356
--> https://bugs.freedesktop.org/attachment.cgi?id=134356&action=edit
updated special varying hack
What about this updated patch? (the previous has to be reverted).
--
You a
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #60 from Samuel Pitoiset ---
Yeah, I built against the same commit and I'm able to reproduce the link-time
error.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #59 from Shmerl ---
Actually, looks like 2.17 is the last one, so their official build should be
just that. It's based on commit bb16263fe1974851f495435fef9a3d57fa2d4aa9
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #58 from Shmerl ---
I suppose I can also build Wine from that commit and apply all staging patches
including past 2.17.
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #57 from Shmerl ---
Here is the run with Wine staging 2.17 (MESA_DEBUG set):
ATTENTION: default value of option mesa_glthread overridden by environment.
*** The Witcher 3 SPECIAL HACK ENABLED ***
Mesa: User error: GL_INVALID_OPERATI
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #56 from Shmerl ---
(In reply to Samuel Pitoiset from comment #55)
> Okay, the hack doesn't work for you, Mesa fails to link because the varying
> name is not the same.
>
> What version of wine are you using? FWIW, I'm building my l
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #55 from Samuel Pitoiset ---
Okay, the hack doesn't work for you, Mesa fails to link because the varying
name is not the same.
What version of wine are you using? FWIW, I'm building my local copy from
bb16263fe1974851f495435fef9a3d5
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #54 from Shmerl ---
Created attachment 134355
--> https://bugs.freedesktop.org/attachment.cgi?id=134355&action=edit
Hack patch debug run log
Run with MESA_DEBUG=true and Wine logging enabled.
--
You are receiving this mail becau
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #53 from Samuel Pitoiset ---
Okay, that's expected. Didn't you get some Mesa user errors as well?
But the fact that it no longer hangs is a good news, somehow. :)
--
You are receiving this mail because:
You are the assignee for th
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #52 from Shmerl ---
(In reply to Samuel Pitoiset from comment #51)
> Guys, can you apply the proposed special hacky patch and try to reproduce
> the hang? It should, at least, partially "fix" the issue in the Velen area
> (cf the sav
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #51 from Samuel Pitoiset ---
Created attachment 134349
--> https://bugs.freedesktop.org/attachment.cgi?id=134349&action=edit
special varying hack
Guys, can you apply the proposed special hacky patch and try to reproduce the
hang?
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #50 from Shmerl ---
(In reply to Alex Deucher from comment #49)
> You can force a reset by reading /sys/kernel/debug/dri/0/amdgpu_gpu_reset
> but very few if any applications currently use the GL robustness extensions
> to query if t
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #49 from Alex Deucher ---
You can force a reset by reading /sys/kernel/debug/dri/0/amdgpu_gpu_reset but
very few if any applications currently use the GL robustness extensions to
query if the context is lost and resubmit their state.
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #48 from Shmerl ---
(In reply to Lukas Jirkovsky from comment #47)
> There's no such file on my system. There is a reset file for other PCI
> busses, but not for the GPU.
I don't have it either for RX 480 card.
--
You are receivin
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #47 from Lukas Jirkovsky ---
(In reply to Jan Vesely from comment #45)
> sounds like hung GPU. afaik amdgpu.ko does not support GPU timeout/reset yet.
> you can try reseting the GPU manually via
> /sys/class/drm/cardX/device/reset
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #46 from Shmerl ---
(In reply to Jan Vesely from comment #45)
> sounds like hung GPU. afaik amdgpu.ko does not support GPU timeout/reset yet.
> you can try reseting the GPU manually via
> /sys/class/drm/cardX/device/reset
How exact
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #45 from Jan Vesely ---
(In reply to Shmerl from comment #44)
> (In reply to Lukas Jirkovsky from comment #43)
> > Here are some additional information:
>
> Yes, I observed that as well. You can access the box over ssh, but it
> doe
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #44 from Shmerl ---
(In reply to Lukas Jirkovsky from comment #43)
> Here are some additional information:
Yes, I observed that as well. You can access the box over ssh, but it doens't
react to any local input. Also attempts to rebo
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #43 from Lukas Jirkovsky ---
I'm having the same problem during the initial cutscene in Velen.
Here are some additional information:
* While the computer seems frozen, it's not frozen completely. I can still
connect over ssh and do
https://bugs.freedesktop.org/show_bug.cgi?id=101731
Samuel Pitoiset changed:
What|Removed |Added
Summary|System freeze with AMDGPU |System freeze with AMDGPU
45 matches
Mail list logo
