-
Bug
-
Resolution: Fixed
-
Major
-
Quillback Milestone 3
jsmoeller noticed the databroker crashing with a coredump while setting up the FOSDEM demo with the HiFive Unmatched board. I can reproduce it with the qemuriscv64 build:
Feb 12 18:57:26 qemuriscv64 kernel: tokio-runtime-w[1965]: unhandled signal 11 code 0x1 at 0x0000000000000000 in databroker[2ac9948000+490000] Feb 12 18:57:26 qemuriscv64 kernel: CPU: 3 PID: 1965 Comm: tokio-runtime-w Not tainted 5.15.124-yocto-standard #1 Feb 12 18:57:26 qemuriscv64 kernel: Hardware name: riscv-virtio,qemu (DT) Feb 12 18:57:26 qemuriscv64 kernel: epc : 0000002ac9c4e882 ra : 0000002ac9c4caaa sp : 0000003fbd880280 Feb 12 18:57:26 qemuriscv64 kernel: gp : 0000002ac9e36d28 tp : 0000003fbd8818e0 t0 : 9550ad9d30000000 Feb 12 18:57:26 qemuriscv64 kernel: t1 : 0000000000000403 t2 : 0000000000040000 s0 : 0000000000000000 Feb 12 18:57:26 qemuriscv64 kernel: s1 : 0000000000000000 a0 : 0000000000000000 a1 : 0000002ac9e48a60 Feb 12 18:57:26 qemuriscv64 kernel: a2 : 0000000000000000 a3 : 0000000000000000 a4 : 0000000000000000 Feb 12 18:57:26 qemuriscv64 kernel: a5 : 0000000000000000 a6 : 0000000000000400 a7 : 0000000000000000 Feb 12 18:57:26 qemuriscv64 kernel: s2 : 0000003fbd8803f8 s3 : 0000003fbd8803f0 s4 : 0000003fbd8803d0 Feb 12 18:57:26 qemuriscv64 kernel: s5 : 0000002ac9e48970 s6 : 0000002ac9e489b0 s7 : 0000000000000003 Feb 12 18:57:26 qemuriscv64 kernel: s8 : 0000000000000001 s9 : 0000002ac9e49620 s10: 0000002ac9e48a40 Feb 12 18:57:26 qemuriscv64 kernel: s11: 0000000000000001 t3 : 403f000000000000 t4 : 0035e68fbcf54610 Feb 12 18:57:26 qemuriscv64 kernel: t5 : ffffffffffffffff t6 : 00000002a0ca08a9 Feb 12 18:57:26 qemuriscv64 kernel: status: 0000000000004020 badaddr: 0000000000000000 cause: 000000000000000d Feb 12 18:57:26 qemuriscv64 audit[1961]: ANOM_ABEND auid=4294967295 uid=900 gid=900 ses=4294967295 subj=system_u:system_r:initrc_t:s0 pid=1961 comm="tokio-runtime-w" exe="/usr/bin/databroker" sig=11 res=1
I believe this was not happening when we first pulled in the kuksa-val 0.4.2 release to get the RISC-V build support, so perhaps it is related to the upgrade to Rust 1.70.