Messages in this thread | | | Date | Fri, 24 Jul 2020 17:35:37 +0200 | From | Joerg Roedel <> | Subject | Re: Regression on todays tip/master (commit 16f70beccf43) |
| |
On Fri, Jul 24, 2020 at 04:50:53PM +0200, Joerg Roedel wrote: > Next thing is, I can reliable reproduce it with yesterdays tip/master > (commit 16f70beccf43), but did not see it with tip/master pulled today > (commit c02699cd25e8) yet.
Next bisection try ended with this log:
# bad: [16f70beccf43f9eb481ff8485974bc00ab2267d8] Merge branch 'core/debugobjects' # good: [ba47d845d715a010f7b51f6f89bae32845e6acb7] Linux 5.8-rc6 git bisect start '16f70beccf43' 'v5.8-rc6' # good: [e9c8c19545f31ec817507ee11884356799f14917] Merge branch 'perf/core' git bisect good e9c8c19545f31ec817507ee11884356799f14917 # bad: [8e62572d2c29e1c484f5d4e7c016793209de2efb] Merge branch 'linus' git bisect bad 8e62572d2c29e1c484f5d4e7c016793209de2efb # good: [c085fb8774671e83f6199a8e838fbc0e57094029] perf/x86/intel/lbr: Support XSAVES for arch LBR read git bisect good c085fb8774671e83f6199a8e838fbc0e57094029 # good: [220dbf4aaa5b574f67ce23fa4d7b0104515bc60e] Merge branch 'WIP.core/headers' git bisect good 220dbf4aaa5b574f67ce23fa4d7b0104515bc60e # bad: [9d246053a69196c7c27068870e9b4b66ac536f68] sched: Add a tracepoint to track rq->nr_running git bisect bad 9d246053a69196c7c27068870e9b4b66ac536f68 # bad: [46609ce227039fd192e0ecc7d940bed587fd2c78] sched/uclamp: Protect uclamp fast path code with static key git bisect bad 46609ce227039fd192e0ecc7d940bed587fd2c78 # bad: [85c2ce9104eb93517db2037699471c517e81f9b4] sched, vmlinux.lds: Increase STRUCT_ALIGNMENT to 64 bytes for GCC-4.9 git bisect bad 85c2ce9104eb93517db2037699471c517e81f9b4 # bad: [faa2fd7cbad4609d06d7904c0a80cf2f8cd23678] Merge branch 'sched/urgent' git bisect bad faa2fd7cbad4609d06d7904c0a80cf2f8cd23678 # first bad commit: [faa2fd7cbad4609d06d7904c0a80cf2f8cd23678] Merge branch 'sched/urgent'
So it ends at a merge commit. I am not going to debug this further as it is no longer reproducible with todays tip/master. It probably was just a bug in a conflict resolution when merging branches or something like that.
Regards,
Joerg
| |