Ubuntu 26.04 Freezing Issues

Support and Help
1

Hi. Followup thread of Ubuntu 26.04 briefly freezing every so often (again!)

26.04.1 LTS version here and I’m also experiencing these freezes all of a sudden with the recent upgrades, but I can’t trace back the cause, journalctl doesn’t show any useful info since it seem stop logging right before the freeze occurs.

Anyone out there with a solution?

:desktop_computer: All system related infos:

System Details Report 
# System Details Report
---

## Report details
- **Date generated:**                              2026-09-05 13:43:27

## Hardware Information:
- **Hardware Model:**                              FUJITSU ESPRIMO E510
- **Memory:**                                      16.0 GiB
- **Processor:**                                   Intel® Core™ i5-3470 × 4
- **Graphics:**                                    Quadro K620
- **Disk Capacity:**                               (null)

## Software Information:
- **Firmware Version:**                            V4.6.5.3 R1.30.0 for D3171-A1x
- **OS Name:**                                     Ubuntu 26.04.1 LTS
- **OS Build:**                                    (null)
- **OS Type:**                                     64-bit
- **GNOME Version:**                               50
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 7.0.0-31-generic
inxi -Fzxxx 
System:
  Kernel: 7.0.0-31-generic arch: x86_64 bits: 64 compiler: gcc v: 15.2.0
    clocksource: tsc
  Desktop: GNOME v: 50.1 tk: GTK v: 3.24.52 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM3 v: 50.1 Distro: Ubuntu 26.04.1 LTS
    (Resolute Raccoon)
Machine:
  Type: Desktop System: FUJITSU product: ESPRIMO E510 v: N/A
    serial: <superuser required> Chassis: type: 3 v: C$ELW3
    serial: <superuser required>
  Mobo: FUJITSU model: D3171-A1 v: S26361-D3171-A1
    serial: <superuser required> part-nu: S26361-Kxxx-Vyyy
    uuid: <superuser required> Firmware: UEFI vendor: FUJITSU // American
    Megatrends v: 4.6.5.3 R1.30.0 for D3171-A1x date: 04/22/2015
CPU:
  Info: quad core model: Intel Core i5-3470 bits: 64 type: MCP
    smt: <unsupported> arch: Ivy Bridge rev: 9 cache: L1: 256 KiB L2: 1024 KiB
    L3: 6 MiB
  Speed (MHz): avg: 1596 min/max: 1600/3600 cores: 1: 1596 2: 1596 3: 1596
    4: 1596 bogomips: 25542
  Flags-basic: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GM107GL [Quadro K620] driver: nvidia v: 580.173.02
    arch: Maxwell pcie: speed: 2.5 GT/s lanes: 16 ports: active: DVI-I-1
    empty: DP-1 bus-ID: 01:00.0 chip-ID: 10de:13bb class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.10
    compositor: gnome-shell driver: gpu: nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: DVI-I-1 model: Fujitsu Siemens B22W-7 LED serial: <filter>
    res: 1680x1050 dpi: 90 size: 474x296mm (18.66x11.65") diag: 559mm (22")
    modes: max: 1680x1050 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.173.02
    glx-v: 1.4 direct-render: yes renderer: Quadro K620/PCIe/SSE2
    display-ID: :0.0
  API: Vulkan v: 1.4.341 layers: 9 surfaces: N/A device: 0
    type: discrete-gpu driver: nvidia device-ID: 10de:13bb device: 1 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo
    gpu: nvidia-settings,nvidia-smi x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Fujitsu
    Solutions B75 Ivy Bridge   CX20642 on Esprimo P510 D3171
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20
    class-ID: 0403
  Device-2: NVIDIA GM107 High Definition Audio [GeForce 940MX]
    driver: snd_hda_intel v: kernel pcie: speed: 5 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:0fbc class-ID: 0403
  API: ALSA v: k7.0.0-31-generic status: kernel-api
  Server-1: PipeWire v: 1.6.2 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Fujitsu Solutions RTL8211DN on Esprimo P510 D3171 driver: r8169
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Drives:
  Local Storage: total: 119.24 GiB used: 65.56 GiB (55.0%)
  ID-1: /dev/sda vendor: SanDisk model: SD8SB8U-128G-1006 size: 119.24 GiB
    type: USB rev: 2.1 spd: 480 Mb/s lanes: 1 tech: SSD serial: <filter>
    fw-rev: 4101 scheme: GPT
Partition:
  ID-1: / size: 115.78 GiB used: 65.55 GiB (56.6%) fs: ext4 dev: /dev/sda2
  ID-2: /boot/efi size: 1.05 GiB used: 10.8 MiB (1.0%) fs: vfat
    dev: /dev/sda1
