[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
----------------------------------------------------------------------------
     Kernel Version|5.7-rc1 - 5.7 - 5.8-rc4+    |5.7-rc1 - 5.7 - 5.8-rc5+

--- Comment #62 from Duncan (1i5t5.duncan at cox.net) ---
(In reply to Duncan from comment #48)
> (In reply to Duncan from comment #47)
> > So I tried [patch-reverting] with the 11 above commits against
> > 5.8.0-rc4-00025-gbfe91da29, which previously tested as triggering the
> freeze
> > for me.  Of the 11, nine clean-reversed and I simply noted and skipped the
> > other two (3202fa62f and 630f289b7) for the moment.  The patched kernel
> > successfully built and I'm booted to it now.
> 
> Bah, humbug!  Got a freeze and the infamous logged trace on that too

After taking a few days discouragement-break I'm back at trying to pin it down.
 The quoted above left two candidate commits, 3202fa62f and 630f289b7, neither
of which would clean-revert as commits since were preventing that.

630f289b7 is a few lines changed in many files so I'm focusing on the simpler
3202fa62f first.  Turns out the reason 320... wasn't reverting was two
additional fixes to it that landed before v5.7.  Since they had Fixes: 320...
labels they were easy enough to find and patch-revert, after which
patch-reverting 320... itself worked against a current v5.8-rc5-8-g0dc589da8. 
I first tested it without the reverts to be sure it's still triggering this bug
for me, and just confirmed it was, freeze with the telltale log dump.

So for me at least, v5.8-rc5 is bad (just updated the version field to reflect
that).

Meanwhile I've applied the three 320-and-followups revert-patches to
v5.8-rc5-8-g0dc589da8 and just did the rebuild with them applied.  Now to
reboot to it and see if it still has our bug.  If no, great, pinned down.  If
yes, there's still that 630... commit to try to test.

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