As usually the schematics were available in the manual it was not too hard to add some additional static ram. There were unused address lines available which could be used for chip select.
a) Do these inode issues also happen with the supplied (v4) kernel?
b) Do these inode issues also happen with a rebuilded kernel which uses the original lib1 and lib2?
I once had strange effects on V6 if lib1 and/or lib2 were rebuild by me.
In my experience, yes: always happens. So far i have not found a way to mount multiple disks without getting these inode errors. And this is just v4, the nsys kernel doesn't even work with a single disk. i hope i'll get to the bottom of this in the near future.
If you want to use multiple technologies in a single project you should not run Goland, PhpStorm etc. but IntelliJ with plugins. Then you don't need to switch IDEs.
Well, this is left to the application developer to decide and the library should not make the choice for them. In my own application it makes sense to use time.Now(), for example.
The systemd config is default and it should dump core and logs a message that it dumped core but I have not been able to find it. Usually core dumps are in
/var/lib/systemd/coredump but the directory is empty.
The server has ECC memory and there are no messages in the syslog about ECC failures.
The SEGV occurred on two consecutive days when systemd was reloading so for the moment I find it unlikely that memory may be the root cause but looking at a core dump would certainly help. Where is it?
Have a look at the Teensy 4.1, it comes with 7936K Flash, 1024K RAM and you can even add up to 2x8Mb PSRAM iirc. Of course it's a bit more expensive but not much.
reply