On Sun, 31 Jul 2022 12:30:42 +0200, Diederik de Haas wrote: >From the partial logs you shared it appeared that your network also went down >after (quite) some time,
If you're referring to my 5.14.0-1 kernel log, I can't offer any insight, as I only tried that kernel briefly, nearly a year ago. If you mean the 5.10 kernel, let me clarify: 1. 5.10 reliably brings up eth0 early enough for dropbear sshd to work. 2. I ssh to dropbear, enter the LUKS passphrase, and the root filesystem is unlocked. 3. When eth0 fails, it's always shortly after that, still during system startup. 4. Once I notice, attach a serial terminal, and reload the kernel module, eth0 comes up and stays up. It doesn't go down again later. I find it curious that eth0 comes up reliably and then *sometimes* goes down shortly afterward. I don't know if it's completely random or something later in the startup process is triggering it. Obviously, a delay between eth0 first coming up and when it goes down could be partly from the time it takes me to ssh and type a LUKS passphrase. >What's odd then is that that commit has been applied/backported to the 5.10 >kernel under commit 97653ba562b9b28e30a3fcff42531e05a434d58c which is part of >5.10.82, so also 5.10.127-2 ... Ah, I didn't notice that patch having been backported with a different commit ID. Thanks for mentioning it.
