On Sun, 5 Jun 2016, I wrote: > On Sat, 4 Jun 2016, John Paul Adrian Glaubitz wrote: > > > On 06/04/2016 07:03 AM, Finn Thain wrote: > > > > > Yes, systemd is very slow to boot on this system, so timeouts are > > > likely to be the problem.
I've since found that the serial console on a 40 MHz 68040 sometimes fails in the same way. The timeout for 'dev-%i.device' seems to be covered by DefaultTimeoutStartSec. https://www.freedesktop.org/software/systemd/man/systemd-system.conf.html#DefaultTimeoutStartSec= So I set this to 180s in /etc/systemd/system.conf and haven't seen the problem since. [* ] A start job is running for dev-ttyS0.device (46s / 3min) > ... > > > 1970-01-01 04:45:26 (0.00 B/s) - Read error at byte 0/63850 (Invalid > > > argument). Retrying. > > > > Hmm, that's very odd. I haven't seen similar issues on my m68k > > machines. Is there a way to verify that the kernel itself works as > > expected? > > If I boot etch-m68k with the same kernel, the wget error is the same. It > still happens with the 'ipv6' module loaded. I'll have to do more > debugging. The wget error went away when I added a 68882 FPU chip. The seg fault during apt-get remains. When the next debootstrap becomes available I'll test again. --
