Le 13/05/2021 à 17:19, Christian Zigotzky a écrit :
On 13 May 2021 at 12:01 pm, Christophe Leroy wrote:
quoted
Le 13/05/2021 à 08:47, Christian Zigotzky a écrit :
quoted
Hi Christophe,
quoted
On 9. May 2021, at 19:37, Christophe Leroy [off-list ref] wrote:
Did I do an error in my analysis ?
No, you didn’t. On the contrary you have found the issue. ;-) The issue is somewhere in the new interrupt code.
I'm not convinced, but let's give it a try.
quoted
quoted
ZZ | * | ceff77efa4f8 powerpc/64e/interrupt: Use new interrupt context tracking scheme
Could you please create a patch for reverting the new interrupt code? I would like to confirm your result.
Please fetch https://github.com/chleroy/linux.git and try the branch for_christian.
This is a revert of approx a dozen of commits around the changes to 64e on top of v5.13-rc1.
If the top of the branch works for you, it would be great if you can find out which one of the reverts fixes the problem for real.
Thanks
Christophe
It's working! Great! I can use the RC1 on my FSL P5040. Thank you! The issue is definitely somewhere in the interrupt code. Please tell me the next steps.
Can you bisect between 5.13-rc1 and the top of the 'for_christian' branch to find the first 'good' commit ?
Take care it is an "up side down" bisect, a 'good' is one that does _not_ work and a 'bad' is a commit that works.
git bisect start
git bisect bad 1c8f441f1485
git bisect good 6efb943b8616
Christophe