[SOLVED] (kinda) Graphics freeze and crashes issues

[trashpanda]

I'm very sorry if the title isn't helpful, I didn't know how to phrase it but hopefully I can provide a better explanation of my problem here.
So, it seems to happen randomly, I didn't find a triggering cause at least, my screen freezes for a couple of seconds, this is followed by everything going black for a couple of seconds and then everything comes back, seemingly normal. I can still hear things and my mic still functions fine, I know this because I was chatting with the boys on mumble a couple of times, however aside from listening and talking the only other thing I can do is move my mouse pointer around. Clicking on things doesn't seem to do anything, same goes with using my keyboard. All I can do is restart, usually I just ctrl+alt+F1 and login there to reboot.

I tried to restart the lightdm service. I tried to stop it and starting it again. It doesn't help much, when I do I can interact with things a little more, if I remember correctly I can move windows around, I can open the menu with all my programs but I can't do things like clicking on tabs on my browser.



I'm on a 64bit version of mint
A full copypaste of my mintreport, because I have no idea which part of this might be useful.

Code: Select all

System:
  Kernel: 5.15.0-73-generic x86_64 bits: 64 compiler: gcc v: 11.3.0 Desktop: Cinnamon 5.6.8
    tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop Mobo: Micro-Star model: X570-A PRO (MS-7C37) v: 3.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: H.J0 date: 02/28/2023
