Ubuntu
linux package

[x86, VMI]TSC going back for VMI clocksource.

Bug #345553 reported by Alok Kataria
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
High
Stefan Bader

Bug Description

TSC going back for the VMI clocksource bug exists for all the hardy/intrepid and jaunty tree.

The patch which fixes this TSC going back issue for vmi clocksource is
already applied in mainline and stable kernels for 2.6.27/28, so I guess
intrepid and jaunty will get it from there.

I just wanted to bring this to your attention for the *hardy* tree, for which you explicitly will have to pick this up.
The commit details are :

commit 48ffc70b675aa7798a52a2e92e20f6cce9140b3d
Author: Alok N Kataria <email address hidden>
Date: Wed Feb 18 12:33:55 2009 -0800

    x86, vmi: TSC going backwards check in vmi clocksource

Can you please pick this up for the hardy tree ?
Also I see that the TSC patches that I had sent to you earlier are in
the hardy git tree, but not available as an kernel update yet, right ?
In that case can we please queue this patch too for the next update
along with the TSC patches.

Revision history for this message
Stefan Bader (smb) wrote :

Provided test package on http://people.ubuntu.com/~smb/bug261937 as this might be an instance of that bug.

Changed in linux:
assignee: nobody → stefan-bader-canonical
importance: Undecided → High
status: New → In Progress
Jeremy Foshee (jeremyfoshee)
tags: added: cherry-pick kernel-core
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

setting Won't Fix as there was no response on the provided test package.

~JFo

Changed in linux (Ubuntu):
status: In Progress → Won't Fix
Revision history for this message
Alok Kataria (akataria) wrote :

I assumed this fix was already picked up. The fix that I point to in the first comment, is required and fixes a legit bug, also the fix has been in mainline for quite a few kernel versions, so I don't think there is any risk associated with it. The fix is pretty straight forward, so I don't think you have to wait for any test confirmations.

I have seen quite a few people complaining because of this bug related to VMI on this thread,
http://ubuntuforums.org/showthread.php?t=882246&page=2 maybe all of them have started using "clocksource=" commandline parameter as a result no one is complaining anymore, but the VMI clock should work too and given that it is more efficient on those releases we should use that, whenever possible.

If the 8.04 release is still maintained, I would recommend that this fix should be picked for the next update. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.