| What | Removed | Added |
|---|---|---|
| Component | DRM/Radeon | Drivers/Gallium/radeonsi |
| Version | XOrg CVS | git |
| Product | DRI | Mesa |
(In reply to Hannu from comment #5) > As I explained above, bisecting this is impossib= le due to random long time > between occurrences of the bug. That doesn't make it impossible, it just means you need patience. Take your time, and make sure you test each commit for at least as long (preferably longer, to account for variation) as it's ever taken for the problem to occ= ur before declaring it good. On the bright side, when the problem occurs quick= ly, you know that commit is bad and can move on to the next one. (In reply to Hannu from comment #6) > I don't know much about xorg stacks inner workin= gs but it might be that mesa > isn't buggy, but has some added functionality between 10.3.x and 10.2.= x that > exercises buggy code path lower in the driver stack. It doesn't matter. Since the problem happens with Mesa 10.3.y but not with 10.2.y, once we know which change between them makes the difference, we'll = be at least a big step closer to solving the problem.