So I believe we've isolated this to a kernel bug between 2.6.32.x and 2.6.33? Though I suppose it could be a problem with Wine that's exposing it?
Time to find the breaking commit, I guess. Git bisecting the kernel won't be too fun though, I imagine xD
So I believe we've isolated this to a kernel bug between 2.6.32.x and 2.6.33?
Though I suppose it could be a problem with Wine that's exposing it?
Time to find the breaking commit, I guess. Git bisecting the kernel won't be too fun though, I imagine xD