https://bugzilla.kernel.org/show_bug.cgi?id=207383 --- Comment #48 from Duncan (1i5t5.duncan@xxxxxxx) --- (In reply to Duncan from comment #47) > > [I]dea to just try patch-reverting them on top of > > 5.7 or current 5.8-rc, thus eliminating the apparently unrelated > > kernel-panics I''ve twice triggered at the current bisect step. > > So I tried this 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! I was hoping to demonstrably prove it to be in those nine! I proved it *NOT* to be! Well, there's still the two commits to look at that wouldn't cleanly simple-revert. Maybe I'll get lucky and it's just an ordering thing, since I applied out of order compared to original commit, and they'll simple-revert on top of the others. Otherwise I'll have to actually look and see if I can make sense of it and manual revert, maybe/maybe-not for a non-coder, or try on 5.7 instead of 5.8-rc. If not them, maybe I'll just have to declare defeat on the bisect and hope for a fix without that. Last resort there's the buy-my-way-out solution, tho of course that leaves others without that option in a bind. But given the hours I've put into this (that I've only been able to thanks to COVID work suspension), at some point you just gotta cut your losses and declare defeat defeat. But we're not there yet. There's still the two to look at first, and the middle-ground 5.7 to try all 11 against. Hopefully... -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
