Firefox131 freeze the system randomly

After upgrading Firefox130 to 131 with yay, my Manjaro Sway has frozen randomly.
When I use Google Chrome or MS Edge, there is no problem.

I use Manjaro Sway edition on MINIFORUM HX90.

Before a force shutdown, the following log appeared.
Is this related to the freeze?

10月 04 21:16:41 hx90 rtkit-daemon[2194]: Supervising 3 threads of 3 processes of 1 users.
10月 04 21:17:43 hx90 rtkit-daemon[2194]: Supervising 3 threads of 3 processes of 1 users.
10月 04 21:17:43 hx90 rtkit-daemon[2194]: Supervising 3 threads of 3 processes of 1 users.
10月 04 21:18:14 hx90 rtkit-daemon[2194]: Supervising 3 threads of 3 processes of 1 users.
10月 04 21:18:14 hx90 rtkit-daemon[2194]: Supervising 3 threads of 3 processes of 1 users.
10月 04 21:19:38 hx90 rtkit-daemon[2194]: The canary thread is apparently starving. Taking action.
10月 04 21:19:38 hx90 rtkit-daemon[2194]: Demoting known real-time threads.
10月 04 21:19:38 hx90 rtkit-daemon[2194]: Successfully demoted thread 24744 of process 3319.
10月 04 21:19:38 hx90 rtkit-daemon[2194]: Successfully demoted thread 4022 of process 2722.
10月 04 21:19:38 hx90 rtkit-daemon[2194]: Successfully demoted thread 2590 of process 2450.
10月 04 21:19:38 hx90 rtkit-daemon[2194]: Demoted 3 threads.
-- Boot 05639eb6f3a04e189880393ff3ee54e7 --
10月 04 21:20:39 hx90 kernel: Linux version 6.6.52-1-MANJARO (builduser@fv-az1204-572) (gcc (GCC) 14.2.1 20240910, GNU ld (GNU Binutils) 2.43.0) #1 SMP PREEM>
10月 04 21:20:39 hx90 kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-6.6-x86_64 root=UUID=c5f3f1e1-6109-43ef-a947-cd4c29c7cfb1 rw rootflags=subvol=@ apparm>
10月 04 21:20:39 hx90 kernel: BIOS-provided physical RAM map:

The following link solved the issue.
The problem was on AMD CPU.

If cstate6 was the problem why limit it to maximum cstate of 1 ?
If its an AMD then why intel options ?

You may have inadvertently applied a good option, but I have trouble seeing all of the options in the linked post being applicable.

Or did you only apply part of what is detailed there?

Also be aware that cstates, in ascending order, are helpful for sleep, low power, and in general saving battery. Limiting cstates to only 1 will unquestionably have negative impacts on your power consumption.

PS.

The real way to disable cstate 6 would be boot parameter

processor.max_cstate=5

But how this would be related to firefox and only shown sometimes … I do not know.
It also does not really make sense to me.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.