[Bug 2103472] Re: Kernel panic on lengthy filesystem access
I was able to consistently reproduce this by: * installing Ubuntu 24.10 and updating and upgrading * setting systemd to default to multi-user.target * mounting the exfat filesystem on the real PCI SD card reader at /mnt (sudo mount /dev/mmcblk0p1 /mnt) * sha256summing each file on it (find /mnt -type f -print0 | xargs -0 sha256sum) When doing this, after processing around 50GB of files, the system crashes. I'm now trying to narrow it down further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103472 Title: Kernel panic on lengthy filesystem access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103472] Re: Kernel panic on lengthy filesystem access
(Note that going into multi-user mode instead of graphical mode is just for convenience; it doesn't appear to be a part of the problem specifically.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103472 Title: Kernel panic on lengthy filesystem access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103472] Re: Kernel panic on lengthy filesystem access
** Description changed: Because of https://bugs.launchpad.net/ubuntu/+source/kdump- tools/+bug/2103470 and https://bugs.launchpad.net/ubuntu/+source/kdump- tools/+bug/2103471, I *still* cannot get a kernel crash dump for this bug. However, it's pretty clear that this is a kernel panic. - Curiously, it appeared in both (a Live CD of) Ubuntu 24.04 and (my - current installation of) Ubuntu 24.10. + Curiously, it appeared in both (a Live CD of) Ubuntu 24.04.2 and (my + current installation of) Ubuntu 24.10. It does NOT appear in (a Live CD + of) Fedora 41-1.4, and on Fedora nothing appears in dmesg to even + suggest that there's a problem (even one that doesn't lead to a panic). The current kernel is 6.11.0-19-generic. I would expect that simple filesystem operations like rsync -Pvach /some/exfat/filesystem/ /some/ext4/filesystem and cp -ar /some/exfat/filesystem/ /some/exfat/filesystem and rsync -Pvach /some/exfat/filesystem/ user@server:/destination/directory and even diff --recursive /some/exfat/filesystem/ /some/ext4/filesystem would not cause the system to kernel panic under any circumstances, and would instead produce userspace errors. However, consistently, after doing one of these tasks for a while, the kernel panics. Again, I'm unable to determine the nature of the kernel panic due to kdump-tools bugs listed above, unless someone else has any suggestions on how to get one. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-19-generic 6.11.0-19.19 ProcVersionSignature: Ubuntu 6.11.0-19.19-generic 6.11.11 Uname: Linux 6.11.0-19-generic x86_64 ApportVersion: 2.30.0-0ubuntu4.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/seq:reya 3892 F pipewire - /dev/snd/controlC0: reya 3897 F wireplumber + USERPID ACCESS COMMAND + /dev/snd/seq:reya 3892 F pipewire + /dev/snd/controlC0: reya 3897 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 17 19:58:31 2025 InstallationDate: Installed on 2025-02-03 (42 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: System76 Darter Pro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-19-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-6.11.0-19-generic N/A - linux-backports-modules-6.11.0-19-generic N/A - linux-firmware 20240913.gita34e7a5f-0ubuntu2.5 + linux-restricted-modules-6.11.0-19-generic N/A + linux-backports-modules-6.11.0-19-generic N/A + linux-firmware 20240913.gita34e7a5f-0ubuntu2.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2024 dmi.bios.release: 0.0 dmi.bios.vendor: coreboot dmi.bios.version: 2024-09-11_351d80d dmi.board.name: Darter Pro dmi.board.vendor: System76 dmi.board.version: darp10 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2024-09-11_351d80d:bd08/06/2024:br0.0:efr0.0:svnSystem76:pnDarterPro:pvrdarp10:rvnSystem76:rnDarterPro:rvrdarp10:cvnSystem76:ct9:cvr:sku: dmi.product.name: Darter Pro dmi.product.version: darp10 dmi.sys.vendor: System76 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103472 Title: Kernel panic on lengthy filesystem access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103470] [NEW] kdump does not reserve enough memory for disk encryption unless the system has 64GB+ memory
Public bug reported: Ubuntu 24.10 kdump-tools 1:1.10.3ubuntu4 I would expect that with crash dumps enabled, the crash dumper would be able to collect the information it needs and reboot with a minimum of information being input from me - and communicate clearly to me what it needs and why. However, the kdump-tools crashkernel gets only 1GB of memory reserved for it by default with 64GB of system memory, since the actual usable total falls *slightly* under 64GB with some memory reserved by the BIOS. This is not enough for disk encryption to start, causing the crashkernel to provide a LUKS password screen that can never be satisfied due to having insufficient memory to start. This is an extremely confusing user experience. It's not clear why the encryption password is being asked for again in the first place - let alone why the system doesn't have enough memory to start encryption. The memory usage issue is something that the kdump-tools package should presumably be able to understand (that the root filesystem is going to need LUKS and that it is going to need to be able to supply enough memory to meet LUKS's demands). But at the very least, the installer should know to inform kdump-tools that it's going to need more memory. I didn't set up kdump-tools OR LUKS - I only asked the installer to set up the latter, and the former is enabled by default. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: kdump-tools 1:1.10.3ubuntu4 ProcVersionSignature: Ubuntu 6.11.0-19.19-generic 6.11.11 Uname: Linux 6.11.0-19-generic x86_64 ApportVersion: 2.30.0-0ubuntu4.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 17 20:02:32 2025 InstallationDate: Installed on 2025-02-03 (42 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) SourcePackage: kdump-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kdump-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103470 Title: kdump does not reserve enough memory for disk encryption unless the system has 64GB+ memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2103470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103472] [NEW] Kernel panic on lengthy filesystem access
Public bug reported: Because of https://bugs.launchpad.net/ubuntu/+source/kdump- tools/+bug/2103470 and https://bugs.launchpad.net/ubuntu/+source/kdump- tools/+bug/2103471, I *still* cannot get a kernel crash dump for this bug. However, it's pretty clear that this is a kernel panic. Curiously, it appeared in both (a Live CD of) Ubuntu 24.04 and (my current installation of) Ubuntu 24.10. The current kernel is 6.11.0-19-generic. I would expect that simple filesystem operations like rsync -Pvach /some/exfat/filesystem/ /some/ext4/filesystem and cp -ar /some/exfat/filesystem/ /some/exfat/filesystem and rsync -Pvach /some/exfat/filesystem/ user@server:/destination/directory and even diff --recursive /some/exfat/filesystem/ /some/ext4/filesystem would not cause the system to kernel panic under any circumstances, and would instead produce userspace errors. However, consistently, after doing one of these tasks for a while, the kernel panics. Again, I'm unable to determine the nature of the kernel panic due to kdump-tools bugs listed above, unless someone else has any suggestions on how to get one. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-19-generic 6.11.0-19.19 ProcVersionSignature: Ubuntu 6.11.0-19.19-generic 6.11.11 Uname: Linux 6.11.0-19-generic x86_64 ApportVersion: 2.30.0-0ubuntu4.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:reya 3892 F pipewire /dev/snd/controlC0: reya 3897 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 17 19:58:31 2025 InstallationDate: Installed on 2025-02-03 (42 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: System76 Darter Pro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-19-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.11.0-19-generic N/A linux-backports-modules-6.11.0-19-generic N/A linux-firmware 20240913.gita34e7a5f-0ubuntu2.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2024 dmi.bios.release: 0.0 dmi.bios.vendor: coreboot dmi.bios.version: 2024-09-11_351d80d dmi.board.name: Darter Pro dmi.board.vendor: System76 dmi.board.version: darp10 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2024-09-11_351d80d:bd08/06/2024:br0.0:efr0.0:svnSystem76:pnDarterPro:pvrdarp10:rvnSystem76:rnDarterPro:rvrdarp10:cvnSystem76:ct9:cvr:sku: dmi.product.name: Darter Pro dmi.product.version: darp10 dmi.sys.vendor: System76 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103472 Title: Kernel panic on lengthy filesystem access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103472] Re: Kernel panic on lengthy filesystem access
Virtual machine definition used to reproduce the kernel panic: ** Attachment added: "VM definition for libvirt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103472/+attachment/5865666/+files/ubuntu24.10.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103472 Title: Kernel panic on lengthy filesystem access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103472] Re: Kernel panic on lengthy filesystem access
** Attachment added: "crash utility analysis of the core dump from KVM" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103472/+attachment/5865667/+files/crash.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103472 Title: Kernel panic on lengthy filesystem access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103471] [NEW] kdump starts into ash instead of collecting a kernel core dump (encrypted rootfs)
Public bug reported: Because of https://bugs.launchpad.net/ubuntu/+source/kdump- tools/+bug/2103470, this bug was obscured to me until I increased my system's total RAM to 96GB, at which point kdump-tools could finally get this far. Ubuntu 24.10 kdump-tools 1:1.10.3ubuntu4 I would expect the kernel crash dump collector to start up, collect a crash dump, and then either reboot or put up signposting indicating that it has finished collecting a crash dump and is ready to reboot when I'd like it to do so. Instead, however, it starts into a Busybox shell (ash). This is after decrypting the encrypted root and registering the LVM VG underneath, but before actually _mounting_ the (ext4) LV. I'm able to mount these on /root, which silences some of the errors, but the rescue environment then tells me that it cannot start '' and the crash kernel itself panics because init has died. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: kdump-tools 1:1.10.3ubuntu4 ProcVersionSignature: Ubuntu 6.11.0-19.19-generic 6.11.11 Uname: Linux 6.11.0-19-generic x86_64 ApportVersion: 2.30.0-0ubuntu4.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 17 19:59:45 2025 InstallationDate: Installed on 2025-02-03 (42 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) SourcePackage: kdump-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kdump-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103471 Title: kdump starts into ash instead of collecting a kernel core dump (encrypted rootfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2103471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
