Hi Christophe, Ok, so let's summarise from my side.
The issue is in the PowerPC updates 5.13-1. I reverted these and after that the issue is gone. We know that only BookE machines are affected. Book3S machines are working with the PowerPC updates. I think it’s not directly an Xorg issue. It’s more a symptom that Xorg restarts again and again. In my point of view the changes for BookE machines in the PowerPC updates are responsible for this issue. Bisecting costs a lot of time and I don’t have time for my main work anymore. Bisecting is good but sometime you have to check your code yourself. We know all facts and now it’s time to check the code because of BookE compatibility. @All You can test it with QEMU as well. I provide some virtual machines and kernels for testing. Guys, it is really important that you test your changes before you release them. Thanks, Christian > On 6. May 2021, at 08:13, Christophe Leroy <christophe.le...@csgroup.eu> > wrote: > > > >> Le 05/05/2021 à 14:43, Christian Zigotzky a écrit : >>> On 04 May 2021 at 05:17pm, Christophe Leroy wrote: >>> Le 04/05/2021 à 16:59, Christian Zigotzky a écrit : >>>> On 04 May 2021 at 04:41pm Christophe Leroy wrote: >>>>> Le 04/05/2021 à 13:02, Christian Zigotzky a écrit : >>>>>> On 04 May 2021 at 12:07pm, Christian Zigotzky wrote: >>>>>>> On 04 May 2021 at 11:49am, Christophe Leroy wrote: >>>>>>> >>>>>>> I am bisecting currently. >>>>>>> >>>>>>> $ git bisect start -- arch/powerpc >>>>>>> $ git bisect good 887f3ceb51cd3~ >>>>>>> $ git bisect bad c70a4be130de333ea079c59da41cc959712bb01c >>>>>> OK, there is another issue after the second bisecting step. The boot >>>>>> stops after loading the dtb and uImage file. I can't solve 2 issues with >>>>>> bisecting at the same time. >>>>> >>>>> In that case, you can use 'git bisect skip' to skip the one that is not >>>>> booting at all. >>>> In my point of view 'git bisect skip' isn't a good idea because I will not >>>> find out if the skipped commit is good or bad and maybe the first bad >>>> commit. >>> >>> The second problem may be completely unrelated to the first one so it could >>> work. >>> >>> In any case, if 'git bisect' finds out that the bad commit is in the middle >>> of a skipped area, it will tell you. So I think it is worth it. >>> >>> The second solution could be to first focus on that 'boot stops after >>> loading problem' and try to find out which commit introduces the bug, then >>> which one fixes it. But it may not be necessary. >>> >>> Other solution, as you were thinking that the conversion of 'booke' to C >>> interrupt entry/exit, you can also try around that: See if d738ee8 has the >>> problem and 2e2a441 doesn't have the problem. >>> >>> If so, you can bisect between those two commits (There are 8 commits >>> inbetween). >> Hi Christophe, >> I am bisecting with skipping the boot issue currently. Unfortunately it >> seems there is another bug. I had to skip two times because the kernel >> didn't compile. > >> Should I continue bisecting? >> You can find the other steps (21 and higher) here: >> https://forum.hyperion-entertainment.com/viewtopic.php?p=53103#p53103 > > Ok, so let's summarise: > > 887f3ceb51cd = Xorg doesn't work > 887f3ceb51cd is the "first bad commit" identified by your first "bisect" > 887f3ceb51cd~ = 627b72bee84d works ok > c70a4be130de = Xorg doesn't work > > Can you check that 887f3ceb51cd with cherry-picked 525642624783 has Xorg > working ? > > Can you provide 'git bisect log' ? > > It seems there is some mismatch between the commit and the description. For > instance, you say fd6db2892eba and 14b3c9d24a7a don't build. I see no reason > for that, I agree there is that build failure but with dc6231821a14, > 0c2472de23ae, 3db8aa10de9a and 097157e16cf8. That is fixed by ceff77efa4f8. > Note that that build failure should not occur if you have > CONFIG_CONTEXT_TRACKING, but it is not our problem for the time being. > > Anyway, what I learn from your details is: > > 56bec2f9d4d0 is the first one you tested which stops after loading the dtb > and uImage. > > Can you bisect between 887f3ceb51cd[good] and 56bec2f9d4d0[bad] to identify > first bad commit that stops after loading the dtb and uImage ? > > Once that first bad commit is identified, can you check whether the > preceeding commit with cherry-picked 525642624783 has Xorg working or not ? > > > ceff77efa4f8 is the last one you tested which stops after loading the dtb and > uImage. > 49c1d07fd04f is bad (Xorg not working) > > Can you bisect between ceff77efa4f8[good] and 49c1d07fd04f[bad] to identify > first commit that doesn't stop after loading the dtb and uImage ? (Here you > have to make a mental exercice: > the ones that stop after loading dtb/uImage are the 'good' and the ones > booting OK are the 'bad') > > Once you have found out what breaks booting and what makes it work again, > then we should be able to progress on the investigation. > > Thanks > Christophe
