Mint-21 crashes

[antonizator]

Hi everyone! Can someone help we to figure out why linux crashes. I don't have much info when this happens. It happens randomly.

Here is inxi -Fxz

Code: Select all

	System:
  Kernel: 5.15.0-53-generic x86_64 bits: 64 compiler: gcc v: 11.2.0
    Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
    base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: Timi product: TM1701 v: N/A
    serial: <superuser required>
  Mobo: Timi model: TM1701 v: MP serial: <superuser required> UEFI: INSYDE
    v: XMAKB5R0P0C07 date: 02/22/2019
Battery:
  ID-1: BAT0 charge: 42.5 Wh (100.0%) condition: 42.5/60.0 Wh (70.8%)
    volts: 8.6 min: 7.6 model: SUNWODA R15B01W status: Full
CPU:
  Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP
    arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 1107 high: 1959 min/max: 400/4000 cores: 1: 1919
    2: 1959 3: 1026 4: 800 5: 800 6: 799 7: 800 8: 757 bogomips: 31999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Xiaomi driver: i915 v: kernel
    bus-ID: 00:02.0
  Device-2: NVIDIA GP108BM [GeForce MX250] vendor: Xiaomi driver: nvidia
    v: 515.65.01 bus-ID: 01:00.0
  Device-3: Sunplus Innovation XiaoMi USB 2.0 Webcam type: USB
    driver: uvcvideo bus-ID: 1-6:3
  Display: x11 server: X.Org v: 1.21.1.3 driver: X:
    loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa gpu: i915
    resolution: 3072x1728~60Hz
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
    v: 4.6 Mesa 22.0.5 direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Xiaomi
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  Sound Server-1: ALSA v: k5.15.0-53-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: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel
    bus-ID: 02:00.0
  IF: wlp2s0 state: up mac: <filter>
  IF-ID-1: br-53637b6f90bd state: down mac: <filter>
  IF-ID-2: br-735af3bac137 state: down mac: <filter>
  IF-ID-3: br-c76bdbedd227 state: down mac: <filter>
  IF-ID-4: br-dd65bac928b8 state: down mac: <filter>
  IF-ID-5: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-5:2
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter>
    bt-v: 2.1 lmp-v: 4.2
