> Gesendet: Dienstag, den 14.05.2024 um 17:21 Uhr > Von: "Debian Bug Tracking System" <ow...@bugs.debian.org> > An: scpcom <scp...@gmx.de> > Betreff: Bug#1070959 closed by Jessica Clarke <jrt...@debian.org> (Re: > Bug#1070959: /usr/lib/riscv64-linux-gnu/libapt-pkg.so.6.0.0: apt: riscv64: > sun20i-d1: http(s): unhandled signal 4 code 0x1 in libapt-pkg.so.6.0.0) > > This is an automatic notification regarding your Bug report > which was filed against the libapt-pkg6.0t64 package: > > #1070959: /usr/lib/riscv64-linux-gnu/libapt-pkg.so.6.0.0: apt: riscv64: > sun20i-d1: http(s): unhandled signal 4 code 0x1 in libapt-pkg.so.6.0.0 > > It has been closed by Jessica Clarke <jrt...@debian.org>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Jessica Clarke > <jrt...@debian.org> by > replying to this email. > > > -- > 1070959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070959 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems
> 0x8330000f is FENCE.TSO, which some of the T-Head cores notoriously > failed to implement, thereby violating the RISC-V spec. LLVM has > emitted it for a long time, but GCC didn’t until recently (14.1) so > without doing proper architectural testing, just running Linux on top > of it historically wouldn’t have revealed the issue. > > OpenSBI 1.1 (released June 2022) emulates the instruction for this > hardware, so update your firmware to a version that includes a > recent-ish version of OpenSBI and pretends your hardware is more > conforming. Thank you, I will try to integrate a newer OpenSBI into my setup.
