Ubuntu 22.04 freezes suddenly for no apparent reason. it cannot reproduce.

[Tony Rmz]

Ubuntu 22.04 freezes suddenly for no apparent reason. It does not respond to any rescue key combination (Alt + SysRq + R E I S U, Alt + F2, etc).
Only with "Alt + SysRq + B" I can do a reset.
I have updated the kernel to the next version
antonio@antoniormz:/var/crash$ uname -r
5.19.0-051900rc6-generic

And I am still testing the stability.

Release:
antonio@antoniormz:/var/crash$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04

Package version:
antonio@antoniormz:/var/crash$ apt-cache policy pkgname
N: Unable to locate package pkgname

Expected behavior:
Could you please help me identify what is causing the system freeze and how to fix it?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
Uname: Linux 5.19.0-051900rc6-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 24 23:38:28 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-01-09 (46 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Daniel van Vugt (vanvugt)]

Also, next time the problem happens, please reboot and then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

[Tony Rmz (tnxhawks)]

Thanks Daniel, since it is my work tool I had to restore the system with TimeShift and be able to use my laptop. And now that I am looking for the crash file there is nothing.

I will keep an eye out if it reproduces again and follow the procedure you indicated.

[Tony Rmz (tnxhawks)]

Hi again Daniel, just after writing you the message before, the system crash again twice.
However, the crash folder doesn't contain any files:
```
antonio@antoniormz:~$ ll /var/crash/
total 8
drwxrwsrwt  2 root whoopsie 4096 feb 25 12:20 ./
drwxr-xr-x 14 root root     4096 ago  9  2022 ../
```
And the system has recorded the crashes of today and previous days.
```
antonio@antoniormz:~$ last -x | egrep "boot|crash" | head
reboot   system boot  5.19.0-32-generi Wed Mar  1 12:32   still running
antonio  :0           :0               Wed Mar  1 11:24 - crash  (01:08)
reboot   system boot  5.19.0-32-generi Wed Mar  1 11:18   still running
antonio  :0           :0               Sun Feb 26 02:44 - crash (3+08:33)
reboot   system boot  5.19.0-32-generi Sun Feb 26 02:44   still running
antonio  pts/1        127.0.0.1        Sat Feb 25 13:03 - crash  (13:40)
antonio  :0           :0               Sat Feb 25 13:01 - crash  (13:42)
reboot   system boot  5.19.0-32-generi Sat Feb 25 13:01   still running
reboot   system boot  5.19.0-32-generi Sat Feb 25 12:40 - 13:01  (00:21)
reboot   system boot  5.19.0-32-generi Sat Feb 25 12:15 - 12:39  (00:24)
```
Here you can find the prevboot.txt file collected.

[Tony Rmz (tnxhawks)]

Hi Daniel, again two more crashes today.
Find attached the prevboot files for each crash.

Thanks in advance!

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1980831, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.