On Tue, Sep 4, 2018 at 2:10 PM, Lev Serebryakov <l...@freebsd.org> wrote: > Wednesday, September 5, 2018, 12:05:43 AM, you wrote: >> I think it is tripping on raise/abort() in one of these routines, but >> nothing is printing that information. See below. > > Maybe, it should be fixed?
Yes, it should. > One second after that random is ready to use and > newfs works as intended. It is, really, some race between early init script > (rc.initdiskless) and kernel. I don't think, that newfs must be > killed/aborted in such situation, it could wait! I agree. It looks like it is waiting, in fact, but then Something Bad Happens when the random device is unblocked. >> Ah, thanks. I missed this. mdmfs(8) has a bug in its run() function. >> It treats programs that exit with a signal (KILL, ABRT, ILL, SEGV...) >> the same as programs that exit with success. This is a (major) >> problem and the reason raise/abort is not visible. > > And it is another problem. But if it will be fixed, it doesn't help to init > system properly in my case, only diagnostic will be better. Yep. Best, Conrad _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
