https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #22 from Shmerl ---
Or kwin doesn't work correctly. What can be the problem then if it's not kwin?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419242
David Edmundson changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #21 from David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #20 from Shmerl ---
So, can anything be done about it? Can you please collaborate with AMD
developers on this somehow?
This IS a bug, because in practice, the session doesn't recover. If the reason
lies in the radeonsi bugs, then they have
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #19 from Shmerl ---
The bottom line is, for the end user this is not working as it should.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #18 from Shmerl ---
> There is no indication of this being a kwin bug at this time.
According to AMD developers, KWin is likely not using OpenGL robustness
extensions correctly, since GPU reset should be supported properly in the
kernel and
https://bugs.kde.org/show_bug.cgi?id=419242
David Edmundson changed:
What|Removed |Added
Resolution|WAITINGFORINFO |NOT A BUG
--- Comment #17 from David Edmundso
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #16 from Christoph Feck ---
The current status of this ticket is ambiguous.
Comment 1 says that resets should be handled gracefully in kwin. If they are
not, this ticket should get reopened.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #15 from Shmerl ---
I can try triggering GPU reset explicitly for a test to see how kwin reacts.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #14 from Shmerl ---
According to AMD developers:
> The kernel driver and mesa support the necessary OpenGL robustness extensions
> to enable this functionality. I'm not familiar with kwin's implementation
> however.
So there is some dis
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #13 from Shmerl ---
Or more exactly: https://gitlab.freedesktop.org/drm/amd/issues/892
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419242
Shmerl changed:
What|Removed |Added
Resolution|NOT A BUG |WAITINGFORINFO
--- Comment #12 from Shmerl ---
(In re
https://bugs.kde.org/show_bug.cgi?id=419242
David Edmundson changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #10 from Shmerl ---
OK, just got another hang and reset. Desktop became garbled, with some
reactions to input.
I switched to tty, and run:
DISPLAY=:0 kwin_x11 --replace
That started, and showed various OpenGL info about the system in the
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #9 from Shmerl ---
Oh, I missed one preceding dmesg part:
[16340.923960] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting
for fences timed out!
[16345.787744] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0
time
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #8 from Shmerl ---
OK, it happened again, and I can tell it was a reset, since I see it in dmesg
(see below).
The session got corrupted again, but was reacting on some garbled fashion to
input like before.
I switched to tty, and run
kwin_
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #7 from Shmerl ---
It reacted in as something was happening on the screen due to Alt+F2, but it
was garbled.
> kwin_x11 --replace
Thanks, I'll give it a try.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #6 from David Edmundson ---
>but the whole desktop was still frozen
>It even reacted on me opening krunner with Alt+F2, but all visuals were
>garbled.
It can't be both.
>What is the right way to do it?
kwin_x11 --replace
--
You are r
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #5 from Shmerl ---
Also, when reset happens, there is a brief period when everything is completely
frozen, and then it starts reacting on input again, and this what happened
here.
It even reacted on me opening krunner with Alt+F2, but all v
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #4 from Shmerl ---
(In reply to David Edmundson from comment #3)
> >The driver reset it,
>
> How do you know?
>
> Did a restart of kwin_x11 fix it?
Because it didn't cause a hard hang, like it used to before amdgpu implemented
reset for N
https://bugs.kde.org/show_bug.cgi?id=419242
David Edmundson changed:
What|Removed |Added
Status|REOPENED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=419242
Shmerl changed:
What|Removed |Added
Summary|Support robust recovery |KWin doesn't recover after
|from GPU
21 matches
Mail list logo
