Solus freezes completely

alexanderzhirov

I've been seeing problems with Solus for the last week. I don't know what this might be related to. Either with a kernel update, or with something else. When working, I catch a dead frieze that does not respond even to switching Ctrl+Alt+F*. Only a cold reboot helps.

System:
  Host: solus Kernel: 6.11.7-308.current arch: x86_64 bits: 64
  Desktop: Xfce v: 4.18.1 Distro: Solus 4.6 convergence
Machine:
  Type: Desktop Mobo: Gigabyte model: Z77-DS3H v: x.x serial: N/A
    UEFI: American Megatrends v: F9 date: 09/19/2012
CPU:
  Info: quad core Intel Core i7-3770 [MT MCP] speed (MHz): avg: 1600
    min/max: 1600/3900
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nvidia v: 560.35.03
  Device-2: Logitech Webcam C310 driver: snd-usb-audio,uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4 driver:
    gpu: nvidia,nvidia-nvswitch resolution: 1: 3440x1440~100Hz 2: 1440x900~60Hz
    3: 1080x2560~60Hz
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 560.35.03
    renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
Network:
  Device-1: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet driver: atl1c
Drives:
  Local Storage: total: 3.88 TiB used: 731.38 GiB (18.4%)
Info:
  Memory: total: 32 GiB available: 31.3 GiB used: 3.36 GiB (10.7%)
  Processes: 265 Uptime: 42m Shell: Bash inxi: 3.3.36

This is what the last logs of journalctl look like before everything freezes:

ноя 16 13:09:15 solus kernel: audit: type=1131 audit(1731751755.164:240): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib64/systemd/systemd" hostname=? addr=? terminal=? res=success'
ноя 16 13:12:13 solus kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
ноя 16 13:12:13 solus kernel: CPU: 5 UID: 0 PID: 0 Comm: swapper/5 Tainted: P           O       6.11.7-308.current #1
ноя 16 13:12:13 solus kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
ноя 16 13:12:13 solus kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z77-DS3H, BIOS F9 09/19/2012
ноя 16 13:12:13 solus kernel: Call Trace:
ноя 16 13:12:13 solus kernel:  <IRQ>
ноя 16 13:12:13 solus kernel:  dump_stack_lvl+0x57/0x80
ноя 16 13:12:13 solus kernel:  __report_bad_irq+0x35/0xaa
ноя 16 13:12:13 solus kernel:  note_interrupt.cold+0xa/0x65
ноя 16 13:12:13 solus kernel:  handle_irq_event+0x71/0x80
ноя 16 13:12:13 solus kernel:  handle_fasteoi_irq+0x9b/0x240
ноя 16 13:12:13 solus kernel:  __common_interrupt+0x68/0xf0
ноя 16 13:12:13 solus kernel:  common_interrupt+0xb3/0xd0
ноя 16 13:12:13 solus kernel:  </IRQ>
ноя 16 13:12:13 solus kernel:  <TASK>
ноя 16 13:12:13 solus kernel:  asm_common_interrupt+0x22/0x40
ноя 16 13:12:13 solus kernel: RIP: 0010:cpuidle_enter_state+0xc6/0x420
ноя 16 13:12:13 solus kernel: Code: a0 5f 2a ff e8 bb 3f 1c ff e8 d6 ee ff ff 49 89 c5 0f 1f 44 00 00 31 ff e8 77 14 1b ff 45 84 ff 0f 85 a5 01 00 00 fb 45 85 f6 <0f> 88 84 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d 0c c4 48
ноя 16 13:12:13 solus kernel: RSP: 0018:ffffc900000efe68 EFLAGS: 00000202
ноя 16 13:12:13 solus kernel: RAX: ffff8887fed40000 RBX: 0000000000000004 RCX: 0000000000000000
ноя 16 13:12:13 solus kernel: RDX: 00000233787cc593 RSI: ffffffff82724eaf RDI: ffffffff82728ece
ноя 16 13:12:13 solus kernel: RBP: ffff8887fed78bf0 R08: 0000000000000002 R09: 0000000000000001
ноя 16 13:12:13 solus kernel: R10: 0000000000000008 R11: ffff8887fed6e824 R12: ffffffff8321cae0
ноя 16 13:12:13 solus kernel: R13: 00000233787cc593 R14: 0000000000000004 R15: 0000000000000000
ноя 16 13:12:13 solus kernel:  ? cpuidle_enter_state+0xb9/0x420
ноя 16 13:12:13 solus kernel:  cpuidle_enter+0x29/0x40
ноя 16 13:12:13 solus kernel:  cpuidle_idle_call+0xfb/0x160
ноя 16 13:12:13 solus kernel:  do_idle+0x78/0xb0
ноя 16 13:12:13 solus kernel:  cpu_startup_entry+0x25/0x30
ноя 16 13:12:13 solus kernel:  start_secondary+0x111/0x130
ноя 16 13:12:13 solus kernel:  common_startup_64+0x13e/0x148
ноя 16 13:12:13 solus kernel:  </TASK>
ноя 16 13:12:13 solus kernel: handlers:
ноя 16 13:12:13 solus kernel: [<00000000452df09c>] usb_hcd_irq [usbcore]
ноя 16 13:12:13 solus kernel: Disabling IRQ #16
ноя 16 13:12:13 solus kernel: NVRM: GPU at PCI:0000:01:00: GPU-cc4bbdf6-3792-99c0-7e24-e64378486fb9
ноя 16 13:12:14 solus kernel: NVRM: Xid (PCI:0000:01:00): 79, pid='<unknown>', name=<unknown>, GPU has fallen off the bus.
ноя 16 13:12:14 solus kernel: NVRM: GPU 0000:01:00.0: GPU has fallen off the bus.
ноя 16 13:12:14 solus kernel: NVRM: A GPU crash dump has been created. If possible, please run
                                 NVRM: nvidia-bug-report.sh as root to collect this data before
                                 NVRM: the NVIDIA kernel module is unloaded.

