Comment 30 for bug 795717

Thilo Uttendorfer (t-lo) wrote :

I'm a bit confused, maybe someone can clarify this.

At it is mentioned that there still exists a underlying bug with kvmclock. I assume that this is not fixed in 2.6.38-11.50. Is it fixed in newer kernels? I assume that older kernels (like the one in lucid) are probably also affected by this underlying bug?