With regards to the previous mail (see below), 6.3.1 with
amd_pstate=passive felt more stable on my hardware but now, after the
GUI within a virtual machine was to start, the outcome was comparable
but less disastrous than with pstate=active: first it felt like the
system froze, the screen was like restarting a few times (black for a
moment each time) before it finally seemed to froze, but then, when
doing CTRL+ALT+F6, it took several seconds but then I could switch to
the terminal. Terminal worked fine. When switching back, the screen
remained black, but CTRL+ALT+F6 was still possible even it it took
always several seconds. systemctl restart sddm seemed to work initially,
but once clicking ENTER in sddm, I am back to the black screen (the
"dead" KDE/wayland screen seems to be not affected by killing sddm).
journalctl -r root logs attached of the last 10 minutes attached, to
ensure all that led to the issue is contained. I now switch so the
default driver acpi-cpufreq, which used to be not reliable on my
hardware in earlier kernels, but maybe in combination with 6.3.1 it
works better. I have not yet opened an issue ticket because 6.3.1 is
still testing and 6.2.X is no longer worth a new ticket. Let me know if
I shall already open one.
Chris/py0xc3
On 5/7/23 22:57, Christopher Klooz wrote:
I started to run 6.3.1. on my system* today with amd_pstate=active
(...hoping it solves some issues I have on my hardware, see the bug
ticket below). The issue of today with 6.3.1.: it worked properly most
of the day, but when the system was not used several minutes, it
completely froze with Firefox and some other applications open
(CTRL+ALT+F* did not respond as well). I attached the "journalctl -r
--boot=-1" after I force-rebooted.
However, I cannot exclude that it is related to an open ticket (this
"symptom" is not new with 6.3.1 on my hardware), but *the logs of this
time with 6.3.1 with amd_pstate=active (see attachment) differ* to the
logs of the earlier issues: see
https://bugzilla.redhat.com/show_bug.cgi?id=2193110 (I don't think at
this time that this is caused by firefox, but firefox may has some
unintended behavior that triggers the issues).
I now switched to amd_pstate=passive but remain with 6.3.1 to see how
it develops. My "feeling" of the day is that 6.3.1 is still more
stable than 6.2.
Maybe the logs are indicative for you.
Concerning the SELinux denials (to which I see no relation in this
issue): the user account is a SELinux confined user sysadm_u.
* Lenovo Thinkpad T16 AMD, AMD Ryzen 7 PRO 6850U, Fedora KDE spin,
tainted=0, only default repos/software.
Regards,
Chris (py0xc3)
_______________________________________________
test mailing list -- test(a)lists.fedoraproject.org
To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue