https://bugzilla.kernel.org/show_bug.cgi?id=101391
Michael Long changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=101391
--- Comment #6 from Michel Dänzer ---
"No more bad commits" isn't necessarily a problem. Just keep testing the
commits you get from running "git bisect good/bad" according to the test result
with the previous commit, until the process is finishe
https://bugzilla.kernel.org/show_bug.cgi?id=101391
--- Comment #5 from Michael Long ---
I managed to proceed with the bisect process but it doesn't lead to another bad
commit.
After that I restarted the bisection but this time without limiting to a
sub-tree. This time e640a280ccb9c448a3d9d522ea
https://bugzilla.kernel.org/show_bug.cgi?id=101391
--- Comment #4 from Michel Dänzer ---
(In reply to Michael Long from comment #3)
> Bisecting: 12 revisions left to test after this (roughly 4 steps)
> error: Your local changes to the following files would be overwritten by
> checkout:
You need
https://bugzilla.kernel.org/show_bug.cgi?id=101391
--- Comment #3 from Michael Long ---
Sorry for the delay, I tried a bisect:
git bisect start 'v4.0..v4.1' 'drivers/gpu/drm'
# good: [39a8804455fb23f09157341d3ba7db6d7ae6ee76] Linux 4.0
git bisect good 39a8804455fb23f09157341d3ba7db6d7ae6ee76
# b
https://bugzilla.kernel.org/show_bug.cgi?id=101391
--- Comment #2 from Michael Long ---
The last working kernel version is 4.0.x, I'm back on 4.0.8 right now. It also
does happen with 4.1.0. I'll try to do a bisect.
--
You are receiving this mail because:
You are watching the assignee of the bu
https://bugzilla.kernel.org/show_bug.cgi?id=101391
--- Comment #1 from Michel Dänzer ---
What was the last kernel version that didn't have this problem? Does it also
happen with 4.1.0? Can you bisect?
--
You are receiving this mail because:
You are watching the assignee of the bug.
