Le 04/05/2021 à 15:48, Christian Zigotzky a écrit :
Am 04.05.21 um 13:02 schrieb Christian Zigotzky:
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.
Xorg restarts again and again.
Here are some interesting error messages:
May 04 15:24:53 dc1.a-eon.tld kernel: lxsession[7255]: segfault (11) at 800000 nip ff6a770 lr
ff6a760 code 1 in libglib-2.0.so.0.4800.2[feaf000+11f000]
May 04 15:24:53 dc1.a-eon.tld kernel: lxsession[7255]: code: 4bfc9401 3920ffff 91210054 8061005c
2f830000 419c0014 38800000 4bfc93e5
May 04 15:24:53 dc1.a-eon.tld kernel: lxsession[7255]: code: 3920ffff 9121005c 2f8f0000 419e0008
<93ef0000> 418e000c 81210040 913b0000
May 04 15:37:40 mintppc.a-eon.tld kernel: packagekitd[4290]: segfault (11) at 8 nip 92dbc8 lr 92dae8
code 1 in packagekitd[920000+51000]
May 04 15:37:40 mintppc.a-eon.tld kernel: packagekitd[4290]: code: 38800080 3be001f4 4cc63182
4802c8ad 4bffff64 60000000 81210018 80be8048
May 04 15:37:40 mintppc.a-eon.tld kernel: packagekitd[4290]: code: 7fa6eb78 38800010 807e801c
3be0ffff <80e90008> 4cc63182 4802c881 4bffff38
Yes it shows you get a segfault for some reason.
So yes, 887f3ceb51cd3 could have been the reason but 525642624783 fixes it
already.
Therefore I think a proper bisect is needed to identify the culprit commit to understand the reason
and fix it.
You are running a 32 bits userspace on a 64 bits kernel ?
