Le 04/05/2021 à 16:59, Christian Zigotzky a écrit :
Am 04.05.21 um 16:41 schrieb Christophe Leroy:
Le 04/05/2021 à 13:02, Christian Zigotzky a écrit :
Am 04.05.21 um 12:07 schrieb Christian Zigotzky:
Am 04.05.21 um 11:49 schrieb Christophe Leroy:
Le 04/05/2021 à 11:46, Christian Zigotzky a écrit :
Am 04.05.21 um 11:11 schrieb Christophe Leroy:
Le 04/05/2021 à 11:09, Christian Zigotzky a écrit :
Am 04.05.21 um 10:58 schrieb Christophe Leroy:
Le 04/05/2021 à 10:29, Christian Zigotzky a écrit :
On 04 May 2021 at 09:47am, Christophe Leroy wrote:
Hi
Le 04/05/2021 à 09:21, Christian Zigotzky a écrit :
Hi Christophe,
Thanks for your answer but I think I don't know how it works with the
cherry-pick.
$ git bisect start
As you suspect the problem to be specific to powerpc, I can do
git bisect start -- arch/powerpc
$ git bisect good 68a32ba14177d4a21c4a9a941cf1d7aea86d436f
$ git bisect bad c70a4be130de333ea079c59da41cc959712bb01c
You said that powerpc-5.13-1 is bad so you can narrow the search I think:
git bisect bad powerpc-5.13-1
git bisect good 887f3ceb51cd3~
I tried it but without any success.
git bisect bad powerpc-5.13-1
Output:
fatal: Needed a single revision
Bad rev input: powerpc-5.13-1
I don't understand, on my side it works. Maybe a difference between your version of git and
mine.
In that case, just use the SHA corresponding to the merge:
git bisect bad c70a4be130de333ea079c59da41cc959712bb01c
Christophe
Do you use a BookE machine?
No I don't unfortunately, and I have tried booting in QEMU a kernel built with your config,
but it freezes before any output.
You can use my kernels and distributions.
Ok, I'll see if I can do something with them.
In the meantime, have you been able to bisect ?
Thanks
Christophe
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).
