Zorin OS freezes after Suspend (Possible Bluetooth Issue)

codesniper · 9 February 2025 17:06

System Info:

Zorin OS Version: 17.2
Kernel Version: 6.8.0-52-generic
Hardware:

System:
  Host: obscura Kernel: 6.8.0-52-generic x86_64 bits: 64 Desktop: GNOME 43.9
    Distro: Zorin OS 17.2
Machine:
  Type: Laptop System: LENOVO product: 20EQS0TR01 v: ThinkPad P50
    serial: <superuser required>
  Mobo: LENOVO model: 20EQS0TR01 serial: <superuser required> UEFI: LENOVO
    v: N1EETA2W (1.75 ) date: 03/18/2024
Battery:
  ID-1: BAT0 charge: 23.1 Wh (40.8%) condition: 56.6/66.0 Wh (85.7%)
CPU:
  Info: quad core Intel Core i7-6820HQ [MT MCP] speed (MHz): avg: 862
    min/max: 800/3600
Graphics:
  Device-1: Intel HD Graphics 530 driver: i915 v: kernel
  Device-2: NVIDIA GM107GLM [Quadro M1000M] driver: nvidia v: 550.120
  Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1
    compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 530 (SKL GT2)
    v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.3
Network:
  Device-1: Intel Ethernet I219-LM driver: e1000e
  Device-2: Intel Wireless 8260 driver: iwlwifi
  Device-3: Intel Bluetooth wireless interface type: USB driver: btusb
Drives:
  Local Storage: total: 931.51 GiB used: 849.51 GiB (91.2%)
Info:
  Processes: 316 Uptime: 16m Memory: 15.45 GiB used: 4.25 GiB (27.5%)
  Shell: Bash inxi: 3.3.13

My system freezes after waking up from suspend. Based on my logs, it seems related to Bluetooth. I tried:

Disabling Bluetooth before suspend (systemctl stop bluetooth)
Reloading the Bluetooth module (modprobe -r btusb && modprobe btusb)
Checking for updates (sudo apt update && sudo apt upgrade)
Looking for logs, but some messages disappear too fast at suspend.

The issue persists since about 24hrs. I installed some (ollama and some from npm repos) apps over the night, but I did not temper with the kernel or OS, to my knowledge.

What else can I try?

Thanks for any help!

Ponce-De-Leon · 9 February 2025 18:21

You could try switching to X11. Go to the Login Screen (simply reboot for that) and click on Your Profile so that the Password Field appears. It has to be appeared. When it is appeared, You should see a Gear Icon in the bottom right Corner. Click on it and choose the Option ''Zorin Desktop on Xorg'' and then log in and test it.

codesniper · 9 February 2025 18:42

Nada.

Thank you for the response. I switched to xorg and suspended and woke up twice with the same result: boot freezes at the same point.

Michel · 9 February 2025 19:06

It’s your nvidia card, see your screenshot.

Try a newer driver 565 or 570.

codesniper · 9 February 2025 19:37

$ nvidia-smi
Sun Feb  9 20:27:07 2025       
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.120                Driver Version: 550.120        CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| 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  Quadro M1000M                  Off |   00000000:01:00.0 Off |                  N/A |
| N/A   30C    P8             N/A /  200W |       9MiB /   2048MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
                                                                                         
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A      1268      G   /usr/lib/xorg/Xorg                              2MiB |
+-----------------------------------------------------------------------------------------+

the repository does not offered any major release

$ sudo add-apt-repository ppa:graphics-drivers/ppa
PPA publishes dbgsym, you may need to include 'main/debug' component
Repository: 'deb https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu/ jammy main'
Description:
Fresh drivers from upstream, currently shipping Nvidia.

## Current releases

Current production branch release: 550.107.02
Current new feature branch release: 555.58.02
Current beta release: 560.28.03

only

ubuntu-drivers devices

showed new and I installed

sudo apt install nvidia-driver-570

Rebooted and testing.

codesniper · 9 February 2025 19:45

No change in behaviour after starting from suspend. The log stops after BT messages.

