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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2080182

Title:
  System hangs after GDM login with 6.8.0 kernel

Status in linux package in Ubuntu:
  New

Bug description:
  I recently upgraded a working system from Ubuntu 22.04 to 24.04. After
  the upgrade, the system has acquired an eagerness to become completely
  nonresponsive about a minute after logging in to a graphical session.
  Logging in via console/SSH does not trigger hangs as quickly but they
  still occur within a few hours typically. When logging in to a
  graphical session, I notice immediately that performance and
  responsiveness is heavily degraded, and within moments, the entire
  system locks up. Any existing SSH sessions immediately stop
  responding, and the display freezes on whatever it was previously
  displaying. No keyboard or mouse input has any observable effect on
  the system, and it must be powered off manually.

  The system does not reboot automatically nor does it power off. I
  configured linux-crashdump and triggered a kernel panic to verify that
  dump files can be written successfully. However, they are not written
  on this hang, implying that it is not a kernel crash.

  The new Linux kernel version is 6.8.0-41, while the old kernel
  6.5.0-45 is still installed. When booting into the older kernel
  version (no other changes), these symptoms do not occur and function
  is as it was before the 24.04 upgrade.

  Seeing LP#2073358, I tested linux-oem-6.8/6.8.0-1011.11 but this has
  the same behavior as 6.8.0-41-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-41-generic 6.8.0-41.41
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  raxod502   1884 F.... wireplumber
   /dev/snd/seq:        raxod502   1880 F.... pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Sep  9 17:51:02 2024
  InstallationDate: Installed on 2022-10-28 (683 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 3626AL3
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash 
crashkernel=2G-4G:1024M,4G-32G:1024M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-45-generic N/A
   linux-backports-modules-6.5.0-45-generic  N/A
   linux-firmware                            20240318.git3b128b60-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-09-03 (7 days ago)
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626AL3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 20124051
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626AL3:pvrThinkPadX201:rvnLENOVO:rn3626AL3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626AL3
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.init.d.apport: 2024-07-22T07:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080182/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to