CPU:
  Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 rev: 0 cache: L1: 384 KiB
    L2: 3 MiB L3: 32 MiB
  Speed (MHz): avg: 2942 high: 4205 min/max: 2200/3600 boost: enabled cores: 1: 2100 2: 3698
    3: 4192 4: 3404 5: 4205 6: 2100 7: 2060 8: 3567 9: 2061 10: 3757 11: 2095 12: 2069
    bogomips: 86405
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: Blackmagic Design Intensity Pro 4K driver: blackmagic-io v: 12.4.1a15 pcie:
    speed: 2.5 GT/s lanes: 4 bus-ID: 23:00.0 chip-ID: bdbd:a139
  Device-2: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: Sapphire driver: amdgpu v: kernel
    pcie: speed: 16 GT/s lanes: 16 ports: active: DP-3,HDMI-A-1 empty: DP-1,DP-2 bus-ID: 2f:00.0
    chip-ID: 1002:73ff
  Device-3: Microdia HDP Webcam USB type: USB driver: snd-usb-audio,uvcvideo bus-ID: 5-1.1:4
    chip-ID: 0c45:636b
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96
  Monitor-1: DisplayPort-2 mapped: DP-3 pos: primary,left model: HP 27es res: 1920x1080 dpi: 82
    diag: 686mm (27")
  Monitor-2: HDMI-A-0 mapped: HDMI-A-1 pos: right model: Samsung S24F350 res: 1920x1080 dpi: 94
    diag: 598mm (23.5")
  OpenGL: renderer: AMD Radeon RX 6600 (navi23 LLVM 15.0.7 DRM 3.42 5.15.0-73-generic)
    v: 4.6 Mesa 22.2.5 direct render: Yes
Audio:
  Device-1: Blackmagic Design Intensity Pro 4K driver: blackmagic-io v: 12.4.1a15 pcie:
    speed: 2.5 GT/s lanes: 4 bus-ID: 23:00.0 chip-ID: bdbd:a139
  Device-2: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT] driver: snd_hda_intel
    v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 2f:00.1 chip-ID: 1002:ab28
  Device-3: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI X570-A PRO
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 31:00.4
    chip-ID: 1022:1487
  Device-4: Microdia HDP Webcam USB type: USB driver: snd-usb-audio,uvcvideo bus-ID: 5-1.1:4
    chip-ID: 0c45:636b
  Device-5: JMTek LLC. USB PnP Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus-ID: 5-1.2.2:7 chip-ID: 0c76:161e
  Sound Server-1: ALSA v: k5.15.0-73-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: r8169 v: kernel pcie: speed: 5 GT/s lanes: 1 port: e000
    bus-ID: 25:00.0 chip-ID: 10ec:8125
  IF: enp37s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI X570-A PRO driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: c000 bus-ID: 27:00.0 chip-ID: 10ec:8168
  IF: enp39s0 state: down mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  IF-ID-2: virbr1 state: down mac: <filter>
  IF-ID-3: virbr2 state: down mac: <filter>
  IF-ID-4: wg-mullvad state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
    bus-ID: 1-2:2 chip-ID: 0a12:0001
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
    sub-v: 22bb
Drives:
  Local Storage: total: 5 TiB used: 2.37 TiB (47.3%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN770 1TB size: 931.51 GiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 37.9 C
  ID-2: /dev/sda model: SATA3 2TB SSD size: 1.82 TiB speed: 6.0 Gb/s serial: <filter>
  ID-3: /dev/sdb vendor: Samsung model: SSD 860 QVO 2TB size: 1.82 TiB speed: 6.0 Gb/s
    serial: <filter>
  ID-4: /dev/sdc vendor: SanDisk model: SDSSDH3 500G size: 465.76 GiB speed: 6.0 Gb/s
    serial: <filter>
Partition:
  ID-1: / size: 931 GiB used: 131.04 GiB (14.1%) fs: xfs dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 63 MiB used: 6 MiB (9.6%) fs: vfat dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002
  Device-1: 1-2:2 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: Bluetooth
    driver: btusb rev: 2.0 speed: 12 Mb/s chip-ID: 0a12:0001
  Hub-2: 2-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002
  Device-1: 3-5:2 info: Micro Star MYSTIC LIGHT type: HID driver: hid-generic,usbhid rev: 1.1
    speed: 12 Mb/s chip-ID: 1462:7c37
  Hub-4: 3-6:3 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip-ID: 05e3:0608
  Hub-5: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
  Hub-6: 5-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002
  Hub-7: 5-1:2 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip-ID: 05e3:0608
  Device-1: 5-1.1:4 info: Microdia HDP Webcam USB type: Video,Audio
    driver: snd-usb-audio,uvcvideo rev: 2.0 speed: 480 Mb/s chip-ID: 0c45:636b
  Hub-8: 5-1.2:6 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip-ID: 05e3:0608
  Device-1: 5-1.2.2:7 info: JMTek LLC. USB PnP Audio Device type: Audio,HID
    driver: hid-generic,snd-usb-audio,usbhid rev: 1.1 speed: 12 Mb/s chip-ID: 0c76:161e
  Hub-9: 5-1.2.3:8 info: Huasheng USB2.0 HUB ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 214b:7250
  Hub-10: 5-1.2.3.1:9 info: Huasheng USB2.0 HUB ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 214b:7250
  Device-1: 5-2:11 info: Google Nexus/Pixel Device (MTP) type: Still Imaging driver: usbfs
    rev: 2.1 speed: 480 Mb/s chip-ID: 18d1:4ee1
  Device-2: 5-3:3 info: Razer USA Naga Left Handed Edition type: Mouse,Keyboard
    driver: razermouse,usbhid rev: 2.0 speed: 12 Mb/s chip-ID: 1532:008d
  Device-3: 5-4:5 info: USB HID GMMK V2 96 type: Keyboard,Mouse driver: hid-generic,usbhid
    rev: 2.0 speed: 12 Mb/s chip-ID: 320f:505a
  Hub-11: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 41.0 C mem: 42.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
  Packages: 3519 note: see --pkg apt: 3492 flatpak: 27
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/aslatter-ppa-jammy.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/aslatter-ppa-jammy.gpg] https: //ppa.launchpadcontent.net/aslatter/ppa/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https: //brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/nicotine-team-stable-jammy.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/nicotine-team-stable-jammy.gpg] https: //ppa.launchpadcontent.net/nicotine-team/stable/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https: //mirror.init7.net/linuxmint vera main upstream import backport
    2: deb http: //mirror.freethought-internet.co.uk/ubuntu jammy main restricted universe multiverse
    3: deb http: //mirror.freethought-internet.co.uk/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //mirror.freethought-internet.co.uk/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
  Processes: 386 Uptime: 20m Memory: 31.27 GiB used: 3.54 GiB (11.3%) Init: systemd v: 249
  runlevel: 5 Compilers: gcc: 11.3.0 alt: 11/12 Client: Unknown python3.10 client inxi: 3.3.13

The only error I could see was upon pressing CTRL+ALT+F1, it showed right after the login prompt:

Code: Select all

[ 7329.657508] [drm:amdgpu_cs_ioctl [amdgpu] ] *ERROR* Failed to initialize parser -125!

I hope I managed to provide all the info I could, I will also include a copypasta of my neofetch, just to provide a smaller amount of info:

Code: Select all

⠀⠀⠀⠀⠀⠀⠀⠀⣀⣠⣤⣀⣀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣀⣤⣤⣴⣦⡀⠀⠀⠀⠀⠀⠀⠀⠀   ╭──────────── Software ────────────
⠀⠀⠀⠀⠀⠀⠀⠀⣿⣿⣿⣿⣿⣿⣶⣤⡀⠀⠀⣀⣠⣤⣤⣶⣶⣶⣶⣶⣶⣤⣤⣀⢀⣠⣶⣿⣿⣿⣿⣿⣿⠇⠀⠀⠀⠀⠀⠀⠀⠀   │ OS› Linuxmint
⠀⠀⠀⠀⠀⠀⠀⠀⢻⣿⣿⣿⣿⣿⣿⣿⣿⣾⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀   │ Kernel› 5.15.0-73-generic
⠀⠀⠀⠀⠀⠀⠀⠀⠘⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠏⠀⠀⠀⠀⠀⠀⠀⠀⠀   │ Packages› 3492 (dpkg), 27 (flatpak)
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠙⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠏⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀   │ Shell› bash 5.1.16
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣯⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀   │ DE› Cinnamon 5.6.8
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣼⣿⣿⣿⣿⣿⡿⠿⠛⠉⠉⠀⠙⢿⣿⣿⣿⠋⠁⠉⠉⠛⠻⢿⣿⣿⣿⣿⣷⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀   │ Terminal› alacritty
⠀⠀⠀⠀⠀⠀⠀⠀⠀⣸⣿⣿⣿⡿⠛⠁⠀⠀⠀⢀⣀⠀⠀⢸⣿⣿⡇⠀⠀⣀⣀⠀⠀⠀⠈⠙⢿⣿⣿⣷⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀   │ Local IP› 10.136.193.129
⠀⠀⠀⠀⠀⠀⠀⠀⢠⣿⣿⠟⠉⠀⠀⠀⠀⣠⣶⣿⣿⣿⡄⢸⣿⣿⡇⠀⣾⣿⣿⣷⣄⡀⠀⠀⠀⠈⠻⣿⣧⠀⠀⠀⠀⠀⠀⠀⠀⠀   ├──────────── Hardware ────────────
⠀⠀⠀⠀⠀⠀⠀⠀⣸⣿⠋⠀⠀⠀⠀⣠⣾⣿⣿⣿⣿⣿⡇⢸⣿⣿⡇⢸⣿⣿⣿⣿⣿⣿⣦⠀⠀⠀⠀⠙⣿⡆⠀⠀⠀⠀⠀⠀⠀⠀   │ Host› MS-7C37 3.0
⠀⠀⠀⠀⠀⠀⠀⠀⣿⠃⠀⠀⠀⠀⣼⣿⣿⣿⣿⣿⣿⣿⠃⢸⣿⣿⡇⠈⢿⣿⣿⣿⣿⣿⣿⣷⡀⠀⠀⠀⠘⣿⠀⠀⠀⠀⠀⠀⠀⠀   │ CPU› AMD Ryzen 5 3600 (12) @ 3.600GHz
⠀⠀⠀⢀⣀⠀⠀⠀⠇⠀⠀⠀⠀⢰⣿⣿⣿⣿⣿⣿⠟⠁⠀⢸⣿⣿⡇⠀⠀⠙⣿⣿⣿⣿⣿⣿⣇⠀⠀⠀⠀⠸⠀⠀⢀⣀⠀⠀⠀⠀   │ GPU› AMD ATI Radeon RX 6600/6600 XT/6600M
⠀⢰⣿⣿⣿⣿⣿⣿⣿⣷⣶⡆⠀⢸⣿⣿⣿⣿⣿⠇⠀⠀⠀⣸⣿⣿⣧⠀⠀⠀⠈⣿⣿⣿⣿⣿⡟⠀⣴⣶⣾⣿⣿⣿⣿⣿⣿⣿⡄⠀   │ Memory› 3179MiB / 32020MiB
⠀⠘⣿⢿⣿⡿⢹⣿⠏⢿⠿⠃⠀⠀⠀⠀⠉⠉⠙⠀⠀⠀⠀⣿⣿⣿⣿⠇⠀⠀⠀⠉⠉⠉⠉⠉⠁⠀⠘⢿⡟⢻⣿⡟⢿⣿⣿⡿⠃⠀   │ Disk (/)› 132G / 931G (15%)
⠀⠀⠈⠘⠛⠀⠈⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⠙⠛⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠉⠀⠈⠛⠁⠁⠀⠀   ├───────────── Uptime ─────────────
                                                                                                                                       │› 19 mins
                                                                ╰──────────────────────────────────

[SMG]

Graphics:
Device-1: Blackmagic Design Intensity Pro 4K driver: blackmagic-io v: 12.4.1a15 pcie:
speed: 2.5 GT/s lanes: 4 bus-ID: 23:00.0 chip-ID: bdbd:a139
Device-2: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: Sapphire driver: amdgpu v: kernel
pcie: speed: 16 GT/s lanes: 16 ports: active: DP-3,HDMI-A-1 empty: DP-1,DP-2 bus-ID: 2f:00.0
chip-ID: 1002:73ff

Pleases try the 6.1-oem kernel. Lots of people with this GPU have run into issues. Sometimes both a newer kernel and a different cable connection to the monitor is needed.

You can install the latest 6.1-oem kernel with

Code: Select all

sudo apt-get install linux-oem-22.04c

and reboot.

[trashpanda]

Hi, it wasn't that sadly, I've been using 6.1 for a couple of days now. On top of that newer kernels are not allowing me to use the capture card you see in the part you quoted under device 1.
I started to think my issue is the MOBO.

EDIT: Just to be more specific, it's an old girl, maybe it's starting to malfunction.

[SMG]

I tried to restart the lightdm service. I tried to stop it and starting it again. It doesn't help much

If there is an issue with the graphics drivers, one restarts X Server and not lightdm.

I have seen in logs where the AMD GPU tries to reset itself. If it fails, it ends up in a state which sounds similar to what you have described. However, there are usually a lot more errors than just what you posted. If you want to ry restarting X Server, you can use Ctl-Atl-Backspace (if you have not remapped that to something else).

On top of that newer kernels are not allowing me to use the capture card you see in the part you quoted under device 1.

Because I am not familiar with the capture card, I do not know why you would want it to be Device-1. That may be appropriate; I'm just not familiar with it to know. I presume it is coming up as Device 1 because of settings in the UEFI.

Is the driver for it loading with the newer kernel? I did a search and found others on the BlackMagic forum having an issue Linux Kernel 6.1 & Desktop Video 12.4.1. I see someone in the topic saying they got the fix to work on Pop_OS 22.04 which is encouraging news. (I suggest reading through the entire topic before trying anything.)

[trashpanda]

I tried to restart the lightdm service. I tried to stop it and starting it again. It doesn't help much

If there is an issue with the graphics drivers, one restarts X Server and not lightdm.

I have seen in logs where the AMD GPU tries to reset itself. If it fails, it ends up in a state which sounds similar to what you have described. However, there are usually a lot more errors than just what you posted. If you want to ry restarting X Server, you can use Ctl-Atl-Backspace (if you have not remapped that to something else).

On top of that newer kernels are not allowing me to use the capture card you see in the part you quoted under device 1.

Because I am not familiar with the capture card, I do not know why you would want it to be Device-1. That may be appropriate; I'm just not familiar with it to know. I presume it is coming up as Device 1 because of settings in the UEFI.

Is the driver for it loading with the newer kernel? I did a search and found others on the BlackMagic forum having an issue Linux Kernel 6.1 & Desktop Video 12.4.1. I see someone in the topic saying they got the fix to work on Pop_OS 22.04 which is encouraging news. (I suggest reading through the entire topic before trying anything.)

Thank you very much to take time to reply again.
It is now time to go to bed, I assume we live in very different timezones, and I will check out the thread you linked tomorrow.
However I wanted to leave a reply about this part of your post:

Because I am not familiar with the capture card, I do not know why you would want it to be Device-1.

It's not that I want it there, it's just how it defaulted itself.
I'm very ignorant but could it be that it shows up in the first position because the GPU reset itself, leaving position 1 free, capture card took over?
I dunno, but if you think it should be in any other position I'm happy to learn why After all a good chunk of why I like using linux is that I get to learn stuff.

[SMG]

Because I am not familiar with the capture card, I do not know why you would want it to be Device-1.

It's not that I want it there, it's just how it defaulted itself.
I'm very ignorant but could it be that it shows up in the first position because the GPU reset itself, leaving position 1 free, capture card took over?
I dunno, but if you think it should be in any other position I'm happy to learn why After all a good chunk of why I like using linux is that I get to learn stuff.

In desktops with more than one option for a GPU, it is usually a function of the hardware as to which device is seen as Device 1 and which one is Device 2. I presume it is due to their locations and how the UEFI interprets those locations.

You might be able to find information on the Blackmagic forum as to whether which PCIe port is used makes a difference to the graphics driver stability.

[trashpanda]

Thanks for the links SMG, I managed to get the capture card drivers to work, it was very satisfying and I'm happy to say I might have learned something. Definitely won't be able to solve things like that on my own but I did learn a couple small things during the process.

[SMG]

Thanks for the links SMG, I managed to get the capture card drivers to work

Good to hear. If your issue is resolved, please go to your first post in this topic, click the pencil icon, and add [SOLVED] to the beginning of the title so others know you are no longer seeking help on this issue. You have a long title so you may need to trim some letters from the existing title to get [SOLVED] to fit.

[trashpanda]

I wouldn't say it's solved as I still freeze and crash, but since I suspect my mobo might be broken I'll mark it as so.

[SMG]

I wouldn't say it's solved as I still freeze and crash, but since I suspect my mobo might be broken I'll mark it as so.

Even with the newer kernel? We can continue investigating the issue. While the motherboard isn't brand new, I would not consider it to be "old".

Was there any change at all with the newer amdgpu graphics driver? Is it freezing less often?

We can start checking logs after the problem happens to see if there are clues. We would want to look at messages which happen right before the freeze.

Code: Select all

journalctl -rb -1 | nc termbin.com 9999

It will return with a url address that you should post in your next reply.

That command prints the journal log information of the prior boot cycle in reverse order (so the reason for the freeze should be near the top) and sends it to termbin.

[trashpanda]

Thanks again SMG, here's the link that I got
https://termbin.com/j6aj

A little more info about why I think it's the mobo rather than the GPU.
I had another GPU before. I was having other issues, not the same, but still issues.
At first I thought it was a power supply issue, then I thought it was the GPU.
Both times I replaced the part I assumed was at fault which in hindsight was silly, I could've saved a bunch of money.
Still, the issues remained even if they were not the exact same issues as before. I was also on a different distro.
As of now the issue I'm experiencing is the least annoying. Before this I had hard crashes, or even the computer shutting itself down, which is why I thought the PSU was to blame.

[SMG]

Before this I had hard crashes, or even the computer shutting itself down, which is why I thought the PSU was to blame.

That would be my first guess to an issue like that, so I don't think changing the PSU was silly.

I suggest cleaning up the /etc/hosts file. That's a lot of messages about errors cluttering the log.

I also noticed a lot of error related to "Timed out waiting for device /dev/disk/UUID" for multiple different devices. The next line says the dependency failed. I don't know if that's because you at one time had other devices/drives or there is something not working properly with your current connections. Those start around 20:19:10 in the log.

I just went back to your inxi to check the drives and I'm not sure that any of those are the ones mentioned in the log, but I just now noticed you are using xfs instead of ext4. I am not familiar with it to know what impact (if any) it might have.

I see mention of the Cinnamon logout sound so this does not appear to be a session which crashed on you. It's a normal shutdown.I read your earlier comment and though you were Alt-Ctl-F1 and logging in to reboot. If you are doing something different when the problem happens, likely we would need to check a different journalctl.

[trashpanda]

I suggest cleaning up the /etc/hosts file. That's a lot of messages about errors cluttering the log.

Do I just empty the file to do that?

As for the errors timed out thing, it might be when the capture cards drivers didn't work, it's the only thing that comes to mind.
Or it might be searching for the external hard drive I backup my stuff onto.

[SMG]

I suggest cleaning up the /etc/hosts file. That's a lot of messages about errors cluttering the log.

Do I just empty the file to do that?

I do not know your setup to know your needs. I am running LM20.3 and below is what my file contains. I am guessing yours is a lot longer.

Code: Select all

 cat /etc/hosts
127.0.0.1	localhost
127.0.1.1	SMG-HP-6360t

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

As for the errors timed out thing, it might be when the capture cards drivers didn't work, it's the only thing that comes to mind.
Or it might be searching for the external hard drive I backup my stuff onto.

There were UUIDs in the lines which would usually be some type of drive. However, it's my understanding the system would only be automatically looking for those drives if you have fstab set up to include them. Usually one only includes drives in fstab which are drives always attached to your computer.

[laszlopalya]

I tried all the solutions on numerous forums and nothing worked until I found this one.
Go into the BIOS and lock the CPU frequency.
For 3 weeks I had no freeze.
Enjoy...

[trashpanda]

I do not know your setup to know your needs. I am running LM20.3 and below is what my file contains. I am guessing yours is a lot longer.

I may have phrased the question poorly sorry, you told me to clean up /etc/hosts
My question here is, to clean /etc/hosts should I just empty the file?

I tried all the solutions on numerous forums and nothing worked until I found this one.
Go into the BIOS and lock the CPU frequency.
For 3 weeks I had no freeze.
Enjoy...

I'll try it. It's gonna be very frustrating if that solves the issue when the motherboard is gonna be here in a few days.
I don't think so though since I had this mobo for years and this issue is brand new.

[SMG]

I do not know your setup to know your needs. I am running LM20.3 and below is what my file contains. I am guessing yours is a lot longer.

I may have phrased the question poorly sorry, you told me to clean up /etc/hosts
My question here is, to clean /etc/hosts should I just empty the file?

I do not normally touch that file. You may have needed to do something to it in the past? If so, then I would think clearing out the lines which are throwing the errors (check the log to see which ones they are), would be what you want to do.