Bug#511412: clocksource/0: Time went backwards

[Hans van Kranenburg]

Using the Xen clocksource seems to be somewhat buggy yes, I also 
experienced lots of related problems until I decoupled the domU clock 
from dom0.


Some time ago I edited the Xen page on wiki.debian.org about this, so I 
think it could be helpful to provide a link for others who are searching 
the bug archives about this issue:


http://wiki.debian.org/Xen#A.27clocksource.2BAC8-0.3ATimewentbackwards.27

Hans



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#511412: clocksource/0: Time went backwards

[Nikita V. Youshchenko]

Package: linux-image-2.6.26-1-xen-686
Version: 2.6.26-12
Severity: normal

After upgrading a domU from etch to lenny kernel, I've faced a hard domU
lockup that very looks like
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1098
after severak hours f running.

I've applied the workaround descried there at comment 13, and since
then domU worked several days under high load without issues.

Maybe make debian kernels not to use xen clocksource until the issue is
fixed? 


-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (620, 'testing'), (600, 'unstable'), (550, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org