Swap:
  ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -1
    file: /swap.img
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB available: 15.07 GiB used: 2.38 GiB (15.8%)
  Processes: 314 Power: uptime: 4m states: freeze,mem,disk suspend: deep
    wakeups: 0 hibernate: platform Init: systemd v: 259 default: graphical
  Packages: 2505 pm: dpkg pkgs: 2473 pm: snap pkgs: 32 Compilers: N/A
    Shell: Bash v: 5.3.9 running-in: ptyxis-agent inxi: 3.3.40
log messages 
Sep  4 20:58:50 systemd: Failed to start app-gnome-snap\x2duserd\x2dautostart-17357.scope - Application launched by gnome-session-service.
Sep  4 20:58:47 gdm-session-wor: gkr-pam: unable to locate daemon control file
Sep  4 20:58:47 gdm-session-wor: gkr-pam: unable to locate daemon control file
Sep  4 20:57:12 gdm-session-wor: gkr-pam: unable to locate daemon control file
Sep  4 20:55:15 systemd: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled.
Sep  4 20:41:28 gdm-session-wor: gkr-pam: couldn't unlock the login keyring.
Sep  4 20:41:23 canonical-livep: Task "refresh" returned an error: livepatch check failed: POST request to "https://livepatch.canonical.com/v1/client/50fad3949d3b45c09fc8315e3b92fcf2/updates" failed: Post "https://livepatch.canonical.com/v1/client/50fad3949d3b45c09fc8315e3b92fcf2/updates": dial tcp: lookup livepatch.canonical.com on 127.0.0.53:53: server misbehaving, retrying in 30s.
Sep  4 20:41:23 canonical-livep: Task "refresh" returned an error: livepatch check failed: POST request to "https://livepatch.canonical.com/v1/client/50fad3949d3b45c09fc8315e3b92fcf2/updates" failed: Post "https://livepatch.canonical.com/v1/client/50fad3949d3b45c09fc8315e3b92fcf2/updates": dial tcp: lookup livepatch.canonical.com on 127.0.0.53:53: server misbehaving, retrying in 30s.
Sep  4 20:41:23 canonical-livep: refresh patch failed: livepatch check failed: POST request to "https://livepatch.canonical.com/v1/client/50fad3949d3b45c09fc8315e3b92fcf2/updates" failed: Post "https://livepatch.canonical.com/v1/client/50fad3949d3b45c09fc8315e3b92fcf2/updates": dial tcp: lookup livepatch.canonical.com on 127.0.0.53:53: server misbehaving
Sep  4 20:41:20 kernel: 
Sep  4 20:41:16 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20251212/psparse-529)
Sep  4 20:41:16 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20251212/psparse-529)
Sep  4 20:41:16 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20251212/psargs-332)
Sep  4 20:41:16 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20251212/psparse-529)
Sep  4 20:41:16 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20251212/psargs-332)
Sep  4 20:41:16 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20251212/psparse-529)
Sep  4 20:41:16 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20251212/psargs-332)
Sep  4 20:41:16 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20251212/psparse-529)
Sep  4 20:41:16 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20251212/psargs-332)
Sep  4 20:41:16 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20251212/psparse-529)
Sep  4 20:41:16 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20251212/psargs-332)
Sep  4 20:41:16 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20251212/psparse-529)
Sep  4 20:41:16 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20251212/psargs-332)
Sep  4 20:41:16 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20251212/psparse-529)
Sep  4 20:41:16 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20251212/psargs-332)
Sep  4 20:41:16 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20251212/psparse-529)
Sep  4 20:41:16 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20251212/psargs-332)
Sep  4 20:41:15 kernel: x86/cpu: SGX disabled or unsupported by BIOS.
Sep  4 20:41:15 kernel: KHO: Failed to reserve lowmem scratch buffer

Further details: This freeze occurs randomly, sometimes 5-10 minutes after booting in, sometimes 2 hours after. It’s really hard to trace back the cause.

:thinking: My observations of what I did before freeze happened, so far:

  • Opened App Center
  • Opened System Settings
  • Double clicked .deb file inside Nautilus
  • Played with Fallout Shelter game via Steam (official snap version)
  • Watched some youtube videos in Chromium (official snap version)
  • Listened to music in Spotify (official snap version)

:thought_balloon: Note: This list doesn’t necesarry mean that these scenarios are directly related to the system freeze, it’s all for logging purposes, to further isolate the source of the problem.

…I will update the list above, in case if I experience the freeze in other kinds of scenarios.

