To be honest… I doubt the answer will show up in the logs.
@enrico seems to have think he upgraded to F32, but seems he did not yet
Upgrading to F32 seems to me the best option for you.
I see I did not help you understand journalctl… you could read “man journalctl” which is what I do… but guess it would help I give you some hints.
journalctl --list-boots
should give you many boot entries… if it give an error it probably means your log are volatile (are erased at every boot) rather than being persistent. And we should help you fix that if it is the case for you.
journalctl --list-boots
give at first column a negative number… 0 or -0 is your current session,
-1 is the previous session,
-2 is the previous session of the previous session,
etc.
So when you reboots because of a freeze, the log with the session that frozed is in the past… -1 if you just rebooted, -2 if you rebooted twice, etc.
And you do things like:
journalctl -b -1
journalctl -b -2
to see these older sessions.
So you have to make a note to yourself of when freeze happens… and looks in journalctl --list-boots entries to find which one contains the session that have frozen.
And then you could send your logs to fpaste web site, with:
journalctl -b -1 --no-pager | fpaste
the -b -1 would means the session before the current one,
-p4 would limit to error messages
–no-pager would make sure it would not wait for you to press keys
| fpaste would send to paste site for 24h the contents…
that should result in a link that you can first check yourself in the browser to make sure it does not contains something you would not wish to publish