Yes, could be. There are so many things that can have unexpected effects. There are certainly limiting factors with the likes of copy2ram, and for simplicity the (default) scripts purposively include no complex logic bound checkings of any sort (though users are encouraged to tweak these accordingly). The zram additions will increase the possibilities of such issues for sure, but, then again, these additions will all be no more than optional (and sometimes such additions may actually help with issues). We make what we can of it.rufwoof wrote:Seems to be due to the changes=ram boot parameter, without that it boots OK. Suspecting its the mount -o mode=1777,nosuid,nodev,size=xxx tweak combined with a borderline size of my build (chromium, libreoffice etc.). Currently I've cpio extracted and changed init to exclude the size=xxx and I'm reforming the sfs using xz compression to see if that squeezes in. Suspecting some form of boundary/buffer overrun that is avoided when hdd frugal booted but that gets hit when booted via usb3. But that's just a guess. If so, perhaps using zram and suchlike could be inclined to potentially introduce difficult to identify/resolve issues (something to be wary of).
On the otherhand, sometimes the reason for a bug is straighforward and staring us in the face but takes us a while to see and understand it.
wiak