:hammer_and_wrench: Tests I performed to isolate hardware related issues:

  • Drive Swap Test A: Moved the primary system drive (the one with the specs listed above) to a known-stable computer, and the freezing issues followed the drive to the new machine.

  • Drive Swap Test B: Installed a known-stable system drive into this machine (the one with the specs listed above), and the machine ran perfectly without any freezes.

:thought_balloon: Note: The other known-stable computer used in - Test A - also runs a dedicated NVIDIA GPU (GTX 1050 Ti) with the exact same 580 proprietary driver version under a different desktop environment/distribution, and it never experienced freezes.

Looking forward for any kind of ideas of what could be the root of the cause.

Thanks in advance.

1 Like
Ubuntu 26.04 briefly freezing every so often (again!)
2

Please do not hijack threads and open a new one instead …

1 Like
3

With all due respect, but how am I hijacking a thread when I’ve just confirmed that I’m experiencing the same freezing issue… In my opinion problems that might relate to each other should be kept in one topic for easier read and identification instead of fragmenting them into different threads, but anyways I’ll open a new thread later today then.

4

@silensium Welcome to Ubuntu Discourse :slight_smile:

We prefer users open their own topics.

Even if something might appear to be similar, often it is not.

We want to offer the best possible support from our volunteer users.

Thanks

1 Like
5

You could just refer to the other issue with a link in your post saying that you assume it is similar :slight_smile:

1 Like
6

Looking at your log output there are SATA errors related to your UEFI/BIOS, is your UEFI up to date with the latest version ?

4 Likes
7

Hmm… It seems to me that… the real problem is your drive speed

In your inxi log, the root SSD is connected via USB 2.0 at only 480 Mb/s. When snaps write in the background, disk I/O completely chokes and freezes the whole desktop. That is why the freeze followed your drive in Test A.

Try plugging it into a blue USB 3 port or an internal SATA slot

PS: It’s Saturday today, let Ubuntu have some rest :grinning_face:

3 Likes
8

It makes sense in some contexts but not in many others.

Specifically in this case the root cause is often hardware related. Different rigs will need different approaches and keeping track of those under the same thread is a lot more complicated, dilutes the troubleshooting efforts and confuses each user seeking help.

Case in point: Cf. the previous post. Your case is nothing like the OP’s.

3 Likes
9

Hi there dear team! Thank you for all your answers, sorry for the the delay, I was having a busy day today, I’ll try my best to answer everyone’s input as much as I can :slight_smile:

Thank you for the warm welcome @rubi1200 , and yes agreed totally understandable, thank you very much for moving this into a separate thread :slight_smile:

You’re right @ogra, that was my next plan, and apologies I was just trying to follow the rules (the below quoted one specifically) - thanks for the guideance, appreciate it :slight_smile:

@ogra Thank you for your time, and oh right ofcourse apologies, that was totally on me, I forgot to mention that the SSD was connected normally via SATA-III when these freezes occured (to clarify the attached Sep 4’s log messages in my original post are from SATA-III), I just connected it via USB now to quickly exctract my system infos for the discourse reply. Since yesterday I was testing around this specific SSD over multiple computers that’s why it was detached, and today I was in a hurry IRL (had my saturday’s BBQ with my family) :smiley:

Yes, the UEFI is up to date as much as it can be,- because sometimes it pops up an update available, but I can never install it though due to the UEFI chip (?) being full, those errors been there for many years, never had any issues, I was told ACPI errors can be completely ignored because it’s just something kernel looks for, complains about for a moment of not finding it, and just moves on. :person_shrugging: On a side note, I have this very same acpi errors across almost all my other 6 machines in my household, due to them being a bit uh “ancient” and UEFI / firwamre upgrades not always able to land on them properly, however these sata errors never were something that was related to freeze / crash on other distros.

@steelf Thank you for your reply, see my answer one paragraph above for further clarification :slight_smile:

Thank you for your reply @celticwarrior, fair point, and thank you for your confirmation aswell :slight_smile:

2 Likes
10

Some update since my last reply. Since I noticed apport-autoreports in my journal I decided disabling automatic error reporting, and since doing it, the freezing has stopped (2days, longest streak so far). It’s gonna be odd if it turns out the auto error reporter was the culprit the whole time :person_shrugging: But I’m keeping my eyes open and if something happens I’ll update again.

11

Happened again, this time I finally figured out what was the culprit. Security center’s ask permission (experimental) pop-up - and I know this, because it was about to pop-up to ask permission and then midway suddenly a hard freeze occured.

Now that I finally isolated the root of the cause, I’ve found other folks had the same issue when it was enabled (seems it’s relating to AppArmor aswell):

I hope the ask permission stuff will eventually go out of experimental phase into a stable one, cause it’s a nice thing to have

12

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