Systemd system, x86_64 architecture, I don't remember all the errors but one of them explicitly said "kernel panic". It happened after rebooting after an update and did a kernel panic immediately upon every boot. Machine was new probably three years ago, so not too old.

I tried reinstalling the systemd version and that failed due to kernel errors. I tried again a few hours ago and now it installs okay, but has a problem with the wired internet connection (probably an unrelated bug?), which is functional during the installer. Explicitly, if I ping 8.8.8.8 it succeeds, but

ping -c 3 gnu.org

gives the error:

temporary failure in name resolution

The dhcpcd service is enabled.

I'm able to get an openrc install with working internet, but I'd prefer to use systemd because it has better documentation.

Then this is no longer a kernel panic bug?

do you have a systemd system installed still.
If so what does cat /etc/resolv.conf show?
What network manager are you using? netctl, wicd, networkmanager
This sounds like a DNS failure. Or a failure to pickup the DNS settings from dhcp correctly

cat /etc/resolv.conf

gives:

1. Generated by NetworkManager
   nameserver 75.75.75.75
   nameserver 75.75.76.76
   nameserver 2001:558:feed::1
2. NOTE: the libc resolver may not support more than 3 nameservers.
3. The nameservers listed below may not be recognized.
   nameserver 2001:558:feed::2

what happens if you:

nslookup gnu.org

nslookup gnu.org 75.75.75.75

Also what class of MODEl of CPU is it a as in i3, i5, i7, pentuim, etc

want to know #1967 may have been involved

If you can no longer reproduce the kernel panic I should mark this bug report as invalid

Network configuration is an entirely different issue.

also which kernel?

Nevermind, this is nonsense. The output I just gave was from the live version, chrooted in. I assumed the command would show the contents of /etc/resolv.conf on the disk, but when I checked it from inside the actual install (not just chrooted) it was blank. In fact, networkmanager wasn't even installed, so of course there's going to be a problem. In the past I never actually needed to explicitly install networkmanager, so I guess it was in the "base" group previously and recently removed.

I'm really sorry for wasting your time, and genuinely appreciate your help.

I'll leave this open until some time tomorrow in case you have another panic. If so please report it. If not I'll mark this invalid