Hello Radon, thank you for taking the time to open this bug report. I've read through much of the logs you have provided, and the only thing that stands out is the segfaults that are happening in the end of the dmesg file and syslog file.
1) [ 321.304482] zsh[5354]: segfault at 10 ip 00006010da089caa sp 00007ffdc1981c00 error 4 in zsh[6010da011000+b9000] likely on CPU 1 (core 0, socket 0) [ 321.304508] Code: f6 74 08 85 f6 0f 84 9d 01 00 00 45 31 ed 89 c2 81 e2 ff ff bf ff 89 53 10 a9 00 00 00 01 75 0d 48 8b 43 20 44 89 e6 48 89 df <ff> 50 10 48 83 7b 30 00 74 1a 48 8b 7b 08 e8 03 8a f8 ff 48 8b 7b ----- 2) [ 378.452809] w[6224]: segfault at 4c ip 000056fa7fe66e73 sp 00007ffe52a049d0 error 4 in w[56fa7fe66000+3000] likely on CPU 3 (core 2, socket 0) [ 378.452827] Code: 01 40 0f 84 8f 00 00 00 80 fb 20 0f 84 86 00 00 00 0f be fb 49 83 c4 01 e8 3a f6 ff ff 4c 39 65 c8 0f 84 88 00 00 00 45 89 ee <41> 0f b6 1c 24 84 db 75 ac 45 85 f6 75 6f 4c 8b 2d 58 41 00 00 bf ----- 3) [ 978.984338] w[7121]: segfault at 4c ip 00005a0e7b31be73 sp 00007ffe88ce6f10 error 4 in w[5a0e7b31b000+3000] likely on CPU 0 (core 0, socket 0) [ 978.984357] Code: 01 40 0f 84 8f 00 00 00 80 fb 20 0f 84 86 00 00 00 0f be fb 49 83 c4 01 e8 3a f6 ff ff 4c 39 65 c8 0f 84 88 00 00 00 45 89 ee <41> 0f b6 1c 24 84 db 75 ac 45 85 f6 75 6f 4c 8b 2d 58 41 00 00 bf ---- These are very strange. Having segfaults in zsh, and w should not be happening. The "error 4" means it is trying to read a user-mode page which cannot be found. Looking at these 3 segfaults: 1) zsh is trying to access the memory address 0x10 and is causing a user page fault. 2) w is trying to access the memory address 0x4c and is causing a user page fault. 3) w is again trying to access memory at 0x4c and is causing a user page fault. Memory addresses 0x10 and 0x4c aren't valid addresses, and this is causing the error. This is usually caused by a failing/faulty disk, or memory. Everything may have been fine when you where running 22.04, but during the upgrade to 24.04 something was corrupted either by faulty memory, or a faulty drive. This means that you will likely hit these same errors repeatability because corrupted versions have been written to disk. This can be seen by the "w" command having the same "Code" and trapping on the same 0x4c address. You should download a copy of memtest86 and try running it on your system, and see if your ram is alright. You should also boot off of a live USB and check the SMART data of your HDD and make sure it is fine. Perhaps copy your data off to another drive if possible. You can also run fsck to try to check the disk. If the memory and disk check out fine, please let me know and I can continue to help with this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080182 Title: System hangs after GDM login with 6.8.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080182/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
