I see now at least three different bugs in this topic, and one phenomenon (including at least one of the bugs mentioned here) has definitely been solved by 6.14.3.
It is no longer comprehensible what belongs to where, and I therefore suggest to maybe open a new topic for post-6.14.3 issues, in order to allow supporters and (in case of a bug report) the maintainers to differentiate the remaining issues from those solved by 6.14.3.
Also, keep in mind that especially kernel issues can be very complex, and the logs of the very moment you experience the issue can be just symptoms (so the major indicator might be logged in the journal long before the time of the experience). Therefore, if you open a new topic, I suggest to add two things:
First, an extract of the very moment (so about the very moment plus at least 15 seconds before and after), but not just with -k (that is kernel-only entries) but from all logs . E.g., get the extract of the very times from sudo journalctl --no-hostname --boot=0 (if you had a full freeze or so, and need to get the logs of a previous boot and not the current one, use -1 instead of 0 → -1 implies the last boot, not the current one)
→ please use a codebox for this (the </> button)
→ also, feel free to further anonymize the content if there are still things contained you consider private or so
Second, at the full log of the kernel: sudo journalctl -k --no-hostname --boot=0 (as before, -1 instead of 0 if the last boot is needed instead of the current one).
→ you might use an external link for that or so
That said, you might want to wait for 6.14.4, which is already released and thus is likely to end up in bodhi soon and in your updates soon later. If that doesn’t solve your issue, open a new topic as suggested, and maybe already a bug report: if you open a bug report against kernel, please read the template carefully (once you click on the component kernel in bugzilla, a template will be automatically added to the report): consideration of the bug report is likely only if the template is filled correctly. Also, add the logs I mentioned. And of course: before creating a new kernel bug report, check out the existing bug reports that have been added since the release of 6.14 → if there is already one that describes your issue and that has then not been solved by 6.14.4, you might just add your case there → the more comes together in one report, the better the chances are to get it solved soon rather than having many different reports of the same thing.