Drives:
  Local Storage: total: 476.94 GiB used: 364.12 GiB (76.3%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-00000
    size: 476.94 GiB temp: 31.9 C
Partition:
  ID-1: / size: 467.89 GiB used: 182.06 GiB (38.9%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
  System Temperatures: cpu: 49.0 C pch: 40.5 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 330 Uptime: 13m Memory: 15.51 GiB used: 4.29 GiB (27.7%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.3.0 Packages: 2711 Shell: Bash
  v: 5.1.16 inxi: 3.3.13

[kc1di]

Hello antonizator,
Welcome to Linux Mint.
I suspect it's the Nvidia graphics card causing the problem. If that is the one your using.
See here:
https://easylinuxtipsproject.blogspot.c ... deset.html
See if that helps.

[Hoser Rob]

Hello antonizator,
Welcome to Linux Mint.
I suspect it's the Nvidia graphics card causing the problem. If that is the one your using.
See here:
https://easylinuxtipsproject.blogspot.c ... deset.html
See if that helps.

It's nt the nvidia card being used, it's the integrated INtel one, as shown here in inxi:

Code: Select all

OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2)

And I wouldn't suggest using nomodeset with Intel myself.

If yu tried it, remove it and then go into driver manager and try the recommended nvidia driver.

[SMG]

Hi everyone! Can someone help we to figure out why linux crashes. I don't have much info when this happens. It happens randomly.

Welcome to the forum, antonizator.

Please describe what you mean by a crash. Does the system just freeze? Does the screen go black? Does the operating system automatically reboot?

Please also let us know what is happening when this crash happens.

By the way, do not add nomodeset as per the recommendation in the second post. Preventing the graphics drivers from loading properly is not a solution to this type of problem.

I would suggest making sure this is the most recent BIOS/UEFI available for your computer.

Machine:
Type: Laptop System: Timi product: TM1701 v: N/A
serial: <superuser required>
Mobo: Timi model: TM1701 v: MP serial: <superuser required> UEFI: INSYDE
v: XMAKB5R0P0C07 date: 02/22/2019

[antonizator]

Hi everyone! Can someone help we to figure out why linux crashes. I don't have much info when this happens. It happens randomly.

Welcome to the forum, antonizator.

Please describe what you mean by a crash. Does the system just freeze? Does the screen go black? Does the operating system automatically reboot?

Please also let us know what is happening when this crash happens.

By the way, do not add nomodeset as per the recommendation in the second post. Preventing the graphics drivers from loading properly is not a solution to this type of problem.

I would suggest making sure this is the most recent BIOS/UEFI available for your computer.

Machine:
Type: Laptop System: Timi product: TM1701 v: N/A
serial: <superuser required>
Mobo: Timi model: TM1701 v: MP serial: <superuser required> UEFI: INSYDE
v: XMAKB5R0P0C07 date: 02/22/2019

Hi, thanks for your reply. By crash i mean that system just freeze for few seconds and after that the black screen appears.

About bios the command:

Code: Select all

fwupdmgr get-updates

gave me

Code: Select all

Devices with no available firmware updates: 
 • ETD2303:00 04F3:3083
 • MZVLB512HAJQ-00000
 • System Firmware
 • UEFI Device Firmware
Devices with the latest available firmware version:
 • UEFI dbx
No updates available

[SMG]

By crash i mean that system just freeze for few seconds and after that the black screen appears.

What are you doing on the computer when that happens?

Is it possible the laptop might be overheating?

[antonizator]

By crash i mean that system just freeze for few seconds and after that the black screen appears.

What are you doing on the computer when that happens?

Is it possible the laptop might be overheating?

I don't think it happens because of overheating. Sometimes it happens instantly after reboot, sometimes when i up docker containers, sometimes while i watching a video.

[SMG]

Sometimes it happens instantly after reboot, sometimes when i up docker containers, sometimes while i watching a video.

Happening instantly after a reboot sounds like it could be a hardware-related issue. The next time you have to restart because this happens, please run the following:

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 (the one which you stopped with the power button--I presume that is how you are restarting) in reverse order (so the reason for the freeze should be near the top) and sends it to termbin.

[antonizator]

Thanks everyone for replies. I think i resolved the problem. I changed from use nvidia on demand to nvidia perfomance mode in nvidia settings and so far i hand't any crashes (i did it yesterday).

[antonizator]

Sometimes it happens instantly after reboot, sometimes when i up docker containers, sometimes while i watching a video.

Happening instantly after a reboot sounds like it could be a hardware-related issue. The next time you have to restart because this happens, please run the following:

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 (the one which you stopped with the power button--I presume that is how you are restarting) in reverse order (so the reason for the freeze should be near the top) and sends it to termbin.

Crashes are back, but they r not so often. I just booted and crashed. Here is the link: https://termbin.com/z5ld

[SMG]

Crashes are back, but they r not so often. I just booted and crashed.

I don't see a crash. I see a power stoppage. Start-up is humming along and then boom--the log just stops.

What are you seeing/hearing that you are making the assumption the system crashed? And how long are you giving the system to respond before you decide it has crashed?

[antonizator]

Crashes are back, but they r not so often. I just booted and crashed.

I don't see a crash. I see a power stoppage. Start-up is humming along and then boom--the log just stops.

What are you seeing/hearing that you are making the assumption the system crashed? And how long are you giving the system to respond before you decide it has crashed?

Maybe you don't see anything cause i ran the command after restart. When system crashes i have either screen freeze or all windows closed after what i can't do anything. Alt F1 doesn't help cause there i see only errors and can't login to system

[SMG]

Maybe you don't see anything cause i ran the command after restart.

The command gets information from the prior boot cycle.

When system crashes i have either screen freeze or all windows closed after what i can't do anything.

How many minutes do you wait before you decide you can not do anything? 5 minutes? 10 minutes?

The system freezing is different than all windows closing. Those are two different types of problems. Please do not combine them when describing what issues you are seeing because it is likely those have two different root causes. Windows closing is likely a crash. The system freezing is not a crash.

[antonizator]

Maybe you don't see anything cause i ran the command after restart.

The command gets information from the prior boot cycle.

When system crashes i have either screen freeze or all windows closed after what i can't do anything.

How many minutes do you wait before you decide you can not do anything? 5 minutes? 10 minutes?

The system freezing is different than all windows closing. Those are two different types of problems. Please do not combine them when describing what issues you are seeing because it is likely those have two different root causes. Windows closing is likely a crash. The system freezing is not a crash.

Oh I see.
I wait 2 or 3 mins after freezing and after that i reboot with power button.
When windows close i try to reboot with system buttons, but i just see black screen with error listing and i can't do anything with that so i reboot with power button either.

[SMG]

I wait 2 or 3 mins after freezing and after that i reboot with power button.

Please wait longer next time.

but i just see black screen with error listing

We need to know that error. Either write down the message or take a photo of it and post it.

A black screen with an error listing sounds like a hardware-related issue.

[antonizator]

I wait 2 or 3 mins after freezing and after that i reboot with power button.

Please wait longer next time.

but i just see black screen with error listing

We need to know that error. Either write down the message or take a photo of it and post it.

A black screen with an error listing sounds like a hardware-related issue.

[SMG]

fs = file system

I hope you have that data on the drive backed up. There are either problems with the drive or with the filesystem. (Problems with the drive could cause file system errors.)

I suggest you boot to a live session of Linux Mint using your install usb/dvd and run fsck on your hard drive. See if you can get those errors fixed.
How to Use fsck Command to Check and Repair Filesystem