Ah. I picked up a kernel update last night that was the version below so
I thought it might have been that.
Thanks!
On Thu, 2006-07-20 at 03:25 +0000, Ben Collins wrote:
> On Thu, 2006-07-20 at 02:56 +0000, sohail wrote:
> > Is this supposed to be fixed for 2.6.15-26-686? Because it still isn't
> > fixed for me (top reports ~80% CPU usage with max_cstate set to 3)
>
>
> "Fix committed" means it's in our source repo. When it's marked "Fix
> released", then it will mean it's uploaded and available.
>
Ah. I picked up a kernel update last night that was the version below so
I thought it might have been that.
Thanks!
On Thu, 2006-07-20 at 03:25 +0000, Ben Collins wrote:
> On Thu, 2006-07-20 at 02:56 +0000, sohail wrote:
> > Is this supposed to be fixed for 2.6.15-26-686? Because it still isn't
> > fixed for me (top reports ~80% CPU usage with max_cstate set to 3)
>
>
> "Fix committed" means it's in our source repo. When it's marked "Fix
> released", then it will mean it's uploaded and available.
>