Re: IBM Workpad z50 dmesg collection

...on Fri, May 21, 2021 at 01:27:54PM +0100, David Brownlee wrote:

 > http://sync.absd.org/hpcmips/ has 2017-01-01, 2018-01-01 and
 > 2018-07-01 kernels right now, more may drop in as builds complete. I'm

Oof, ok, this is going to take some time :)

Up to now, I tried the 2017-01-01, 2017-02-01, 2017-03-01 kernels.
Pcmcia seems fine with those three, but the userland troubles are 
present in all of them.

If I try to boot to multi-user, ntpdate will crash, and some things  
past that will hang (while some don't - if I happen to get through 
to inetd, I can actually log in via telnet?). 
In single-user, I can poke around for some time, then something will 
segfault, and after that more and more parts die, until I apparently 
lose the getty too at some point.

From a serial console log with 2017-03-01 (I disabled some of the 
more time consuming tasks from the startup procedure to make it 
slightly less tedious):

--- cut ---
Starting network.
Hostname: z50.rfc1918
IPv6 mode: host
Configuring network interfaces: ne0ISA IRQ 3 -> vrgiu0 port 9, level high through
pcmcia0: card irq 3
.
Adding interface aliases:.
Waiting for DAD completion for statically configured addresses...
Starting dhcpcd.
vrpiu:AD: 962, 104, 1
Building databases: dev, utmp, utmpx.
Starting syslogd.
Setting date via ntp.
[1]   Segmentation fault (core dumped) ${command} ${rc_...
/etc/rc.d/ntpdate exited with code 1
Mounting all file systems...
Clearing temporary files.
vrpiu:AD: 965, 105, 0
Updating fontconfig cache: done.
Checking quotas: done.
Setting securelevel: kern.securelevel: 0 -> 1
swapctl: setting dump device to /dev/wd0b
Starting virecover.
vrpiu:AD: 963, 103, 0
vrpiu:AD: 963, 104, 0
vrpiu:AD: 963, 103, 2
vrpiu:AD: 965, 101, 0
^C
/etc/rc.d/virecover terminated with signal 2
vrpiu:AD: 967, 103, 0
vrpiu:AD: 967, 103, 0
^C
Starting local daemons:.
Updating motd.
^CStarting inetd.
Starting cron.
vrpiu:AD: 963, 103, 2
--- cut ---

Again, this doesn't happen on 7.0.2 or 7.1.2

Regards,

Alex.