On 2012-12-11, Debian Bug Tracking System wrote:
> #674907: shifts the clock by 50 minutes unexplicably under a Xen dom0
>
> It has been closed by Bastian Blank .
What about us poor users on Debian squeeze? Or worse, about the upcoming
wheezy release?
Is there the possibility to backport this fix
And here's the possible fix if anyone is still following this bug :
http://lists.xen.org/archives/html/xen-devel/2012-11/msg01384.html
Cheers,
Sylvain
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.d
I have the same issue running wheezy with a recent custom compiled kernel.
I also used to have the issue under squeeze ...
root@sake:~ # xm dmesg | grep "Xen version"
(XEN) Xen version 4.1.3 (Debian 4.1.3-2) (wa...@debian.org) (gcc
version 4.7.1 (Debian 4.7.1-7) ) Fri Sep 7 17:48:19 UTC 2012
roo
On Mon, 2012-10-01 at 23:14 +0200, Mauro wrote:
> On 1 October 2012 21:01, Thomas Goirand wrote:
> > On 10/01/2012 09:21 PM, Bastian Blank wrote:
> >>
> >> Please don't top-post.
> >>
> >> On Mon, Oct 01, 2012 at 02:42:54PM +0200, Pierre Colombier wrote:
> >>>
> >>> - Unreliable Time affects all t
On 1 October 2012 20:24, Jonathan Nieder wrote:
> Mauro wrote:
>
>> The shift time happens also in dom0 not only in domUs.
>
> Thanks.
>
> Just gathering information: some references:
>
> http://thread.gmane.org/gmane.comp.emulators.xen.user/75486
> http://thread.gmane.org/gmane.comp.emulators.x
On 1 October 2012 21:01, Thomas Goirand wrote:
> On 10/01/2012 09:21 PM, Bastian Blank wrote:
>>
>> Please don't top-post.
>>
>> On Mon, Oct 01, 2012 at 02:42:54PM +0200, Pierre Colombier wrote:
>>>
>>> - Unreliable Time affects all the system and can make the whole host
>>> useless. At least for
On 2012-10-01, Jonathan Nieder wrote:
> Mauro wrote:
>
>> The shift time happens also in dom0 not only in domUs.
>
> Thanks.
>
> Just gathering information: some references:
>
> http://thread.gmane.org/gmane.comp.emulators.xen.user/75486
> http://thread.gmane.org/gmane.comp.emulators.xen.user/655
On 10/01/2012 09:21 PM, Bastian Blank wrote:
Please don't top-post.
On Mon, Oct 01, 2012 at 02:42:54PM +0200, Pierre Colombier wrote:
- Unreliable Time affects all the system and can make the whole host
useless. At least for production use.
Still the system.
- Is "just" broken for all my 53
can't really know if it's in the hypervisor or the linux kernel's way to
handle the clocksource from the hypervisor.
after some google search, the bug seems to appear in kernel 2.6.20
(don't take this for granted)
If it's really like this, then the bug is probably in the linux kernel.
Anyway the
Mauro wrote:
> The shift time happens also in dom0 not only in domUs.
Thanks.
Just gathering information: some references:
http://thread.gmane.org/gmane.comp.emulators.xen.user/75486
http://thread.gmane.org/gmane.comp.emulators.xen.user/65530
What's the newest kernel and hypervisor you've tr
On 2012-10-01, Mauro wrote:
> The shift time happens also in dom0 not only in domUs.
That is correct.
--
Le pouvoir n'est pas à conquérir, il est à détruire
- Jean-François Brient, de la servitude moderne
pgp8jP4TxLv2R.pgp
Description: PGP signature
On 1 October 2012 20:01, Jonathan Nieder wrote:
> This particular bug is known to be a domU problem, so I suspect
> Bastian made the right call. If he has overlooked something, we'd
> welcome the missing information.
The problem happens also in dom0.
--
To UNSUBSCRIBE, email to debian-bugs-d
On 1 October 2012 16:20, Antoine Beaupré wrote:
>
> There are 3 separate "users", which I would qualify more as "admins"
> which are reporting this bug, but a lot more users are affected than
> this. If you want, I can organise the users of those domUs to voice
> their frustration with the shifti
Hi Antoine,
anarcat wrote:
> Why was this reassigned to the linux kernel?
>
> I explicitely stated (twice) that machines not running Xen are *not*
> affected, so this is specifically a Xen issue.
Xen in squeeze consists of both a hypervisor and tools and a kernel
patch, and potential changes to
On Mon, Oct 01, 2012 at 04:06:27PM +0200, Bastian Blank wrote:
> reassign 674907 src:linux-2.6
Why was this reassigned to the linux kernel?
I explicitely stated (twice) that machines not running Xen are *not*
affected, so this is specifically a Xen issue.
I do not want to get into an edit war h
Please don't top-post.
On Mon, Oct 01, 2012 at 02:42:54PM +0200, Pierre Colombier wrote:
> - Unreliable Time affects all the system and can make the whole host
> useless. At least for production use.
Still the system.
> - Is "just" broken for all my 53 physical servers with different
> hardware.
- Unreliable Time affects all the system and can make the whole host
useless. At least for production use.
- breaks data on time-sensitive databases especially if the data is
spread on multiple hosts.
- Is "just" broken for all my 53 physical servers with different
hardware. (with 2 or 3 server "sh
On Mon, Oct 01, 2012 at 10:32:36AM +0200, Pierre Colombier wrote:
> When the "50 minute shift" occurs. It occurs simultaneously on all domU
> and dom0.
> on all domU and dom0, the syslog says
> Clocksource tsc unstable (delta = -2999660303146 ns) (or something very
> near 3000 seconds)
The TSC is
On Wed, Sep 26, 2012 at 06:13:58PM -0400, Antoine Beaupré wrote:
> Do you mind explaining why this bug was downgraded from grave (which had
> a justification) to normal?
- It only affects itself, it is already the system.
- It does not break data.
- It does not open a security hole.
- It is not br
I want to add this log messages in kern.log
Sep 30 23:21:12 xen-p01 kernel: [104363.072636] Clocksource tsc
unstable (delta = -811538939738 ns)
Sep 30 23:21:13 xen-p01 kernel: [104363.189879] []
? run_timer_softirq+0x196/0x268
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.o
I thingk this bug is grave since time synchronization is critical for
many applications.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I have exactly the same problem.
I have two cluster nodes HP Proliant DL 580 G5 systems with four quad
core Xeon processors.
Operating system is debian squeeze.
Uname -a:
Linux xen-p02 2.6.32-5-xen-amd64 #1 SMP Sun Sep 23 13:49:30 UTC 2012
x86_64 GNU/Linux
This is an annoying problem, the system
I want to add some information
When the "50 minute shift" occurs. It occurs simultaneously on all domU
and dom0.
on all domU and dom0, the syslog says
Clocksource tsc unstable (delta = -2999660303146 ns) (or something very
near 3000 seconds)
Using ntp is ok to resync the clock but does not prev
Do you mind explaining why this bug was downgraded from grave (which had
a justification) to normal?
--
C'est avec les pierres de la loi qu'on a bâti les prisons,
et avec les briques de la religion, les bordels.
- Blake, William
pgpwrvaPeSEgn.pgp
Description: PGP signatu
reassign 674907 xen
found 674907 4.0.1-5.4
notfound 674907 3.2.1-2
severity 674907 grave
summary 674907 clock shifts forward by 50 minutes unexplicably under Xen
thanks
We have switched to the "ntp" package to see if this was
OpenNTPd-specific: turns out it's not. We are seeing crashes of ntp on
t
Hi,
Here's the requested logs, I hope they are helpful.
> $ date
> mercredi 6 juin 2012, 10:48:50 (UTC-0400)
>
> root@socrate:/home/sebas# date
> mercredi 6 juin 2012, 11:37:36 (UTC-0400)
>
> root@socrate:/home/sebas# cat /var/lib/openntpd/ntpd.drift
> cat: /var/lib/openntpd/ntpd.drift: Aucun f
On 28/05/12 11:20, Antoine Beaupre wrote:
> Package: openntpd
> Version: 3.9p1+debian-8~bpo60+1
> Severity: normal
>
> This software inexplicably shifts the clock by 3000 seconds (around 10
> minutes) every 4 days when running in a
> Xen domU in Debian Squeeze. Example logs:
>
> May 18 19:35:56 a
Package: openntpd
Version: 3.9p1+debian-8~bpo60+1
Severity: normal
This software inexplicably shifts the clock by 3000 seconds (around 10 minutes)
every 4 days when running in a
Xen domU in Debian Squeeze. Example logs:
May 18 19:35:56 athena ntpd[1411]: skew change -11.931 exceeds limit
May 18
28 matches
Mail list logo
