This bug was fixed in the package linux - 2.6.27-14.33
---
linux (2.6.27-14.33) intrepid-proposed; urgency=low
[Stefan Bader]
* Fix FTBS due to a mysteriously missing ABI directory.
linux (2.6.27-14.32) intrepid-proposed; urgency=low
[Stefan Bader]
* Rebuild of 2.6.27-14.3
** Changed in: linux (Ubuntu Intrepid)
Importance: Undecided => Wishlist
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Hardy)
Importance: Undecided => Wishlist
Assignee: (unassigned) => Stefan Bader
This bug was fixed in the package linux - 2.6.24-24.53
---
linux (2.6.24-24.53) hardy-proposed; urgency=low
[Stefan Bader]
* Rebuild of 2.6.24-24.51 with 2.6.24-23.52 security patches applied.
linux (2.6.24-24.51) hardy-proposed; urgency=low
[Alessio Igor Bogani]
* rt: Upd
Accepted linux into intrepid-proposed; please test and give feedback
here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
Include backport of vmware stable TSC patchset
https
Fixes have been committed to Hardy. One additional patch added to import those
changes into Xen specific header files.
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commitdiff;h=acc45377a3a9938404bcc27586bd7ab4a2add062
** Changed in: linux (Ubuntu Hardy)
Status: In Progress =>
Hi Stefan,
I would like to test this on our ESX setup as we often see the
'Clocksource tsc unstable' warnings on these machines. Do you have a
test case to reliably repeat the issue? We get the warning sporadically
without any obvious pattern which makes testing the -proposed packages a
little tri
This bug was fixed in the package linux - 2.6.28-7.18
---
linux (2.6.28-7.18) jaunty; urgency=low
[ Alok Kataria ]
* SAUCE: (drop after 2.6.29) x86: add a synthetic TSC_RELIABLE feature
bit
- LP: #319945
* SAUCE: (drop after 2.6.29) x86: add X86_FEATURE_HYPERVISOR featu
As I don't have a real good environment for this, I never saw this myself. The
descriptions of the bug sound like it could happen more often when the host is
very busy (probably the guest workload should not be to high but might not
matter much). So the guest process is not scheduled for a longe
