Freezing on every Distro (Need help)

L

LavaGrenade

New Member
Joined
Jun 25, 2023
Messages
3
Reaction score
2
Credits
39
Hi, I am a generally new Linux user. I have been using various distros for around the past year and on every one I have the same issue. My whole system will randomly freeze with no way to interact at all. I have to hold the power button down and force shut down the system to restart it. This has occurred on various distros (Endeavor, Manjaro, Ubuntu, Fedora, etc). I really want to get Linux working on my machine but I am at a loss as for how to do so. Any help would be much appreciated. Right now I'm running Ubuntu with the Gnome DE (Ubuntu 22.04.2 LTS).
My system hardware is as listed:
Motherboard: MSI MS-7977
CPU: Intel core i7-6700k (not overclocked)
GPU: Nvidia GP106 (GeForce GTX 1060 6GB)
I have 3 drives, 1 ssd (500gb boot) and 2 hdd's
I also have a wifi card installed but am using ethernet
 


LavaGrenade said:
Right now I'm running Ubuntu with the Gnome DE (Ubuntu 22.04.2 LTS).
Click to expand...
Welcome to the forums, MSI can throw up a range of problems
open a terminal and enter, inxi -Fnxz, copy and paste back the results, so we can check the components and drivers, another thing you could try is disable hardware acceleration
 
Last edited:
Nvidia usually ends up being the problem - make sure you have the correct driver installed
 
Is this happening while you have a browser open?

