Freeze in kernel 6.5 (but 6.2 works)

[Jonathan Higdon]

Freeze began after a system update

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 21:45:39 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller])
InstallationDate: Installed on 2022-02-09 (713 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2018
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: INTEL H55
dmi.board.vendor: INTEL
dmi.board.version: INTEL
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[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. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. 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.

3. If step 2 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.

[Jonathan Higdon (jphigdon9999)]

HI, Thx for your help.

I got this error msg in step one:

" Failed to add match 'journalctl': Argumento inválido "

Em 24/01/2024 00:19, Daniel van Vugt escreveu:
> 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. Run these commands:
> journalctl -b0 > journal.txt
> journalctl -b-1 > prevjournal.txt
> and attach the resulting text files here.
>
> 2. 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.
>
> 3. If step 2 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.
>
>
> ** Package changed: xorg (Ubuntu) => ubuntu
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
> ** Summary changed:
>
> - Xorg freeze
> + Freeze
>
--
J.P.

3D Studio

www.jonathanpaul.com.br

[Daniel van Vugt (vanvugt)]

I'm guessing you accidentally inserted a space somewhere in the parameters to journalctl. The commands in comment #2 are correct.

[Jonathan Higdon (jphigdon9999)]

Ok I'll try again. Do I run it from the GRUB Root terminal?

Em 24/01/2024 00:19, Daniel van Vugt escreveu:
> 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. Run these commands:
> journalctl -b0 > journal.txt
> journalctl -b-1 > prevjournal.txt
> and attach the resulting text files here.
>
> 2. 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.
>
> 3. If step 2 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.
>
>
> ** Package changed: xorg (Ubuntu) => ubuntu
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
> ** Summary changed:
>
> - Xorg freeze
> + Freeze
>
--
J.P.

3D Studio

www.jonathanpaul.com.br

[Jonathan Higdon (jphigdon9999)]

Here 's a screen shot. I copy paste it from your email.

Em 24/01/2024 22:24, Daniel van Vugt escreveu:
> I'm guessing you accidentally inserted a space somewhere in the
> parameters to journalctl. The commands in comment #2 are correct.
>
--
J.P.

3D Studio

www.jonathanpaul.com.br

[Jonathan Higdon (jphigdon9999)]

Ok I figured it out.

Em 24/01/2024 22:24, Daniel van Vugt escreveu:
> I'm guessing you accidentally inserted a space somewhere in the
> parameters to journalctl. The commands in comment #2 are correct.
>
--
J.P.

3D Studio

www.jonathanpaul.com.br

[Daniel van Vugt (vanvugt)]

I see you're using kernel 6.2 now, but previously had kernel 6.5. So it looks like the issue is bug 2028165 and you should stick to kernel 6.2 to avoid that problem. Did I miss anything?

[Jonathan Higdon (jphigdon9999)]

That is correct. 6.2 is the only one that works in recovery mode.

Em 29/01/2024 02:59, Daniel van Vugt escreveu:
> I see you're using kernel 6.2 now, but previously had kernel 6.5. So it
> looks like the issue is bug 2028165 and you should stick to kernel 6.2
> to avoid that problem. Did I miss anything?
>
--
J.P.

3D Studio

www.jonathanpaul.com.br

[Daniel van Vugt (vanvugt)]

Oh I missed that. Having a problem with recovery mode probably means this isn't as simple as bug 2028165. Instead I'll move this to being just some new bug in kernel 6.5.

[Jonathan Higdon (jphigdon9999)]

So i reported the bug for you. But my computer is still in the same bad
shape. Will the new kernel fix it? Or will I have to format and
reinstall ubuntu again?

Em 30/01/2024 01:34, Daniel van Vugt escreveu:
> Oh I missed that. Having a problem with recovery mode probably means
> this isn't as simple as bug 2028165. Instead I'll move this to being
> just some new bug in kernel 6.5.
>
> ** Summary changed:
>
> - Freeze
> + Freeze in kernel 6.5 (but 6.2 works)
>
> ** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu)
>
> ** Changed in: linux-hwe-6.5 (Ubuntu)
> Status: Incomplete => New
>
--
J.P.

3D Studio

www.jonathanpaul.com.br

[Daniel van Vugt (vanvugt)]

I suggest you keep using older kernels for the time being. Please also subscribe to bug 2028165 because that does seem to be happening on your system.