[UNSOLVED] ventoy UEFI causing system to freeze.

P

price1221

Active Member
Joined
Jun 13, 2021
Messages
109
Reaction score
26
Credits
797
Linux starts to one by one application then freezes. Then black and white error shows. I got no clue why it is happening. And dont know which logs to check bcz i have to reboot the device.
 
Last edited:


Hardware info
1709752318173.png
 
Sadly I can't read text to see what's happening but it looks like there is stack trace included at the end in your first post which might suggest driver issue or something similar.

What I would try is boot in recovery mode or boot by using secondary kernel, during boot process select recovery mode or secondary (older kernel)
 
CaffeineAddict said:
Sadly I can't read text to see what's happening but it looks like there is stack trace included at the end in your first post which might suggest driver issue or something similar.

What I would try is boot in recovery mode or boot by using secondary kernel, during boot process select recovery mode or secondary (older kernel)
Click to expand...
im currently in 6.1.0-18-amd64. while booting i get 6.1.0-18-amd64 and 6.1.0-17-amd64 both gives this problem. and the problem is sudden so i cant reproduce or anything. just happens all of a sudden.


maybe this is kinda visible
1709758465906.png
1709758486843.png
1709758465906.png
1709758486843.png
 
Last edited by a moderator:
mukto6121 said:
This doesnt happens when in grub but after using my laptop and all of sudden everything starts to crash and then black and white screen with those texts. and if doesnt happen everytime but once in while
Click to expand...
Thanks for that clarification. I guess it might be time to check the overall health of the system since freezes can be caused from many different parts of the system. You can check things whilst the machine is running well, or use a live disk or a rescue disk such as systemrescue to check a lot of things also.

These suggestions may be of use:

Check the output of the command: dmesg, to see if there is any output of interest showing a problem.

The logs to check are in the directory /var/log. Some are text logs which can be inspected with a text editor like nano, vim, gedit etc. The major logs in /var/log to check include: syslog, messages, kern.log, user.log. Some may not be there depending on installation.

The journal log needs to be accessed by a journalctl command like:
Code: 
journalctl -b -x -p 3
which should show errors, or a command like:
Code: 
journalctl -b | grep error
or to see all of the journal output for the current boot:
Code: 
journalctl -b
where you'd need to check through perhaps a couple of thousand lines ... but it doesn't take too long if you are searching for errors.

These further areas are possibly worth checking:
Is there an issue with RAM? One can check RAM with the program: memtest86+, from a live disk or rescue disk, or install the program and run it from the grub menu.

Is there overheating? Check temperatures with the program: lm-sensors, installed. Run:
Code: 
sensors
It will show the high and critical temperatures that are not to be reached.

Is there an issue with the storage drive? Check the hard drive with the program: smartctl, e.g.
Code: 
smartctl -H /dev/sdX
where you replace /dev/sdX with the device name of your hard drive.

Are there power supply issues? To check the power supply can be a bit more involved requiring the use of a multimeter, but probably only needs to be checked if all the other tests don't find any problem.

If you can run in text mode without any of the freezing happening, then the issue may be associated with the graphics card and/or its drivers and modules. So, if you knew for example, that the freeze would always occur within an hour, then running in text mode for more than that hour without a freeze, could suggest a graphics issue.

In relation to the BIOS/UEFI, it's best to have the latest version installed if the manufacturer has an update available, but it may be best to leave this step until everything else has been checked if there are no symptoms of a BIOS/UEFI problem.

The images provided in post #1 and post #4 are unreadable. If you can read them, perhaps transcribe the last 10 or so lines exactly, or as many as you can manage.
 
Last edited:
Run Memtest overnight to see if the RAM is bad.

I had performance issues with the Gnome DE installed.
After installing the Cinnamon DE all those performance issue disappeared.
 
I can read the second to the last line on the bottom photo in post 4 - it says "Kernel Panic - Not Syncing: Attempted to kill Init!"

Since this is intermittent I would check your HD for errors using smartctl - your HD may be getting ready to die as @osprey has stated
 
osprey said:
Thanks for that clarification. I guess it might be time to check the overall health of the system since freezes can be caused from many different parts of the system. You can check things whilst the machine is running well, or use a live disk or a rescue disk such as systemrescue to check a lot of things also.

These suggestions may be of use:

Check the output of the command: dmesg, to see if there is any output of interest showing a problem.

The logs to check are in the directory /var/log. Some are text logs which can be inspected with a text editor like nano, vim, gedit etc. The major logs in /var/log to check include: syslog, messages, kern.log, user.log. Some may not be there depending on installation.

The journal log needs to be accessed by a journalctl command like:
Code: 
journalctl -b -x -p 3
which should show errors, or a command like:
Code: 
journalctl -b | grep error
or to see all of the journal output for the current boot:
Code: 
journalctl -b
where you'd need to check through perhaps a couple of thousand lines ... but it doesn't take too long if you are searching for errors.

These further areas are possibly worth checking:
Is there an issue with RAM? One can check RAM with the program: memtest86+, from a live disk or rescue disk, or install the program and run it from the grub menu.

Is there overheating? Check temperatures with the program: lm-sensors, installed. Run:
Code: 
sensors
It will show the high and critical temperatures that are not to be reached.

Is there an issue with the storage drive? Check the hard drive with the program: smartctl, e.g.
Code: 
smartctl -H /dev/sdX
where you replace /dev/sdX with the device name of your hard drive.

Are there power supply issues? To check the power supply can be a bit more involved requiring the use of a multimeter, but probably only needs to be checked if all the other tests don't find any problem.

If you can run in text mode without any of the freezing happening, then the issue may be associated with the graphics card and/or its drivers and modules. So, if you knew for example, that the freeze would always occur within an hour, then running in text mode for more than that hour without a freeze, could suggest a graphics issue.

In relation to the BIOS/UEFI, it's best to have the latest version installed if the manufacturer has an update available, but it may be best to leave this step until everything else has been checked if there are no symptoms of a BIOS/UEFI problem.

The images provided in post #1 and post #4 are unreadable. If you can read them, perhaps transcribe the last 10 or so lines exactly, or as many as you can manage.
Click to expand...
sudo swapoff -a
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 4K 1 loop /snap/bare/5
loop1 7:1 0 105.8M 1 loop /snap/core/16202
loop2 7:2 0 55.7M 1 loop /snap/core18/2812
loop3 7:3 0 74.2M 1 loop /snap/core22/1122
loop4 7:4 0 63.9M 1 loop /snap/core20/2182
loop5 7:5 0 66.5M 1 loop /snap/cups/1024
loop6 7:6 0 164.8M 1 loop /snap/gnome-3-28-1804/198
loop7 7:7 0 105.4M 1 loop /snap/core/16574
loop8 7:8 0 438.3M 1 loop /snap/kf5-5-110-qt-5-15-11-core22/3
loop9 7:9 0 84.3M 1 loop /snap/notion-snap-reborn/36
loop10 7:10 0 303.1M 1 loop /snap/wine-platform-5-stable/18
loop11 7:11 0 101.2M 1 loop /snap/termius-app/181
loop12 7:12 0 45.6M 1 loop /snap/winbox/133
loop13 7:13 0 347.1M 1 loop /snap/wine-platform-runtime/360
loop14 7:14 0 84.3M 1 loop /snap/notion-snap-reborn/37
loop15 7:15 0 45.6M 1 loop /snap/winbox/131
loop16 7:16 0 347.1M 1 loop /snap/wine-platform-runtime/358
loop17 7:17 0 91.7M 1 loop /snap/gtk-common-themes/1535
loop18 7:18 0 101.2M 1 loop /snap/termius-app/182
sda 8:0 0 238.5G 0 disk
├─sda1 8:1 0 300M 0 part /boot/efi
├─sda2 8:2 0 230G 0 part /
└─sda3 8:3 0 8.2G 0 part
sudo smartctl -H /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-18-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
 
GatorsFan said:
I can read the second to the last line on the bottom photo in post 4 - it says "Kernel Panic - Not Syncing: Attempted to kill Init!"

Since this is intermittent I would check your HD for errors using smartctl - your HD may be getting ready to die as @osprey has stated
Click to expand...
have provided the output above
 
mukto6121 said:
Maybe this is better
Click to expand...
It does tell a lot, but before anything can be concluded please answer the following 4 questions:

1. Is your GPU Nvidia?

2. If so, which driver version are you using?
To learn driver version run this nvidia-smi --query-gpu=driver_version --format=csv,noheader

3. Which kernel version are you using?
To learn kernel version run uname -r

4. Are you using X11 or Wayland session to log-in to desktop?
You can see which you're using on login screen
 
osprey said:
@CaffeineAddict, in post #2 it is clear that the graphics card is intel, the driver is i915, the machine is running wayland and xwayland, and the kernel is 6.1.0-18 :)
Click to expand...
Crap, I completely forgot about it!
thanks for reminder.

@mukto6121
I suggest you switch to x11 and use it for your desktop session, if you again encounter the same problem with x11 then I would start focusing on your GPU driver.
 
mukto6121 said:
sudo swapoff -a
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 4K 1 loop /snap/bare/5
loop1 7:1 0 105.8M 1 loop /snap/core/16202
loop2 7:2 0 55.7M 1 loop /snap/core18/2812
loop3 7:3 0 74.2M 1 loop /snap/core22/1122
loop4 7:4 0 63.9M 1 loop /snap/core20/2182
loop5 7:5 0 66.5M 1 loop /snap/cups/1024
loop6 7:6 0 164.8M 1 loop /snap/gnome-3-28-1804/198
loop7 7:7 0 105.4M 1 loop /snap/core/16574
loop8 7:8 0 438.3M 1 loop /snap/kf5-5-110-qt-5-15-11-core22/3
loop9 7:9 0 84.3M 1 loop /snap/notion-snap-reborn/36
loop10 7:10 0 303.1M 1 loop /snap/wine-platform-5-stable/18
loop11 7:11 0 101.2M 1 loop /snap/termius-app/181
loop12 7:12 0 45.6M 1 loop /snap/winbox/133
loop13 7:13 0 347.1M 1 loop /snap/wine-platform-runtime/360
loop14 7:14 0 84.3M 1 loop /snap/notion-snap-reborn/37
loop15 7:15 0 45.6M 1 loop /snap/winbox/131
loop16 7:16 0 347.1M 1 loop /snap/wine-platform-runtime/358
loop17 7:17 0 91.7M 1 loop /snap/gtk-common-themes/1535
loop18 7:18 0 101.2M 1 loop /snap/termius-app/182
sda 8:0 0 238.5G 0 disk
├─sda1 8:1 0 300M 0 part /boot/efi
├─sda2 8:2 0 230G 0 part /
└─sda3 8:3 0 8.2G 0 part
sudo smartctl -H /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-18-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
Click to expand...
It looks to me that you have a bunch of snaps installed and there in may lay your problem. I have no snaps install on my debian 12 and never have a problem with it freezing. Just a thought.
 
CaffeineAddict said:
It does tell a lot, but before anything can be concluded please answer the following 4 questions:

1. Is your GPU Nvidia?

2. If so, which driver version are you using?
To learn driver version run this nvidia-smi --query-gpu=driver_version --format=csv,noheader

3. Which kernel version are you using?
To learn kernel version run uname -r

4. Are you using X11 or Wayland session to log-in to desktop?
You can see which you're using on login screen
Click to expand...


1. not using any gpu. intel cpu with its gpu
2. no nvidia driver
3. 6.1.0-18-amd64 kernel
4. wayland with gnome
 
CaffeineAddict said:
Crap, I completely forgot about it!
thanks for reminder.

@mukto6121
I suggest you switch to x11 and use it for your desktop session, if you again encounter the same problem with x11 then I would start focusing on your GPU driver.
Click to expand...
x11 also causes the problem. The problem happens rarely but it is must when i am using discord to share screen for few minutes in discord application by apt or by browser
 
kc1di said:
It looks to me that you have a bunch of snaps installed and there in may lay your problem. I have no snaps install on my debian 12 and never have a problem with it freezing. Just a thought.
Click to expand...
ok i will remove the snap packages
 
You must log in or register to reply here.

Members online

Total: 740 (members: 2, guests: 738)

Latest posts

Top