$ nvidia-smi
Sun Feb  9 20:43:49 2025       
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 570.86.16              Driver Version: 570.86.16      CUDA Version: 12.8     |
|-----------------------------------------+------------------------+----------------------+
| 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  Quadro M1000M                  Off |   00000000:01:00.0 Off |                  N/A |
| N/A   40C    P8             N/A /  200W |       7MiB /   2048MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
                                                                                         
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI              PID   Type   Process name                        GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A            1372      G   /usr/bin/gnome-shell                      0MiB |
+-----------------------------------------------------------------------------------------+

Michel · 9 February 2025 21:30

Did you check if there is a firmware available for your Bluetooth device ?

codesniper · 9 February 2025 21:51

$ sudo dmesg | grep -i bluetooth | grep -i firmware
[    5.326076] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    5.335107] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[    6.933174] Bluetooth: hci0: Waiting for firmware download to complete
[    6.933191] Bluetooth: hci0: Firmware loaded in 1560624 usecs
[    6.951272] Bluetooth: hci0: Firmware revision 0.0 build 14 week 44 2021

$ sudo apt update && sudo apt install --reinstall linux-firmware

rebooting and testing

Nope. No change. The BT is still on

[    5.414926] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi

StarTreker · 10 February 2025 03:34

I've got the same issue, and I have reported this on the forum as well. I don't think suspend works well on Linux. If I let my system suspend, it will then freeze the system, and nothing I can do, will get my system to return, short of a forced shutoff, and startup.

I decided to choose a different approach, which has worked for me. It won't be what you want, but it will be better then nothing at all.

First and for-most, click logo bottom of screen, and then click on "Power." Set "Blank Screen" to never. Set "automatic suspend" to "when on battery power." You may want to set the "power button behavior" to "power" off for convenience as well.

Now run the following commands from my post here, to make sure Gnome power services are disabled, and to install XScreenSavers...

Once you have done that, don't forget reboot your computer.

Then launch xscreensaver from your app list, and set your time to blank into the screensaver. Since getting a new monitor, I have set that lower to 30-minutes now. Keep the cycle minutes to 0, unless you want the app to cycle screensavers.

I prefer to manually choose a screensaver and keep it on the one I like, which is Flurry in the list. Make sure to put a checkmark in "Lock screen after" box. Best to set that to 1 minute after screensaver comes on, that gives you time to move the mouse, if you are still at your computer watching a movie, without needing to re-enter your password. But will still secure your system if you are not around.

So why is this a good alternative you ask? Because screensavers do what they were invented to do, save your screen from burn in. But it doesn't fully suspend or hibernate the system in order to do so, and that is why I like it. Plus screensavers always look cool on screen too.

If you want, double check your "Advanced" options, make sure that display power management is not enabled. I was testing it at the time I took the screenshot. Then when my system froze, I was reminded why I didn't use power management features on my notebook, cause its terrible. Don't enable the box!

Ponce-De-Leon · 10 February 2025 10:51

Did You take a Look in the ''Additional Drivers'' Tab in Software & Updates if there are beneath Your Nvidia Driver any others offered?

codesniper · 10 February 2025 19:39

Only the one I updated already:

codesniper · 10 February 2025 19:44

Thank you, StarTreker. But I cannot let my laptop running all night or so, it is not efficient and safe. I somehow made my laptop recognize lid closure earlier and I will figure it out to change it to shutdown instead.

Ponce-De-Leon · 10 February 2025 19:59

And when You scroll down, there are only Nvidia Drivers, yes?

codesniper · 10 February 2025 20:46

Yes, only those.

codesniper · 10 February 2025 21:11

The issue is connected to the nvidia services/settings or whatever. It helped to disable the nvidia services:

sudo systemctl disable nvidia-suspend.service
sudo systemctl disable nvidia-resume.service
sudo systemctl disable nvidia-hibernate.service
sudo systemctl mask nvidia-suspend.service
sudo systemctl mask nvidia-resume.service
sudo systemctl mask nvidia-hibernate.service
sudo reboot

Apparently, when I installed and run my first ollama model, it changed the nvidia/CUDA card services. After disabling the above services, I still can ollama run mistral, and use the suspend feature of the laptop. Thank you everybody for the input and sharing knowledge!