alexanderzhirov

Has anyone had a similar experience?
Maybe it's worth rolling back to the previous core?

alexanderzhirov

Some forums say that the problem may be related to the operation of the graphics card. Either the problem is with the graphics card drivers.

Axios

alexanderzhirov Ya from your post looks like either driver or Gpu issue
I dont run any gpu cards so not much help but thats what it appears to me from your post.

alexanderzhirov

Based on the update history, most likely this could have affected the work, as I have been experiencing problems for the last week.

Axios

alexanderzhirov There always seems be some Nvidia or graphics issues floating
around forum.
Somebody in the know prob comment later.
Tell you the truth never had to roll anything back to get something to work.
Thats prob best place to start.

Staudey

alexanderzhirov As you can see from the versions that's not a version upgrade, but simply a rebuild for the new kernel. It's unlikely that problems were introduced that way. More likely that it's an issue with one of the other updates (kernel, xorg-server, etc.)

brent

"no one cared" is an odd message in the output🙂.

Axios There always seems be some Nvidia or graphics issues floating
around forum.

there are some new ones I've noticed as well around the 5XX series...

BuzzPCSOS If you still get the same issues then it is more likely not update related.
It is always worth a quick look around to make sure that you are getting good cooling, fans all working, airways not clogged, heatsinks clear of dust etc.
Sorry if this all sounds a bit basic but it is always best to start with the easy fixes that everyone forgets.

I concur wit both these gentlemen this is hardware error without doubt.

2 CENTS:
1) switching to the Nouveua drivers to confirm likely a waste of time.

2) I personally am 1 of 5 in successful rollbacks but it can be done.

see what the team has cooking in devtracker, maybe a patch is coming

BuzzPCSOS

Just to prove the hardware it would be a good idea to try running the Live environment directly from your Solus install media. If you still get the same issues then it is more likely not update related.
It is always worth a quick look around to make sure that you are getting good cooling, fans all working, airways not clogged, heatsinks clear of dust etc.
Sorry if this all sounds a bit basic but it is always best to start with the easy fixes that everyone forgets.

SilverBird775

The most horrible deadlocks are indeed a gpu lockups. Unfortunately, there is no ready solutions for them on the user side, and it may take a painful statistic analysis on the last actions before a lockup. This terrible summer, my main system was tormented by random gpu lockups with googling it led to unfixed "ring timeouts" issues. The GPU's logs of taking it's last breath are not fun nor helpful at all.

In my experience, the deadly combo of Plasma adaptive sync and their frame buffering experiments and MESA GL threading experiments has failed on my system (amdgpu). The lockups completely gone after setting "MESA_GLTHREAD=single" system wide and disabling the "adaptive sync" for a desktop.

zmaint

Have a browser open? I've had Brave from the repo cause random hard locks off and on over several years, including recently. Different machines, different GPU's, def different drivers.. but it's always Brave open with Youtube. Usually the next Brave update will fix it for a while, but it seems to always come back. Sometimes REISUB will reset, sometimes I have to hold the old power button down. I also use Chromium (flatpak) and have never had a Youtube lock up.

TraceyC

The best thing to do at this point is to get a backtrace of the system crash that happened. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? (Or you can post it to a pastebin service). Thanks.