On Sun, Mar 26, 2017 at 08:42:43PM +0300, Anton Zinoviev wrote: >> I have done some more experimentation and it shows fairly >> strange results. > > Thanks a lot! :)
That is what I can contribute. > > Sometimes cached_setup_font.sh does not seem to get run AT > > ALL -- the log file simply does not exist after a clean boot. > > Maybe this happened because cached_setup_font.sh was run while / was > still read-only? Possibly. Suspecting that is why I chose / in the hope it'll get mounted rw real early :-) > > However, as witnessed by this log snippet from the most > > recent boot, it does not ALWAYS run in parallel: > > Let us clear one point: no matter whether it runs in parallel or not -- > the console is never configured properly? Or sometimes it is? It is NEVER configured properly anymore. It used to always work until fairly recently (shortly before I filed the bug) but now _never_ does, regardless of whether I can find a log under /. One thing I *haven't* tested yet is whether earlier kernel would make a difference -- not that I would think but who knows. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346