Comment # 265
on bug 66963
from Kajzer
(In reply to Alex Deucher from comment #264) > (In reply to Kajzer from comment #263) > > git bisect visualize > > commit 6101b3ae94b4f266456308824e9ca4eab1235d1a > > Author: Alex Deucher <alexander.deucher@amd.com> > > Date: Tue Aug 19 11:54:15 2014 -0400 > > > > drm/radeon: fix active cu count for SI and CIK > > > > This fixes the CU count reported to userspace for > > OpenCL. > > > > bug: > > https://bugzilla.kernel.org/show_bug.cgi?id=82581 > > > > Signed-off-by: Alex Deucher <alexander.deucher@amd.com> > > Reviewed-by: Michel Dänzer <michel.daenzer@amd.com> > > Cc: stable@vger.kernel.org > > Something must have gone wrong in your bisect. That commit does not affect > your chip. Perhaps the bug is somewhat hard to reproduce which caused you > to mis-mark some commits as good. Could be the case. Bug is hard to reproduce because it happens only in games and at random intervals. And you can't idle it. Sadly I don't have much time for gaming now. I'll try it one more time, more thoroughly. One question though, if I'm 100% positive that v3.16 is good, should I skip bisects (mark them as good) if they end up as 3.16.0+ image after bisect ? Thus testing only v3.17 bisects. Because out of 7 steps 3 were from 3.17, it can save a lot of time if I could skip 3.16 bisects.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
