Thanks Peter. They appear different. I don't get a kernel panic, but rather a segv on a systemd-udevd thread related to eth0 that does not kill systemd-udevd nor create a kernel panic. After boot, a "udevadm trigger --type=devices --action=add" seems to succeed and bring eth0 up without error. Restarting systemd-udevd and issuing "udevadm trigger --type=subsystems --action=add" and "udevadm trigger --type=devices --action=add" also succeeds, brings up eth0, and no thread segv. I can not reproduce the segv after boot and I don't see an easy way to debug systemd-udevd in the middle of booting. By adding log messages, I can see the problem is in link-config.c. The looping through alternative_names_policy is failing. if I comment out that section of code, the system boots as expected. _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
