https://bugzilla.novell.com/show_bug.cgi?id=344877
User nice@titanic.nyme.hu added comment
https://bugzilla.novell.com/show_bug.cgi?id=344877#c18
Tamás Németh changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nice@titanic.nyme.hu
--- Comment #18 from Tamás Németh 2008-01-08 09:24:13 MST ---
I also have this problem (or similar) on an x86_64 system which runs a
paravirtualized Linux domU (x86_64 of course, but 32 bit userland) and a fully
virtualized Windows Server 2003. After 2-3 days of continuous running the clock
of dom0 suddenly jums into the year 2203 and freezes, but the logs keep
complainig about the time going backwards. However, setting the clocksource to
jiffies solved the problem for me. It was even possible to log in via SSH into
the virtually unresponsive dom0 and change the clock source on the fly.
Let's see some parts of /var/log/messages:
Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164325959175799191 shadow=182530936064246 offset=51157
Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164325959175786337 shadow=182530936064246 offset=63939
Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164325959175776875 shadow=182530936064246 offset=73371
Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164325959175758012 shadow=182530936064246 offset=92210
Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164325959175745946 shadow=182530936064246 offset=104288
Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164325959175731660 shadow=182530936064246 offset=118562
Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164325959175723354 shadow=182530936064246 offset=126875
Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164325959175705242 shadow=182530936064246 offset=144986
Dec 24 03:41:43 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164325959175693748 shadow=182530936064246 offset=156475
May 1 13:38:47 carrier1 syslog-ng[3110]: STATS: dropped 165
May 1 13:38:47 carrier1 kernel: 284321 shadow=194035956173844 offset=142457115
May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed.
May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164314454013278739 shadow=194035956173844 offset=142462709
May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed.
May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164314454013273157 shadow=194035956173844 offset=142468291
May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed.
May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164314454013267575 shadow=194035956173844 offset=142473867
May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed.
May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164314454013261987 shadow=194035956173844 offset=142479455
May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed.
May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164314454013256399 shadow=194035956173844 offset=142485043
May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed.
May 1 13:38:47 carrier1 nmbd[4024]: [2203/05/01 13:38:47, 0]
nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164314454013250793 shadow=194035956173844 offset=142490649
May 1 13:38:47 carrier1 nmbd[4024]: find_domain_master_name_query_fail:
May 1 13:38:47 carrier1 kernel: printk: 4 messages suppressed.
As you can see, there is a point when the time suddenly changes, but before
that point complaining begins. After the time journey, the time is virtually
frozen, but not entirely:
Let's see, what happened somewhat(?) later:
May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164305755947820318 shadow=202733992062057 offset=172040497
May 1 13:38:47 carrier1 kernel: printk: 8738 messages suppressed.
May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164305750947799778 shadow=202738992057513 offset=172069418
May 1 13:38:47 carrier1 kernel: printk: 8609 messages suppressed.
May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164305745947835361 shadow=202743992057509 offset=172029508
May 1 13:38:47 carrier1 kernel: printk: 8704 messages suppressed.
May 1 13:38:47 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164305740947825450 shadow=202748992058412 offset=172038763
May 1 20:18:41 carrier1 kernel: printk: 12490 messages suppressed.
May 1 20:18:41 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164328465117250601 shadow=202753992057501 offset=172023354
May 1 20:18:41 carrier1 syslog-ng[3110]: STATS: dropped 7238
May 1 20:18:41 carrier1 nmbd[4024]: [2203/05/01 20:18:41, 0]
nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
May 1 20:18:41 carrier1 nmbd[4024]: find_domain_master_name_query_fail:
May 1 20:18:41 carrier1 nmbd[4024]: Unable to find the Domain Master Browser
name AD<1b> for the workgroup AD.
May 1 20:18:41 carrier1 nmbd[4024]: Unable to sync browse lists in this
workgroup.
May 1 20:18:41 carrier1 kernel: printk: 9544 messages suppressed.
May 1 20:18:41 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164328460117239584 shadow=202758992058125 offset=172033212
May 1 20:18:41 carrier1 kernel: printk: 9039 messages suppressed.
May 1 20:18:41 carrier1 kernel: clocksource/0: Time went backwards:
delta=-6164328455117234725 shadow=202763992057246 offset=172038426
May 1 20:18:41 carrier1 kernel: printk: 9328 messages suppressed.
I've also found the description of the same (or very similar) bug at:
https://bugs.launchpad.net/xen/+bug/146924
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.