I can confirm the bug. The relevant part section of the log appears to be: KDump Default Enablement Criteria: CPU Architectures: x86_64 aarch64 s390x, CPU Threads >= 4, RAM/Swap: 6-2048 GB, Free Space in /var >= 5x RAM/Swap (40 GB) Hardware Found: CPU Architecture: unknown, CPU Threads: 4, Memory: 8 GB, Free space in /var: 91 GB KDump will be disabled.
The kdump_set_default script is reading the architecture with `uname -p` [0], which is returning a bad answer: $ uname -p unknown This fails in both the live environment and installed system. [0] https://git.launchpad.net/ubuntu/+source/kdump-tools/tree/debian/kdump_set_default#n21 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2125027 Title: kdump fails to enable on suitable system To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2125027/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
