[Bug 207383] [Regression] 5.7 amdgpu/polaris11 gpf: amdgpu_atomic_commit_tail

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=207383

Duncan (1i5t5.duncan at cox.net) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #290093|0                           |1
        is obsolete|                            |

--- Comment #38 from Duncan (1i5t5.duncan at cox.net) ---
Created attachment 290101
  --> https://bugzilla.kernel.org/attachment.cgi?id=290101&action=edit
Another partial git bisect log update

Just as I was thinking that step was going to be bisect good... it wasn't. 
Confirmed with the usual tail-commit log trace.

(In reply to Duncan from comment #36)
> 6cad420cc akpm (the majority).  Very likely in this tree.

Definitely this tree/pull.  No merge but 113 commits remaining *at* this step
(not _after_), all with signed-off-by both Andrew and Linus so it's all the
akpm tree.  We know the tree, now.

FWIW for anyone relatively new to the bug who skipped some of the first
comments, my bad first bisect attempt ended up in akpm as well.  I haven't
checked if it was the same pull altho I'd guess so.  However, at that time I
was only testing commits with drm in the path (including several that went in
via the akpm tree not the drm tree, one of which that bisect ultimately pointed
me at), and I suspect that's what did me in.

So I strongly suspect that while it's the akpm tree, it's *NOT* the one
remaining candidate with the drm-path in it (4064b9827), thus explaining why
the first bisect ended up pointing at a drm-path commit that I tested by
reverting, only to still have the bug.  I tried a shortcut and it ended up a
rabbit trail. =:^(

Other than that, 113 candidate commits left (well, 112 if we subtract that one)
is still too many (for me) to guess at or really to even just list here.  Two
more steps should bring it down to 28ish, three to 14ish, and maybe I can start
guessing then.  With luck I'll get a couple more bad ones right away and narrow
it down quickly.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.