Note for everyone that wants to retry, follow https://wiki.ubuntu.com/RISC-V which works fine in e.g. a hirsute LXD container without messing anything up in your main system.
After eliminating all of the postinst and config this can be triggered by the test-for-startability call like: $ mysqld --verbose --help --innodb-read-only terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc 07:55:23 UTC - mysqld got signal 6 ; Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x46000 /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x62) [0x2ae71187d0] /usr/sbin/mysqld(handle_fatal_signal+0x270) [0x2ae649fe64] linux-vdso.so.1(__vdso_rt_sigreturn+0) [0x3fe1fba800] /lib/riscv64-linux-gnu/libc.so.6(gsignal+0xa2) [0x3fe13f9fec] /lib/riscv64-linux-gnu/libc.so.6(abort+0xb4) [0x3fe13ea98c] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915275 Title: mysql-8.0 regressed on riscv64 due to new glibc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1915275/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
