Re: [bisected] endless sd card reader polling in tip

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 27, 2021 at 06:56:39PM +0200, Mike Galbraith wrote:
> I then perfectly cleanly bisected the little bugger to the below.
> Mmm.. not convinced. Suggestions?

Yah, that doesn't look like a tip commit to me. Hmm, maybe we've pulled
in some broken stuff.

So what I do in such cases is bisect the tip merge commits:

$ git log --oneline --merges tip/master
d478ddf4e3cf Merge remote-tracking branch 'tip/irq/urgent' into tip-master
f9bfed3ad5b1 Merge tag 'irqchip-fixes-5.15-1' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/urgent
430117f4e609 Merge branch 'tip-x86-urgent' into tip-master
d2134885549e Merge remote-tracking branch 'tip/x86/cpu' into tip-master
723c56e57a63 Merge remote-tracking branch 'tip/timers/urgent' into tip-master
f1dfe445713e Merge remote-tracking branch 'tip/ras/core' into tip-master
ad214c6bf962 Merge remote-tracking branch 'tip/x86/fpu' into tip-master
b93350f79ec6 Merge remote-tracking branch 'tip/x86/urgent' into tip-master
f6d58d7648d4 Merge remote-tracking branch 'tip/x86/misc' into tip-master
b386cdf52519 Merge remote-tracking branch 'tip/x86/core' into tip-master
9a91b66ea202 Merge remote-tracking branch 'tip/irq/core' into tip-master
9665682cd5c3 Merge remote-tracking branch 'tip/sched/core' into tip-master
2e0f59f0ccbd Merge remote-tracking branch 'tip/x86/cleanups' into tip-master
66dced5982db Merge remote-tracking branch 'tip/locking/core' into tip-master
0a3dd0c68cfd Merge remote-tracking branch 'tip/locking/wwmutex' into tip-master
bec64008cfba Merge remote-tracking branch 'tip/perf/core' into tip-master
c6999a0491f7 Merge remote-tracking branch 'tip/objtool/core' into tip-master
9261e152ecf4 Merge remote-tracking branch 'tip/x86/cpu' into tip-master
...

You can either start in the middle of that list above and jot down in a
text file which merge is ok and which is not ok or you can simply get
the latest master, and start merging bottom to top, one by one and test
each merge in the process.

That would at least tell us which branch introduces the problem and then
we can drill down deeper.

HTH.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette



[Index of Archives]     [Linux Stable Commits]     [Linux Stable Kernel]     [Linux Kernel]     [Linux USB Devel]     [Linux Video &Media]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux