Conversation

Daniel Micay
@DanielMicay
twitter.com/GrapheneOS/sta Going to be switching to doing release builds on the new Ryzen 5950X build because this old workstation is severely haunted. We've never had an issue like this. Build and signing was otherwise completely reproducible but somehow a directory wasn't made.
Quote Tweet
GrapheneOS
@GrapheneOS
The issue has been resolved with a rebuild. The firmware images are identical, as is every single file in each of the OS images other than an expected signing metadata difference. Only actual difference is /firmware_mnt somehow wasn't created in the vendor image for broken build.
Show this thread
1
9
Daniel Micay
@DanielMicay
It's quite possible this nonsense is caused by USB triggering kernel memory corruption. I've been increasingly having problems with USB on the old workstation. I was setting up having all the phones plugged in and ready during the builds. USB corrupting ext4 memory? Who knows.
Twitter Web App
4
Likes
Daniel Micay
@DanielMicay
Replying to
@DanielMicay
Could also be caused by memory bit flip but I doubt it. I'm blaming USB. I get tons of kernel panics from USB. Having a dozen phones plugged into the computer and tests running on some of them is a nice stress test for the Linux kernel USB stack and it fails on a daily basis.
2
6