Comment 4 for bug 1991441

I don't have anything of value to contribute, but I also ran into this exact same issue on an odroid HC2 (basically the same as an XU4 in a different form factor) upgraded from focal to jammy.

# /usr/sbin/glusterd --debug
[2023-06-24 04:18:36.664100 +0000] I [MSGID: 100030] [glusterfsd.c:2767:main] 0-/usr/sbin/glusterd: Started running version [{arg=/usr/sbin/glusterd}, {version=10.1}, {cmdlinestr=/usr/sbin/glusterd --debug}]
[2023-06-24 04:18:36.664220 +0000] I [glusterfsd.c:2447:daemonize] 0-glusterfs: Pid of current running process is 3913
[2023-06-24 04:18:36.664256 +0000] D [logging.c:1705:__gf_log_inject_timer_event] 0-logging-infra: Starting timer now. Timeout = 120, current buf size = 5
[2023-06-24 04:18:36.670335 +0000] D [MSGID: 0] [gf-io.c:513:gf_io_run] 0-io: Trying I/O engine 'legacy'
[2023-06-24 04:18:36.670377 +0000] D [MSGID: 0] [gf-io.c:517:gf_io_run] 0-io: I/O engine 'legacy' is ready
[2023-06-24 04:18:36.670603 +0000] D [logging.c:1675:gf_log_flush_extra_msgs] 0-logging-infra: Log buffer size reduced. About to flush 3 extra log messages
[2023-06-24 04:18:36.670634 +0000] D [logging.c:1681:gf_log_flush_extra_msgs] 0-logging-infra: Just flushed 3 extra log messages
pending frames:
patchset: git://git.gluster.org/glusterfs.git
signal received: 4
time of crash:
2023-06-24 04:18:36 +0000
configuration details:
argp 1
backtrace 1
dlfcn 1
libpthread 1
llistxattr 1
setfsid 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 10.1
---------
Illegal instruction (core dumped)
#

Out of curiosity, I installed the focal gluster 7.2 packages on jammy (I know, not the right thing to do, but I was interested as a test) and they work fine.