Ubuntu 26.04 briefly freezing every so often (again!)

Hi everyone,

Following the suggestions in the thread ( Kubuntu 26.04 briefly freezing every so often - #3 by ogra ), I installed the 7.0.0-26 packages on my Ubuntu 26.04, and the same problems described in that thread—which were also occurring here—disappeared.

However, when I had to reinstall Ubuntu and apply version 7.0.0-29 (since v.26 no longer exists), the problems returned :frowning:
Here is my laptop’s configuration:
Acer Nitro ANV15-41, 32 GB RAM
AMD Ryzen™ 7 7735HS (with AMD Radeon 680M × 16 integrated graphics)
NVIDIA GeForce RTX 4050 Laptop GPU
Firmware version V1.51
nvidia-driver-595-open / 595.84-0ubuntu0.26.04.1 - CUDA Version: 13.2

I use Ubuntu with a second Samsung monitor connected via HDMI, in extended mode.
I’ve noticed that the freezes happen most frequently when watching YouTube videos in a browser with multiple tabs open. But that’s not the only scenario; it also happens simply while browsing the web or working in an IDE. Suddenly, the laptop screen freezes, but the second monitor remains active. If I open a new application or move the mouse to the primary screen and click, everything freezes completely—even the keyboard stops working. I’m forced to hold down the power button to restart the laptop.

Are you experiencing the same problem? Do you know how I can figure out what’s going on? I have little experience with logs and don’t know where or how to look for errors.

You cited a good example. Provide equivalent information.
I see your hardware specs. Where is your OS information?

If you are open to a suggestion, start the diagnostic process fresh here – you have a freeze, and want help to diagnose it. Don’t jump to the conclusion that “it’s the kernel” unless you have proof (show us).

Sometimes it is the kernel…sometimes it’s not. The topic you cited also discovered possible hardware and wayland issues.

2 Likes

Had a similar issue with freezing on an nvidia laptop. Here’s my solution.

I’m just an ordinary Ubuntu user with very little technical knowledge to perform a comprehensive analysis of the issue.

I’ve been following the instructions from the thread I mentioned, which is why I assumed it was a kernel problem—though it could actually be something else, like a driver issue.

So, let me rephrase my request: Could you provide a set of steps (such as terminal commands) to help me investigate the problem further?

Here are my some details about my laptop and system:

Ubuntu 26.04 LTS
GNOME 50.1
Wayland
Linux 7.0.0-29-generic
x86_64

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / Mobile] [10de:28a1] (rev a1)
   Subsystem: Acer Incorporated [ALI] Device [1025:1758]
   Kernel driver in use: nvidia
   Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
75:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] [1002:1681] (rev 0a)
   Subsystem: Acer Incorporated [ALI] Device [1025:1758]
   Kernel driver in use: amdgpu
   Kernel modules: amdgpu
❯ ubuntu-drivers list
nvidia-driver-595-open, (kernel modules provided by linux-modules-nvidia-595-open-generic-hwe-26.04)
nvidia-driver-580-open, (kernel modules provided by linux-modules-nvidia-580-open-generic-hwe-26.04)
nvidia-driver-610-open, (kernel modules provided by linux-modules-nvidia-610-open-generic-hwe-26.04)
nvidia-driver-595, (kernel modules provided by linux-modules-nvidia-595-generic-hwe-26.04)
nvidia-driver-580, (kernel modules provided by linux-modules-nvidia-580-generic-hwe-26.04)
nvidia-driver-610, (kernel modules provided by linux-modules-nvidia-610-generic-hwe-26.04)
nvidia-driver-595-server-open, (kernel modules provided by linux-modules-nvidia-595-server-open-generic-hwe-26.04)
nvidia-driver-580-server-open, (kernel modules provided by linux-modules-nvidia-580-server-open-generic-hwe-26.04)
nvidia-driver-595-server, (kernel modules provided by linux-modules-nvidia-595-server-generic-hwe-26.04)
nvidia-driver-580-server, (kernel modules provided by linux-modules-nvidia-580-server-generic-hwe-26.04)

❯ nvidia-smi
Mon Aug 10 14:42:38 2026
±----------------------------------------------------------------------------------------+
| NVIDIA-SMI 595.84                 Driver Version: 595.84         CUDA Version: 13.2     |
±----------------------------------------±-----------------------±---------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 4050 …    Off |   00000000:01:00.0 Off |                  N/A |
| N/A   38C    P3             12W /   68W |      20MiB /   6141MiB |     14%      Default |
|                                         |                        |                  N/A |
±----------------------------------------±-----------------------±---------------------+

These are the last events recorded in the log, immediately before the freeze, but I don’t know how to interpret them. Can anyone help me, please?

$ journalctl -b -1 -k

ago 17 17:50:18 nitro kernel: audit: type=1400 audit(1786999818.696:522): apparmor="AUDIT" operation="exec" class="file" info="conflicting profile attachments" profile="unconfined" name="/opt/brave.com/brave/brave" pid=76788 comm="ThreadPoolSingl" requested_mask="x" fsuid=1000 ouid=0
ago 17 17:50:57 nitro kernel: audit: type=1400 audit(1786999857.371:523): apparmor="AUDIT" operation="exec" class="file" info="conflicting profile attachments" profile="unconfined" name="/opt/brave.com/brave/brave" pid=76868 comm="ThreadPoolSingl" requested_mask="x" fsuid=1000 ouid=0
ago 17 17:58:52 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
ago 17 17:58:52 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
ago 17 17:58:52 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
ago 17 17:59:02 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* [CRTC:364:crtc-0] flip_done timed out
ago 17 18:00:02 nitro kernel: audit: type=1400 audit(1787000402.731:524): apparmor="DENIED" operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" name="/proc/sys/vm/max_map_count" pid=77191 comm="firmware-notifi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
ago 17 18:19:04 nitro kernel: audit: type=1400 audit(1787001544.125:525): apparmor="AUDIT" operation="exec" class="file" info="conflicting profile attachments" profile="unconfined" name="/opt/brave.com/brave/brave" pid=79164 comm="ThreadPoolForeg" requested_mask="x" fsuid=1000 ouid=0
ago 17 18:19:21 nitro kernel: sysrq: This sysrq operation is disabled.
ago 17 18:19:22 nitro kernel: sysrq: This sysrq operation is disabled.
ago 17 18:19:23 nitro kernel: sysrq: This sysrq operation is disabled.
ago 17 18:19:24 nitro kernel: sysrq: Emergency Sync
ago 17 18:19:24 nitro kernel: Emergency Sync complete
ago 17 18:19:25 nitro kernel: sysrq: Emergency Remount R/O

There are several possibilites:

This looks like a GPU-related bug. Might be a driver issue. Might not.

I will leave diagnosing the GPU errors to somebody more schooled in that area.

This also looks GPU-related bug. Oversimplified: This occurs when a display page refresh times out.

I will leave diagnosing the GPU errors to somebody more schooled in that area.

‘Emergency Remount R/O’ of a storage device typically occurs when connection to the disk/ssd is interrupted or the hardware is failing. Disks and SSDs wear out, and this is what wearing out looks like in the log.

I suggest looking up how to run a SMART test on your storage device to rule out that cause.

1 Like

Using ChatGPT, it recommended a few tasks:

  1. Turn off Night Light
  2. Disable NVIDIA gpu (I started here)
  3. Use Xorg
  4. Use another kernel
  5. Test firmware
  6. Check laptop’s configuration
    For all the recommended tasks, ChatGPT asked for details so we could analyze the problem together. I started with Task 2 because, for me, it was the simplest and made the most sense. Details follow below:
$ prime-select query
on-demand
$ sudo prime-select intel
$ sudo reboot

…but since my laptop has only one HDMI port linked directly to the Nvidia GPU and I use a second monitor connected to it, that task became unfeasible. So, I enabled only the Nvidia GPU:

$ sudo prime-select nvidia
$ sudo reboot
$ prime-select query
nvidia

So far, the laptop hasn’t frozen. I’ww keep testing it.

Unfortunately, it didn’t work :frowning:

I had two IDEs open, plus Brave with several tabs—some of which were playing YouTube videos. I noticed this happens as I navigate through the video comments. Here is the journal:

ago 18 16:13:30 nitro kernel: audit: type=1400 audit(1787080410.319:338): apparmor="AUDIT" operation="exec" class="file" info="conflicting profile attachments" profile="unconfined" name="/opt/brave.com/brave/brave" pid=101676 comm="ThreadPoolSingl" requested_mask="x" fsuid=1000 ouid=0
ago 18 16:39:47 nitro kernel: audit: type=1400 audit(1787081987.984:339): apparmor="AUDIT" operation="exec" class="file" info="conflicting profile attachments" profile="unconfined" name="/opt/brave.com/brave/brave" pid=111613 comm="ThreadPoolSingl" requested_mask="x" fsuid=1000 ouid=0
ago 18 16:40:11 nitro kernel: audit: type=1400 audit(1787082011.985:340): apparmor="AUDIT" operation="exec" class="file" info="conflicting profile attachments" profile="unconfined" name="/opt/brave.com/brave/brave" pid=111759 comm="ThreadPoolSingl" requested_mask="x" fsuid=1000 ouid=0
ago 18 16:40:18 nitro kernel: audit: type=1400 audit(1787082018.885:341): apparmor="AUDIT" operation="exec" class="file" info="conflicting profile attachments" profile="unconfined" name="/opt/brave.com/brave/brave" pid=111788 comm="ThreadPoolSingl" requested_mask="x" fsuid=1000 ouid=0
ago 18 16:40:41 nitro kernel: audit: type=1400 audit(1787082041.272:342): apparmor="AUDIT" operation="exec" class="file" info="conflicting profile attachments" profile="unconfined" name="/opt/brave.com/brave/brave" pid=111932 comm="ThreadPoolSingl" requested_mask="x" fsuid=1000 ouid=0
ago 18 17:19:23 nitro kernel: audit: type=1400 audit(1787084363.542:343): apparmor="AUDIT" operation="exec" class="file" info="conflicting profile attachments" profile="unconfined" name="/opt/brave.com/brave/brave" pid=125419 comm="ThreadPoolSingl" requested_mask="x" fsuid=1000 ouid=0
ago 18 17:19:58 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
ago 18 17:19:58 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
ago 18 17:19:58 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
ago 18 17:20:09 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* [CRTC:364:crtc-0] flip_done timed out
ago 18 17:22:27 nitro kernel: audit: type=1400 audit(1787084547.480:344): apparmor="AUDIT" operation="exec" class="file" info="conflicting profile attachments" profile="unconfined" name="/opt/brave.com/brave/brave" pid=126775 comm="brave-browser-s" requested_mask="x" fsuid=1000 ouid=0
ago 18 17:22:27 nitro kernel: audit: type=1400 audit(1787084547.559:345): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=126775 comm="brave" requested="userns_create" target="unprivileged_userns" execpath="/opt/brave.com/brave/brave"
ago 18 17:22:27 nitro kernel: audit: type=1400 audit(1787084547.561:346): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=126791 comm="brave" capability=21  capname="sys_admin"
ago 18 17:22:27 nitro kernel: audit: type=1400 audit(1787084547.564:347): apparmor="AUDIT" operation="exec" class="file" info="conflicting profile attachments" profile="unconfined" name="/opt/brave.com/brave/brave" pid=126792 comm="brave" requested_mask="x" fsuid=1000 ouid=0
ago 18 17:22:27 nitro kernel: audit: type=1400 audit(1787084547.568:348): apparmor="AUDIT" operation="exec" class="file" info="conflicting profile attachments" profile="unconfined" name="/opt/brave.com/brave/brave" pid=126794 comm="chrome-sandbox" requested_mask="x" fsuid=1000 ouid=0
ago 18 17:24:13 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* flip_done timed out
ago 18 17:24:13 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* [CRTC:364:crtc-0] commit wait timed out
ago 18 17:24:23 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* flip_done timed out
ago 18 17:24:23 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* [CONNECTOR:378:eDP-1] commit wait timed out
ago 18 17:24:31 nitro kernel: sysrq: This sysrq operation is disabled.
ago 18 17:24:32 nitro kernel: sysrq: This sysrq operation is disabled.
ago 18 17:24:32 nitro kernel: sysrq: This sysrq operation is disabled.
ago 18 17:24:33 nitro kernel: sysrq: Emergency Remount R/O
ago 18 17:24:34 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* flip_done timed out
ago 18 17:24:34 nitro kernel: amdgpu 0000:75:00.0: [drm] *ERROR* [PLANE:202:plane-3] commit wait timed out
1 Like

3 posts were split to a new topic: Ubuntu 26.04 Freezing Issues

I would focus on this ^^^ (plus it’s easy to test) instead of most of the suggestions offered by the LLM:

#3 isn’t applicable, The Gnome shipped with Ubuntu 26.04 is wayland only.

#1 seems nonsensical.

Everything else is as generic “trow stuff at the wall to see what sticks” as it can be.

Do not bury the SSD yet, that “sysrq: Emergency Remount R/O” is just someone bravely pressing Alt+SysRq+U in panic! :grinning_face:

The real villain right above it is AMD display firmware crashing on eDP-1: amdgpu: DMCUB error / flip_done timed out

Add amdgpu.psr=0 to your grub command line to disable Panel Self Refresh, and your laptop screen should stop freezing :wink:

3 Likes

This topic was automatically closed after 30 days. New replies are no longer allowed.