https://bugs.kde.org/show_bug.cgi?id=466620
Chema <rondo...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #16 from Chema <rondo...@gmail.com> ---
I have good news! I just installed the new kernel 6.2.2, and with this version
the Powedevil problem is solved, at least for me in Wayland, which was where it
crashed! I hope it works for others too.
Going through the kernel changelog, I can only find these reviews that I see
that may have had something to do with it:
commit 83d403e773a851c9447e4d1847a6f1df91604d43
Author: Stylon Wang <stylon.w...@amd.com>
Date: Tue Jan 10 14:38:33 2023 +0800
drm/amd/display: Properly reuse completion structure
commit 0cf8307adbc6beb5ff3b8a76afedc6e4e0b536a9 upstream.
[Why]
Connecting displays to TBT3 docks often produces invalid
replies for DPIA AUX requests. It turns out the completion
structure was not re-initialized before reusing it, resulting
in immature wake up to completion.
[How]
Properly call reinit_completion() on reused completion structure.
Cc: sta...@vger.kernel.org
Reviewed-by: Solomon Chiu <solomon.c...@amd.com>
Acked-by: Alan Liu <haoping....@amd.com>
Signed-off-by: Stylon Wang <stylon.w...@amd.com>
Tested-by: Daniel Wheeler <daniel.whee...@amd.com>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
Cc: "Limonciello, Mario" <mario.limoncie...@amd.com>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
commit 9c591e6a027053460b61d63c239df4391fbce98f
Author: Nicholas Kazlauskas <nicholas.kazlaus...@amd.com>
Date: Mon Jan 23 14:59:28 2023 -0500
drm/amd/display: Move DCN314 DOMAIN power control to DMCUB
commit e383b12709e32d6494c948422070c2464b637e44 upstream.
[Why]
DOMAIN power gating control is now required to be done via firmware
due to interlock with other power features. This is to avoid
intermittent issues in the LB memories.
[How]
If the firmware supports the command then use the new firmware as
the sequence can avoid potential display corruption issues.
The command will be ignored on firmware that does not support DOMAIN
power control and the pipes will remain always on - frequent PG cycling
can cause the issue to occur on the old sequence, so we should avoid it.
Reviewed-by: Hansen Dsouza <hansen.dso...@amd.com>
Acked-by: Qingqing Zhuo <qingqing.z...@amd.com>
Signed-off-by: Nicholas Kazlauskas <nicholas.kazlaus...@amd.com>
Tested-by: Daniel Wheeler <daniel.whee...@amd.com>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
Cc: "Limonciello, Mario" <mario.limoncie...@amd.com>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
commit 8417e002b7165bdde96ef6af48708ad8de6fe194
Author: Thomas Weißschuh <li...@weissschuh.net>
Date: Mon Feb 20 06:46:12 2023 +0000
vc_screen: don't clobber return value in vcs_read
commit ae3419fbac845b4d3f3a9fae4cc80c68d82cdf6e upstream.
Commit 226fae124b2d ("vc_screen: move load of struct vc_data pointer in
vcs_read() to avoid UAF") moved the call to vcs_vc() into the loop.
While doing this it also moved the unconditional assignment of
ret = -ENXIO;
This unconditional assignment was valid outside the loop but within it
it clobbers the actual value of ret.
To avoid this only assign "ret = -ENXIO" when actually needed.
[ Also, the 'goto unlock_out" needs to be just a "break", so that it
does the right thing when it exits on later iterations when partial
success has happened - Linus ]
Reported-by: Storm Dragon <stormdragon2...@gmail.com>
Link: https://lore.kernel.org/lkml/y%2fks6vdql2pis...@hotmail.com/
Fixes: 226fae124b2d ("vc_screen: move load of struct vc_data pointer in
vcs_read() to avoid UAF")
Signed-off-by: Thomas Weißschuh <li...@weissschuh.net>
Link:
https://lore.kernel.org/lkml/64981d94-d00c-4b31-9063-43ad0a384...@t-8ch.de/
Signed-off-by: Linus Torvalds <torva...@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
I don't know if any of these fixes could really solve the problem, but it's the
only thing I see that makes any sense related to the Powerdevil problem.
Now I only have to solve the KDE problems with the HDMI, if one day I get
it....
--
You are receiving this mail because:
You are watching all bug changes.
