Hi Fabio, Am So., 19. Sept. 2021 um 23:44 Uhr schrieb Fabio Estevam <festevam@xxxxxxxxx>: > > Hi Heiko, > > On Sun, Sep 19, 2021 at 4:33 PM Heiko Thiery <heiko.thiery@xxxxxxxxx> wrote: > > > > Does this patch help? > > > https://pastebin.com/raw/yZKz1huL > > > > I can confirm that on the next-20210915 (that includes commit > > 78e80c4b4238c1f5642b975859664fced4f9c69e) your provided patch solves > > the problem. > > Thanks for testing it. > > > But is it explainable that in the version before the commit > > 78e80c4b4238c1f5642b975859664fced4f9c69e the problem occurs in the > > form I reported? > > I don't understand this problem either. I would suggest bisecting it. Now it is clear to me. I used the dtb for my board that had already changed the phy node and tried to boot the "old" kernel 5.14. Thus no phy could be found. Nevertheless the kernel should not crash in case no phy was found. So I made a beginner's mistake here. But this also means that you can no longer start an old kernel with the changed dtb. This comes into play when you e.g. a standard distribution where the embedded dtb is passed from the uboot via EFI boot. -- Heiko
