[artix-general] [s6] not booting/rebooting laptop

[Javier]

I believe I found the issue, and it's the order on which S6 shutdowns dhcpcd vs. wpa_supplicant.

The reason I didn't have the reboot/poweroff issues on other boxes is that I didn't enabled wpa_supplicant on them.  And in fact on another Toshiba laptop where I enabled wpa_supplicant, I found the same issue.

See, if wpa_supplicant is not enabled, then I can shut dhcpcd down and turn it up, and then down and up again, as many times as I want.  The bottom line is that dhcpcd just shutdowns fine.

If I enable wpa_supplicant, then I can shut wpa_supplicant down and turn it up, and then down and up again, also as many times as I want.

With wpa_supplicant enabled, if I 1st shut wpa_supplicant down, and then I shut dhcpcd down, and then turn dhcpcd up, and then I turn wpa_supplicant up, and then I can keep repeating that process without issues as many times as I want.

However, with wpa_supplicant enabled, if I 1st shut dhcpcd down, 1st it automatically makes wpa_supplicant shut down, which makes sense, since wpa_supplicant depends on dhcpcd.  But after wpa_supplicant shuts down, dhcpcd just hangs, and it never shuts down.

Having wpa_supplicant enabled, I tried both, without dhcpcd being part of the default bundle, and with dhcpcd being part of the default bundle (I forced shutdowns in the middle, so that the system started with the default bundle I wanted to test, and then performed the tests).  There's no difference on whether dhcpcd is part of the default bundle or not.  This sounds fine since whether dhcpcd is part of the default bundle or not, it gets enabled any ways, whether by wpa_supplicant in one case, or by the same wpa_supplicant reason or by being part of the default bundle in the other (whatever gets turned up 1s by S6 in the last case).

I think what happens is that "s6-rc -bda change" gets to shut dhcpcd down before or at the same time than wpa_supplicant (at the same time is possible if doing stuff in parallel), and that causes issues.  It seems dhcpcd is handling fine being a dependency for wpa_supplicant, since it's shutting down wpa_supplicant before the dhcpcd shutting down is attempted, but it hangs afterwords, so there's an issue with dhcpcd and wpa_supplicant.

BTW, I also noticed this with the recent upgrade of s6-scripts (20200918-1 -> 20200923-1), s6-linux-init (1.0.4.1-2 -> 1.0.4.2-1) and the removal of eudev-s6.  The upgrade just hanged, and I had to break it (ctrl-c), and when doing so, there was a message on failing to shut the dhcpcd service, though the removal of udev-s6 succeeded after the break.  I guess the removal of the eudev service caused other services depending on it, as the dhcpcd one, to shut down, to then be brought up back once s6-scripts got upgraded.  So I had to upgrade again, and to make sure, I also installed all packages on that upgrade manually...

So, what do you think @Dudemanguy?  Any way to deal with this order of dhcpcd vs. wpa_supplicant getting shut down, or specify that particular order to S6?

-- 
Javier

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <https://lists.artixlinux.org/archives/artix-general/attachments/20200926/ea51d16c/attachment.sig>