Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
nina@q66@gts.q66.moe (2026-10-16 22:43:04)
considering getting riscv in chimera on the chopping block again because i'm not happy with the way things are at all
rn our builder is a milkv pioneer thing (kindly provided to us via remote access), the performance is fine enough but the hardware is severely buggy and broken and has draft rvv so we need custom kernel patches to hide rvv from the auxiliary vector in order to make stuff not pick up the rvv paths at runtime (as wherever we have those, they are rvv 1.0 and these share the same hwcap bit)
the worst part is probably that the nvme controller (or something else) dies regularly under load, resulting in the machine going unresponsive for remote access until someone reboots it (because the system stays up but the filesystem disappears); this happens every couple weeks
the machine has no bmc, so we can't reboot it ourselves, which resulted in me writing a little program that periodically tries to write to the filesystem and if it can't, it forces a hard reboot via syscall so that i can access it post-bringup again
the other worst part is that it runs fedora 38 and can't really do mainline anything which requires workarounds around outdated distro (fortunately cbuild/buildbot doesn't need that much) and i'm generally not happy with running old stuff like that
i checked what other hardware options there are today and it seems there isn't really anything else still that's not slower than a raspberry pi
yesterday the filesystem dying was bad enough that it booted into recovery shell; so i had to get the owner of the box to manually fsck it...
so idk... we don't really face stuff like this with any other architecture
---Reply---
nina@q66@gts.q66.moe (2026-10-17 00:50:43)
less than one hour from the point where we revived the box it died again
chat i think riscv might not be very good
Reply
---Replies---
Erin, the OSHA denialist@ekatwired@so.yuri.diy (2026-10-17 00:51:55)
@q66 Is that really RISC-V's fault?