My ubuntu OS which I installed on hard-disk which is alongside ssd that contains windows is crashing very frequently. I have installed the OS quite a few times now but still after sometime it crashes and boots in initramfs. I have ran fsck command like so many times, and even after re installing ubuntu it runs good for a while but then crashes. Now even Chrome doesn't open. Sometimes after running fsck all my system appearance settings goes back to previous settings which were there when I installed it. What could be the problem?
Ubuntu 22.04.5 LTS crashes frequently
- Thread starter Gloria
- Start date
[ 0.000000] x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
[ 0.437526] i8042: Warning: Keylock active
[ 0.809844] RAS: Correctable Errors collector initialized.
[ 1.453671] psmouse serio1: elantech: elantech_send_cmd query 0x02 failed.
[ 1.453678] psmouse serio1: elantech: failed to query capabilities.
[ 3.048340] psmouse serio1: Failed to enable mouse on isa0060/serio1
[ 118.406368] xdg-desktop-por[2185]: segfault at 8 ip 00007cd7d12f2215 sp 00007fff61e3b700 error 4 in ld-linux-x86-64.so.2[7cd7d12d1000+2a000] likely on CPU 1 (core 1, socket 0)
[ 153.185920] ld-linux-x86-64[2864]: segfault at 8 ip 0000714e4104e215 sp 00007fffbacaa660 error 4 in ld-linux-x86-64.so.2[714e4102d000+2a000] likely on CPU 2 (core 2, socket 0)
[ 154.287645] ld-linux-x86-64[2879]: segfault at 8 ip 00007587139b0215 sp 00007ffe7fdb1430 error 4 in ld-linux-x86-64.so.2[75871398f000+2a000] likely on CPU 0 (core 0, socket 0)
[ 155.371850] ld-linux-x86-64[2891]: segfault at 8 ip 00007bbc3dcb5215 sp 00007ffc8327b480 error 4 in ld-linux-x86-64.so.2[7bbc3dc94000+2a000] likely on CPU 0 (core 0, socket 0)
[ 208.212530] xdg-desktop-por[4469]: segfault at 8 ip 000073c61eae4215 sp 00007ffc2d61b030 error 4 in ld-linux-x86-64.so.2[73c61eac3000+2a000] likely on CPU 5 (core 1, socket 0)
[ 220.565595] ld-linux-x86-64[5107]: segfault at 8 ip 000075f552d5a215 sp 00007ffc47c02220 error 4 in ld-linux-x86-64.so.2[75f552d39000+2a000] likely on CPU 0 (core 0, socket 0)
[ 221.675882] ld-linux-x86-64[5120]: segfault at 8 ip 00007158caf11215 sp 00007ffdd8741c80 error 4 in ld-linux-x86-64.so.2[7158caef0000+2a000] likely on CPU 2 (core 2, socket 0)
[ 222.789521] ld-linux-x86-64[5132]: segfault at 8 ip 00007694d65b4215 sp 00007ffd6a1eb3e0 error 4 in ld-linux-x86-64.so.2[7694d6593000+2a000] likely on CPU 5 (core 1, socket 0)
[ 328.374203] xdg-desktop-por[6243]: segfault at 8 ip 000070ba6c182215 sp 00007ffcecfc62b0 error 4 in ld-linux-x86-64.so.2[70ba6c161000+2a000] likely on CPU 3 (core 3, socket 0)
[ 2730.313673] xdg-desktop-por[8436]: segfault at 8 ip 00007d31ed7ca215 sp 00007ffe2062aa70 error 4 in ld-linux-x86-64.so.2[7d31ed7a9000+2a000] likely on CPU 2 (core 2, socket 0)
[ 0.437526] i8042: Warning: Keylock active
[ 0.809844] RAS: Correctable Errors collector initialized.
[ 1.453671] psmouse serio1: elantech: elantech_send_cmd query 0x02 failed.
[ 1.453678] psmouse serio1: elantech: failed to query capabilities.
[ 3.048340] psmouse serio1: Failed to enable mouse on isa0060/serio1
[ 118.406368] xdg-desktop-por[2185]: segfault at 8 ip 00007cd7d12f2215 sp 00007fff61e3b700 error 4 in ld-linux-x86-64.so.2[7cd7d12d1000+2a000] likely on CPU 1 (core 1, socket 0)
[ 153.185920] ld-linux-x86-64[2864]: segfault at 8 ip 0000714e4104e215 sp 00007fffbacaa660 error 4 in ld-linux-x86-64.so.2[714e4102d000+2a000] likely on CPU 2 (core 2, socket 0)
[ 154.287645] ld-linux-x86-64[2879]: segfault at 8 ip 00007587139b0215 sp 00007ffe7fdb1430 error 4 in ld-linux-x86-64.so.2[75871398f000+2a000] likely on CPU 0 (core 0, socket 0)
[ 155.371850] ld-linux-x86-64[2891]: segfault at 8 ip 00007bbc3dcb5215 sp 00007ffc8327b480 error 4 in ld-linux-x86-64.so.2[7bbc3dc94000+2a000] likely on CPU 0 (core 0, socket 0)
[ 208.212530] xdg-desktop-por[4469]: segfault at 8 ip 000073c61eae4215 sp 00007ffc2d61b030 error 4 in ld-linux-x86-64.so.2[73c61eac3000+2a000] likely on CPU 5 (core 1, socket 0)
[ 220.565595] ld-linux-x86-64[5107]: segfault at 8 ip 000075f552d5a215 sp 00007ffc47c02220 error 4 in ld-linux-x86-64.so.2[75f552d39000+2a000] likely on CPU 0 (core 0, socket 0)
[ 221.675882] ld-linux-x86-64[5120]: segfault at 8 ip 00007158caf11215 sp 00007ffdd8741c80 error 4 in ld-linux-x86-64.so.2[7158caef0000+2a000] likely on CPU 2 (core 2, socket 0)
[ 222.789521] ld-linux-x86-64[5132]: segfault at 8 ip 00007694d65b4215 sp 00007ffd6a1eb3e0 error 4 in ld-linux-x86-64.so.2[7694d6593000+2a000] likely on CPU 5 (core 1, socket 0)
[ 328.374203] xdg-desktop-por[6243]: segfault at 8 ip 000070ba6c182215 sp 00007ffcecfc62b0 error 4 in ld-linux-x86-64.so.2[70ba6c161000+2a000] likely on CPU 3 (core 3, socket 0)
[ 2730.313673] xdg-desktop-por[8436]: segfault at 8 ip 00007d31ed7ca215 sp 00007ffe2062aa70 error 4 in ld-linux-x86-64.so.2[7d31ed7a9000+2a000] likely on CPU 2 (core 2, socket 0)
x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks:
This message indicates that the kernel has detected a split lock, which can degrade performance. The kernel is configured to crash on kernel split locks and warn on user-space split locks.
i8042: Warning: Keylock active:
This warning suggests that the keylock (often related to the keyboard controller) is active. It usually doesn't affect system performance but indicates that the keyboard might be locked.
RAS: Correctable Errors collector initialized:
This message is part of the Reliability, Availability, and Serviceability (RAS) features of the kernel. It indicates that the system is ready to collect and handle correctable hardware errors.
psmouse serio1: elantech: elantech_send_cmd query 0x02 failed and psmouse serio1: elantech: failed to query capabilities:
These errors are related to the Elantech touchpad driver failing to communicate with the touchpad hardware. This might result in the touchpad not working correctly.
psmouse serio1: Failed to enable mouse on isa0060/serio1:
This error indicates that the system failed to initialize the mouse on the specified port. It could be related to the previous Elantech errors6.
Segfaults in xdg-desktop-portal and ld-linux-x86-64.so.2:
These segmentation faults (segfaults) indicate that the xdg-desktop-portal and ld-linux-x86-64.so.2 processes are crashing. This could be due to bugs in the software or issues with the system libraries.
the segmentation faults (segfaults) you're seeing on the CPU cores are related to ld-linux-x86-64.so.2. These errors indicate that the dynamic linker/loader (ld-linux-x86-64.so.2) is encountering issues, likely due to trying to access invalid memory addresses.
Segfaults typically occur when a program tries to read or write to a memory location that it shouldn't. In this case, the errors are happening within the dynamic linker, which is responsible for loading shared libraries needed by programs. The repeated segfaults suggest there might be a problem with the dynamic linker itself, the libraries it is trying to load, or the applications using it.
A few steps you can take to troubleshoot these issues:
Check for Updates: Ensure your system and all packages are up to date. Sometimes, these issues are resolved in newer versions of the software.
Run Diagnostics: Use tools like memtest86 to check for memory issues, as faulty RAM can cause segfaults.
Reinstall ld-linux-x86-64.so.2 and any related packages to ensure they are not corrupted.
Check Logs: Look at other system logs for additional clues. Sometimes, segfaults are preceded by other warnings or errors that can help pinpoint the issue.
Debugging: If you have experience with debugging, you can use tools like gdb to get more detailed information about where and why the segfaults are occurring.
As a last resort, you can try booting from a LiveUSB of a different distro ( with a different kernel version ) and see if the same thing happens.
I see you are getting these errors on most of your CPU cores. If it was just 1 or 2 I would say maybe the CPU is suspect. But because I see it on all 6, I don't think it's the CPU. So then what do they have in common? The RAM could be bad. ( test with memtest ), or the ld-linux-so.2 library could be bad ( try re-installing it if you can )
This message indicates that the kernel has detected a split lock, which can degrade performance. The kernel is configured to crash on kernel split locks and warn on user-space split locks.
i8042: Warning: Keylock active:
This warning suggests that the keylock (often related to the keyboard controller) is active. It usually doesn't affect system performance but indicates that the keyboard might be locked.
RAS: Correctable Errors collector initialized:
This message is part of the Reliability, Availability, and Serviceability (RAS) features of the kernel. It indicates that the system is ready to collect and handle correctable hardware errors.
psmouse serio1: elantech: elantech_send_cmd query 0x02 failed and psmouse serio1: elantech: failed to query capabilities:
These errors are related to the Elantech touchpad driver failing to communicate with the touchpad hardware. This might result in the touchpad not working correctly.
psmouse serio1: Failed to enable mouse on isa0060/serio1:
This error indicates that the system failed to initialize the mouse on the specified port. It could be related to the previous Elantech errors6.
Segfaults in xdg-desktop-portal and ld-linux-x86-64.so.2:
These segmentation faults (segfaults) indicate that the xdg-desktop-portal and ld-linux-x86-64.so.2 processes are crashing. This could be due to bugs in the software or issues with the system libraries.
the segmentation faults (segfaults) you're seeing on the CPU cores are related to ld-linux-x86-64.so.2. These errors indicate that the dynamic linker/loader (ld-linux-x86-64.so.2) is encountering issues, likely due to trying to access invalid memory addresses.
Segfaults typically occur when a program tries to read or write to a memory location that it shouldn't. In this case, the errors are happening within the dynamic linker, which is responsible for loading shared libraries needed by programs. The repeated segfaults suggest there might be a problem with the dynamic linker itself, the libraries it is trying to load, or the applications using it.
A few steps you can take to troubleshoot these issues:
Check for Updates: Ensure your system and all packages are up to date. Sometimes, these issues are resolved in newer versions of the software.
Run Diagnostics: Use tools like memtest86 to check for memory issues, as faulty RAM can cause segfaults.
Reinstall ld-linux-x86-64.so.2 and any related packages to ensure they are not corrupted.
Check Logs: Look at other system logs for additional clues. Sometimes, segfaults are preceded by other warnings or errors that can help pinpoint the issue.
Debugging: If you have experience with debugging, you can use tools like gdb to get more detailed information about where and why the segfaults are occurring.
As a last resort, you can try booting from a LiveUSB of a different distro ( with a different kernel version ) and see if the same thing happens.
I see you are getting these errors on most of your CPU cores. If it was just 1 or 2 I would say maybe the CPU is suspect. But because I see it on all 6, I don't think it's the CPU. So then what do they have in common? The RAM could be bad. ( test with memtest ), or the ld-linux-so.2 library could be bad ( try re-installing it if you can )
Last edited:
Staff online
-
wizardfromozAdministrator
Latest posts
-
-
-
-
Direct Unbound DNS-over-HTTPS (DoH) traffic through SSH tunneling- Latest: CaffeineAddict
-