Also, you can use REISUB to reboot more cleanly (probably, unless it's too frozen).

linux-tips.us

What You Need To Know About Linux's Magic SysRq Key • Linux Tips

The magic SysRq key can help you deal with a frozen and unresponsive system. It avoids doing a hard reboot and the potential loss of data.
linux-tips.us linux-tips.us
 
Brickwizard said:
Welcome to the forums, MSI can throw up a range of problems
open a terminal and enter, inxi -Fnxz, copy and paste back the results, so we can check the components and drivers, another thing you could try is disable hardware acceleration
Click to expand...
Here is the output of the command. Thank you for the help!
System: Kernel: 5.19.0-45-generic x86_64 bits: 64 compiler: N/A Desktop: GNOME 42.5 Distro: Ubuntu 22.04.2 LTS (Jammy Jellyfish) Machine: Type: Desktop Mobo: MSI model: Z170A GAMING M5 (MS-7977) v: 1.0 serial: <superuser required> UEFI: American Megatrends v: 1.A0 date: 07/22/2016 CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB Speed (MHz): avg: 4092 high: 4187 min/max: 800/4200 cores: 1: 4123 2: 4182 3: 4001 4: 4000 5: 4166 6: 4000 7: 4187 8: 4078 bogomips: 63999 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: eVga.com. driver: nvidia v: 515.105.01 bus-ID: 01:00.0 Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz OpenGL: renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 515.105.01 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Device-2: NVIDIA GP106 High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel bus-ID: 01:00.1 Device-3: Corsair VOID PRO Wireless Gaming Headset type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-6:2 Sound Server-1: ALSA v: k5.19.0-45-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: Qualcomm Atheros Killer E2400 Gigabit Ethernet vendor: Micro-Star MSI driver: alx v: kernel port: d000 bus-ID: 03:00.0 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel bus-ID: 04:00.0 IF: wlp4s0 state: down mac: <filter> IF-ID-1: nordlynx state: unknown speed: N/A duplex: N/A mac: N/A Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-10:3 Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2 Drives: Local Storage: total: 5 TiB used: 1.12 TiB (22.4%) ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB ID-2: /dev/sdb vendor: Toshiba model: HDWD130 size: 2.73 TiB ID-3: /dev/sdc vendor: Toshiba model: DT01ACA200 size: 1.82 TiB Partition: ID-1: / size: 456.88 GiB used: 387.04 GiB (84.7%) fs: ext4 dev: /dev/sda3 ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda2 Swap: ID-1: swap-1 type: file size: 2 GiB used: 2 MiB (0.1%) file: /swapfile Sensors: System Temperatures: cpu: 29.8 C pch: 39.0 C mobo: 27.8 C gpu: nvidia temp: 46 C Fan Speeds (RPM): N/A gpu: nvidia fan: 0% Info: Processes: 338 Uptime: 2h 42m Memory: 15.57 GiB used: 5.81 GiB (37.3%) Init: systemd runlevel: 5 Compilers: gcc: 11.3.0 Packages: 2544 Shell: Bash v: 5.1.16 inxi: 3.3.13

z7vl7abxc said:
do you know if you are using proprietary drivers for your nvidia gpu?
Click to expand...
kc1di said:
Nvidia usually ends up being the problem - make sure you have the correct driver installed
Click to expand...
I'm pretty sure I'm using the proprietary drivers. Do you know which one I should be using for my card? Thank you!

KGIII said:
Is this happening while you have a browser open?

Also, you can use REISUB to reboot more cleanly (probably, unless it's too frozen).

linux-tips.us

What You Need To Know About Linux's Magic SysRq Key • Linux Tips

The magic SysRq key can help you deal with a frozen and unresponsive system. It avoids doing a hard reboot and the potential loss of data.
linux-tips.us linux-tips.us
Click to expand...
It happens with and without the browser. I can open nothing and let it sit and eventually it'll still happen, even on fresh installs.
I have tried REISUB in the past and have not gotten the computer to shut down. I still have to hold down the power button in order to get it to turn off. Thank you for the help!
 
LavaGrenade said:
I'm pretty sure I'm using the proprietary drivers. Do you know which one I should be using for my card? Thank you!
Click to expand...
according to your inxi output, it does look like you are using the proprietary drivers.

i just created an ubuntu 22.04 virtual machine and it looks like there is an Additional Drivers item in the applications menu. have you tried running that to see if it has any suggestions for you regarding the gpu?

as far as the freezing issue, it looks like ubuntu also has a log viewer program. have you tried looking in there to see if you notice any errors or warnings? it looks like you could even filter for the word "error" or "warning" (without quotes). i realize as a new linux user it might be hard to distinguish, but that is one way to start trying to look into things until or unless someone else chimes in with a different investigation technique.

i have found the terminal command journalctl to be a more efficient way to search through log and system journal messages once you get the hang of it: https://www.thegeekdiary.com/beginn...urnalctl-to-view-and-manipulate-systemd-logs/
 
z7vl7abxc said:
isn't the -z option usually added to the above to filter out sensitive info?
Click to expand...
yes and should always be used with the F string if you are posting on an open site
 
the latest non-free Nvidia driver can be found here... https://www.nvidia.com/download/driverResults.aspx/179620/en-us/

LavaGrenade said:
System Temperatures: cpu: 29.8 C pch: 39.0 C mobo: 27.8 C gpu: nvidia temp: 46 C
Click to expand...
tells me there is nothing seriously wrong with the machine after nearly 3 hrs of running, the Z170A is used by several manufacturers and carries a varied range of minor problems,

so let's start with something basic, have you done a CMOS/bios re-boot ? To do this first save any current work on the machine, remove any cables attached to the machine [Power USB etc] Press and hold the power on button down for 60 seconds then switch on and re-boot
 
First thing I'd do, is to check all connections; but it could be a ram problem, as you say it happens on lots of different distros
 
Brickwizard said:
the latest non-free Nvidia driver can be found here... https://www.nvidia.com/download/driverResults.aspx/179620/en-us/


tells me there is nothing seriously wrong with the machine after nearly 3 hrs of running, the Z170A is used by several manufacturers and carries a varied range of minor problems,

so let's start with something basic, have you done a CMOS/bios re-boot ? To do this first save any current work on the machine, remove any cables attached to the machine [Power USB etc] Press and hold the power on button down for 60 seconds then switch on and re-boot
Click to expand...
Hi so sorry for the late reply to your help, it is very much appreciated. I did the CMOS reboot per your instructions and now I am no longer booting with a driver (I might be reading the inxi output wrong)? I have done a regular reboot afterwards to see if that would help but it didn't seem to do anything. I keep daily backups through timeshift so I could roll back to one of those and probably fix that particular issue.
My inxi output now reads
Code: 
System:
  Kernel: 5.19.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: GNOME 42.5
    Distro: Ubuntu 22.04.2 LTS (Jammy Jellyfish)
Machine:
  Type: Desktop Mobo: MSI model: Z170A GAMING M5 (MS-7977) v: 1.0
    serial: <filter> UEFI: American Megatrends v: 1.A0 date: 07/22/2016
CPU:
  Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP
    arch: Skylake-S rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 4047 high: 4200 min/max: 800/4200 cores: 1: 4000
    2: 4200 3: 4000 4: 4000 5: 4000 6: 4183 7: 4000 8: 4000 bogomips: 63999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: eVga.com. driver: N/A
    bus-ID: 01:00.0
  Display: server: X.Org v: 1.21.1.4 driver: X: loaded: nouveau,vesa
    unloaded: fbdev,modesetting gpu: N/A resolution: 1024x768~76Hz
  OpenGL: renderer: llvmpipe (LLVM 15.0.6 256 bits) v: 4.5 Mesa 22.2.5
    direct render: Yes
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  Device-2: NVIDIA GP106 High Definition Audio vendor: eVga.com.
    driver: snd_hda_intel v: kernel bus-ID: 01:00.1
  Sound Server-1: ALSA v: k5.19.0-46-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: Qualcomm Atheros Killer E2400 Gigabit Ethernet
    vendor: Micro-Star MSI driver: alx v: kernel port: d000 bus-ID: 03:00.0
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel bus-ID: 04:00.0
  IF: wlp4s0 state: down mac: <filter>
  IF-ID-1: nordlynx state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-10:2
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter>
    bt-v: 2.1 lmp-v: 4.2
Drives:
  Local Storage: total: 5 TiB used: 409.34 GiB (8.0%)
  ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
  ID-2: /dev/sdb vendor: Toshiba model: HDWD130 size: 2.73 TiB
  ID-3: /dev/sdc vendor: Toshiba model: DT01ACA200 size: 1.82 TiB
Partition:
  ID-1: / size: 456.88 GiB used: 409.33 GiB (89.6%) fs: ext4 dev: /dev/sda3
  ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat
    dev: /dev/sda2
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
  System Temperatures: cpu: 29.8 C pch: 36.5 C mobo: 27.8 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 318 Uptime: 2m Memory: 15.57 GiB used: 2.07 GiB (13.3%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.3.0 Packages: 2547 Shell: Sudo
  v: 1.9.9 inxi: 3.3.13

Brickwizard said:
just a thought, have you tried MX 21-AHS https://sourceforge.net/projects/mx-linux/files/Final/Xfce/MX-21.3_ahs_x64.iso/download
Click to expand...
I have not tried this distro before, but I will give it a try if I can't fix the issue on my current installation. Thank you for the recommendation, I had not heard of this distro before but it looks promising. Thank you for your help.
z7vl7abxc said:
according to your inxi output, it does look like you are using the proprietary drivers.

i just created an ubuntu 22.04 virtual machine and it looks like there is an Additional Drivers item in the applications menu. have you tried running that to see if it has any suggestions for you regarding the gpu?

as far as the freezing issue, it looks like ubuntu also has a log viewer program. have you tried looking in there to see if you notice any errors or warnings? it looks like you could even filter for the word "error" or "warning" (without quotes). i realize as a new linux user it might be hard to distinguish, but that is one way to start trying to look into things until or unless someone else chimes in with a different investigation technique.

i have found the terminal command journalctl to be a more efficient way to search through log and system journal messages once you get the hang of it: https://www.thegeekdiary.com/beginn...urnalctl-to-view-and-manipulate-systemd-logs/
Click to expand...
I have sifted through the journal ctl log of my last crash and I have copied anything that stood out to me. Thank you for you help and suggestions!

There may be a bug present? see the first line of the selected journalctl entries. Is there a way I can determine if this is present/active?
Code: 
Jul 15 14:35:24 AustinsDesktop kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kern>
Jul 15 14:35:24 AustinsDesktop kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. See http>
Jul 15 14:35:24 AustinsDesktop kernel:  #5 #6 #7

Jul 15 14:35:24 AustinsDesktop kernel: pci 0000:03:00.0: [Firmware Bug]: disabling VPD access (can't determine >

Jul 15 14:35:24 AustinsDesktop kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IM>
Jul 15 14:35:24 AustinsDesktop kernel: device-mapper: uevent: version 1.0.3
Jul 15 14:35:24 AustinsDesktop kernel: device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@re>
Jul 15 14:35:24 AustinsDesktop kernel: platform eisa.0: Probing EISA bus 0
Jul 15 14:35:24 AustinsDesktop kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Jul 15 14:35:24 AustinsDesktop kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Jul 15 14:35:24 AustinsDesktop kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Jul 15 14:35:24 AustinsDesktop kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Jul 15 14:35:24 AustinsDesktop kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Jul 15 14:35:24 AustinsDesktop kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Jul 15 14:35:24 AustinsDesktop kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Jul 15 14:35:24 AustinsDesktop kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Jul 15 14:35:24 AustinsDesktop kernel: platform eisa.0: Cannot allocate resource for EISA slot 8

Jul 15 14:35:24 AustinsDesktop kernel: usb: port power management may be unreliable

Jul 15 14:35:25 AustinsDesktop kernel: thermal thermal_zone3: failed to read out thermal zone (-61)

Jul 15 14:35:25 AustinsDesktop udisksd[825]: failed to load module mdraid: libbd_mdraid.so.2: cannot open share>

Jul 15 14:35:25 AustinsDesktop udisksd[825]: Failed to load the 'mdraid' libblockdev plugin

Jul 15 14:35:29 AustinsDesktop systemd[1]: kerneloops.service: Found left-over process 1084 (kerneloops) in con>
Jul 15 14:35:29 AustinsDesktop systemd[1]: This usually indicates unclean termination of a previous run, or ser>

Jul 15 14:35:31 AustinsDesktop NetworkManager[795]: <warn>  [1689456931.4245] platform-linux: do-add-ip6-addres>

Jul 15 14:35:46 AustinsDesktop gnome-session-binary[1390]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error >
Jul 15 14:35:46 AustinsDesktop gnome-session-binary[1390]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error >

Thank you all for your help! It is much appreciated
 
regarding that bug line from your journalctl output, this is the full line from my system running mx linux 21.3 in case you want to check the link:
Jul 13 13:32:50 kernel: [ 0.118458] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Click to expand...

if the journal messages get cut off, i usually try to maximize the window i am running the command in to get the most of them when possible.

from your inxi ouput, it does appear that the nvidia driver wasn't in use. nouveau (the open source nvidia driver) was loaded, but not listed as the gpu's driver so it may also not have been in use.

that inxi output identifies the gpu's pci bus as 01:00.0. in order to look for journal messages about that device and those drivers, i usually try something like

journalctl -b | grep -iE '01:00.0|nvidia|nouveau'
 
You must log in or register to reply here.

Members online

Total: 582 (members: 7, guests: 575)

Latest posts

Top