On Fri, 3 Jun 2016, John Paul Adrian Glaubitz wrote:
> >
> > And I'm getting "Failed to execute operation: Connection timed out"
> > from systemctl, and other systemd weirdness like a shutdown hang.
>
> This is actually a known issue in systemd and fixing it is still on my
> TODO list, I just forget it. The problem here is that the dbus timeout
> in systemd is sometimes insufficiently low when running on old m68k
> Macs. I have also talked with Lennart about this and he has no problems
> improving that to make it work on m68k hardware.
>
Yes, systemd is very slow to boot on this system, so timeouts are likely
to be the problem. Immediately after booting it and logging in at ttyS0, I
see that PID 1 has already consumed over 2 CPU minutes (for comparison, ps
consumed 2 CPU seconds).
root@pacman:~# ps -cHA
PID CLS PRI TTY TIME CMD
2 TS 19 ? 00:00:00 kthreadd
3 TS 19 ? 00:00:12 ksoftirqd/0
4 TS 19 ? 00:00:00 kworker/0:0
5 TS 39 ? 00:00:00 kworker/0:0H
6 TS 19 ? 00:00:00 kworker/u2:0
7 TS 19 ? 00:00:00 kworker/u3:0
8 FF 139 ? 00:00:00 watchdog/0
9 TS 39 ? 00:00:00 khelper
10 TS 19 ? 00:00:00 kdevtmpfs
11 TS 39 ? 00:00:00 netns
12 TS 19 ? 00:00:00 khungtaskd
13 TS 39 ? 00:00:00 writeback
14 TS 39 ? 00:00:00 bioset
15 TS 39 ? 00:00:00 kblockd
16 TS 39 ? 00:00:00 rpciod
17 TS 19 ? 00:00:00 kworker/0:1
18 TS 19 ? 00:00:11 kswapd0
19 TS 19 ? 00:00:00 fsnotify_mark
20 TS 39 ? 00:00:00 nfsiod
21 TS 19 ? 00:00:43 kworker/u2:1
26 TS 19 ? 00:00:00 scsi_eh_0
27 TS 39 ? 00:00:00 scsi_tmf_0
28 TS 39 ? 00:00:00 ncr5380_0
30 TS 29 ? 00:00:00 aoe_tx0
31 TS 29 ? 00:00:00 aoe_ktio0
32 TS 39 ? 00:00:00 deferwq
33 TS 39 ? 00:00:00 ext4-rsv-conver
34 TS 39 ? 00:00:00 kworker/0:1H
52 TS 19 ? 00:00:00 kworker/0:2
83 TS 19 ? 00:00:00 kworker/0:3
1 TS 19 ? 00:02:05 systemd
50 TS 19 ? 00:00:30 systemd-journal
63 TS 19 ? 00:00:10 systemd-udevd
146 TS 19 ? 00:00:01 cron
148 TS 19 ? 00:00:04 rsyslogd
152 TS 19 tty1 00:00:03 agetty
153 TS 19 ttyS0 00:00:05 login
167 TS 19 ttyS0 00:00:04 bash
173 TS 19 ttyS0 00:00:02 ps
root@pacman:~#
root@pacman:~#
> You see the timeout, but the actual systemctl should be effective
> nevertheless.
>
> > I also tried to fetch ntpdate_4.2.8p7+dfsg-4_m68k.deb but wget fails
> > with "Read error at byte 0/63850 (Invalid argument)".
>
> How did you try to fetch it?
root@pacman:~# wget
http://ftp.ports.debian.org/debian-ports/pool-m68k/main/n/ntp/ntpdate_4.2.8p7+dfsg-4_m68k.deb
converted
'http://ftp.ports.debian.org/debian-ports/pool-m68k/main/n/ntp/ntpdate_4.2.8p7+dfsg-4_m68k.deb'
(ANSI_X3.4-1968) ->
'http://ftp.ports.debian.org/debian-ports/pool-m68k/main/n/ntp/ntpdate_4.2.8p7+dfsg-4_m68k.deb'
(UTF-8)
--1970-01-01 04:45:18--
http://ftp.ports.debian.org/debian-ports/pool-m68k/main/n/ntp/ntpdate_4.2.8p7+dfsg-4_m68k.deb
Resolving ftp.ports.debian.org (ftp.ports.debian.org)... 130.89.148.14,
149.20.20.22, 2001:610:1908:b000::148:14, ...
Connecting to ftp.ports.debian.org (ftp.ports.debian.org)|130.89.148.14|:80...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 63850 (62K) [application/x-debian-package]
Saving to: 'ntpdate_4.2.8p7+dfsg-4_m68k.deb.1'
ntpdate_4.2.8p7+dfs 0%[ ] 0 --.-KB/s in 0s
1970-01-01 04:45:24 (0.00 B/s) - Read error at byte 0/63850 (Invalid argument).
Retrying.
--1970-01-01 04:45:25-- (try: 2)
http://ftp.ports.debian.org/debian-ports/pool-m68k/main/n/ntp/ntpdate_4.2.8p7+dfsg-4_m68k.deb
Connecting to ftp.ports.debian.org (ftp.ports.debian.org)|130.89.148.14|:80...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 63850 (62K) [application/x-debian-package]
Saving to: 'ntpdate_4.2.8p7+dfsg-4_m68k.deb.1'
ntpdate_4.2.8p7+dfs 0%[ ] 0 --.-KB/s in 0s
1970-01-01 04:45:26 (0.00 B/s) - Read error at byte 0/63850 (Invalid argument).
Retrying.
The same wget command works fine on my Linux/x86 laptop (which is also
running a custom kernel but is not running Debian unstable). Is kernel
support for IPv6 madatory in Debian unstable?
>
> > Next up I will have to try to build an equivalent Atari kernel and
> > test the same filesystem on Aranym, or else somehow try to fetch and
> > install a Debian kernel on this 68030 system.
> >
> > Adrian, if you debootstrap and publish a more up-to-date root
> > filesystem, I suggest that /etc/resolv.conf and /etc/apt/sources.list
> > should use Google DNS and ftp.ports.debian.org respectively.
>
> Yeah, will do that later today. Was planning to do that anyway.
Thanks. Perhaps the new debootstrap will fix the wget error.
I would also like to try the Debian kernel at
http://ftp.de.debian.org/debian-ports/pool-m68k/main/l/linux/linux-image-4.5.0-2-m68k_4.5.5-1_m68k.deb
but it is not possible to boot a Debian kernel without an initrd
containing all the kernel modules. But apt-get is not working for me...
root@pacman:~# apt-get install linux-image-m68k
Reading package lists... 65%
Segmentation fault
>
> Any wishes for additional, pre-installed packages?
Would it help to pre-install linux-image-m68k? That is, would it cause a
usable initrd to be generated? Otherwise perhaps I could generate that for
myself after I boot a custom kernel.
ntpdate is always useful for old machines that may have no clock battery
(as old batteries tend to leak acid) or have no RTC support in the kernel,
which is the case for certain Mac models.
In general I would choose lightweight package alternatives (sysvinit, ucb
vi, busybox etc.) but that isn't going to suit most d.p.o users, as the
relevant hardware is usually more powerful than this Mac LC III, with 20
MB RAM and a 25 MHz 68030.
BTW, I see that the Debian kernel config sets CONFIG_MAC_SCSI=y. As of
v3.19 you can make that driver modular and save memory on systems that
don't need it like Atari, Amiga and 68040 Macs. Similarly,
CONFIG_MAC8390=y can be made modular as of v4.4.
--
