similar to: Time went backwards / Stability issues

Displaying 20 results from an estimated 10000 matches similar to: "Time went backwards / Stability issues"

2007 Oct 09
13
clocksource/0: Time went backwards
Dear fellow Xen''ers! I''m having a problem with my new Xen-enabled colocation server.. I hope ( at least ;) ) one of you guys know how to fix this problem.. For a certain amount of time ( 1-2 days ) the domU runs fine.. until the console starts spitting out messages like these: [80182.004456] clocksource/0: Time went backwards: delta=-6917292717540055641 shadow=80182004054805
2007 Sep 28
3
Time went backwards in domU after migration
Hello gurus, I have two physical xen hosts and when I migrate a domU from one host to another, I get many of this error from domU kernel: clocksource/0: Time went backwards: delta=-3536123661 shadow=686019823475 offset=281887188 Sometimes domU time stalls and network stops working, but other times it gets working again. The two hosts are using different platform timer source:
2007 Apr 18
1
Use of absolute timeouts for oneshot timers
I've been thinking a bit more about how useful an absolute timeout is for a oneshot timer in a virtual environment. In principle, absolute times are generally preferable. A relative timeout means "timeout in X ns from now", but the meaning of "now" is ambiguous, particularly if the vcpu can be preempted at any time, which means the determination of "now" can be
2007 Apr 18
1
Use of absolute timeouts for oneshot timers
I've been thinking a bit more about how useful an absolute timeout is for a oneshot timer in a virtual environment. In principle, absolute times are generally preferable. A relative timeout means "timeout in X ns from now", but the meaning of "now" is ambiguous, particularly if the vcpu can be preempted at any time, which means the determination of "now" can be
2011 Jan 10
6
2.6.37 dom0 under Xen 4.1 clocksource not working
When booting 2.6.37 (from kernel.org) under Xen 4.1, there are apparently issues with timer interrupts being delivered to the dom0. Repeatedly causing an interrupt (for example, the ACPI power button) will allow the system to boot, as does adding "clocksource=jiffies" to the kernel command line. This is only present under Xen, not when booting the same kernel on real hardware. When boot
2007 Aug 17
6
Gutsy Xen 3.1 2.6.22-9-xen network-bridge problem
Hi, I have a strange problem with my networking setup. I read all forums around the world where people had similar problems, but couldn''t find a solution. I have an Attansic L1 gigeth chip on my mainboard. This chip works OK in stock Ubuntu Gutsy (development) 2.6.22-9-generic kernel. When I boot into Xen, and after the bridge is created, the network stops working. Some info: - If I
2012 Jun 08
2
Xen 4.0.x 3,000 second time skew problem
Hi, I have two installs of Xen 4.0.1 on Debian squeeze dom0s that occasionally skew the time by 3000 seconds. It is always 3000 seconds and it always affects all guests. Depending on the kernels in the guests they will say: tp0 kernel: [9339489.266542] Clocksource tsc unstable (delta = -2999660317697 ns) or perhaps the kernel doesn''t notice but ntpd does: ls0 ntpd[15009]:
2012 Aug 07
1
Hist function
Hello everyone, First i explain my aim. I would like to calculate the frecuency of temperature (datos.mx1, columns 3-6) for each month with the thresholds of table lf.med and lc.med. numero1 <- hist(subset(datos.mx1[,3], datos.mx1$Mes==1),plot=FALSE,breaks=c(min(datos.mx1[,3]),lf.med[1,2],lc.med[1,2],max(datos.mx1[,3]))) # First month and only the first weather station (column 3) I now
2023 Jan 15
1
dovecot replication - new and cur folders on mx1 and mx2
Hello, I have a question in regards to specific dovecot replication behaviour and I'm just wondering if this is actually an expected/normal behaviour, or just a version issue. I'm using dovecot 2.3.16 which is packed by default with latest Ubuntu 22.04.1 LTS server release. I setup dovecot replication pair (mx1 - mx2) which is working ok. MX1 has priority 10, MX2 has priority 20. I
2023 Jan 17
1
dovecot replication - new and cur folders on mx1 and mx2
I can confirm this in a slightly different setting, but still using two-way sync between two dovecots. On e is 2.3.19.1 running on macOS Monterey, the other is 2.3.20 running in an alpine container on Ubuntu. Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>) R&A IT Strategy <https://ea.rna.nl/> (main site) Book: Chess and the Art of Enterprise?Architecture
2023 Jan 17
1
dovecot replication - new and cur folders on mx1 and mx2
It might have a noticeable effect on clients. I encountered (probably triggered by this in some way?) that I was unable to het the 'read' bit set in macOS Mail.app. Maybe (as I am doing HA with round robin) the Mail.app client got to one dovecot repository on one tcp connection and then on the other. Is there a reason why syncing tis move from new to cur is a bad idea? Gerben Wierda
2007 Apr 18
1
[PATCH 9/10] Vmi timer update.patch
Convert VMI timer to use clock events, making it properly able to use the NO_HZ infrastructure. On UP systems, with no local APIC, we just continue to route these events through the PIT. On systems with a local APIC, or SMP, we provide a single source interrupt chip which creates the local timer IRQ. It actually gets delivered by the APIC hardware, but we don't want to use the same local
2007 Apr 18
1
[PATCH 9/10] Vmi timer update.patch
Convert VMI timer to use clock events, making it properly able to use the NO_HZ infrastructure. On UP systems, with no local APIC, we just continue to route these events through the PIT. On systems with a local APIC, or SMP, we provide a single source interrupt chip which creates the local timer IRQ. It actually gets delivered by the APIC hardware, but we don't want to use the same local
2018 May 08
2
replicator: User listing returned failure
> I don't know if it makes a difference, I don't have quotes on my > mail_plugins: I don't have quotes too (It's difference between config file and dovecot -n output) > Did you check permissons on the replication fifos? For what? I think that problems on slave. How it should work in automatic mode? I repeat that from slave manually all works fine: >> As I
2018 May 07
2
replicator: User listing returned failure
Hello. I've tried to configure TCP replication to slave server. But I got some errors... mx1:~# dovecot --version 2.2.27 (c0f36b0) From dovecot.log: May 07 19:27:41 auth-worker(34348): Warning: mysql: Query failed, retrying: Unknown column 'username' in 'field list' May 07 19:27:41 auth-worker(34348): Debug: sql(*): SELECT username, domain FROM users May 07 19:27:41
2012 Jul 29
2
Error in for-loop
Hello erverybody, I have a problem with my second for-loop. 1. First i read the tables. datos.mx1 <- read.table('PETmx1.csv',head=TRUE,sep=';') datos.min <- read.table('PETmin.csv',head=TRUE,sep=';') http://r.789695.n4.nabble.com/file/n4638257/PETmx1.csv PETmx1.csv http://r.789695.n4.nabble.com/file/n4638257/PETmin.csv PETmin.csv names(datos.mx1)
2012 Mar 13
2
problems with SSH-based clustering dovecot 2.1.1
Hello, I'm using dovecot 2.1.1 with vpopmail 5.4.30 with multiples domains and I have problems setting up synchronization in between multiple computers. All act like master (my clients can connect to any of the them and read their emails either via POP3 either via IMAP, inbound email gets on any of the machines). Each machine is on a different continent, there is no shared drive in between
2012 Aug 11
3
replace funcion
Hello everybody, I would like to replace or recode a list of numbers between 1 and 12 (total 100). I have tried to make it with recode, but i have two types of replacements. For 1,2,3,4,11,12 => invierno and for 5,6,7,8,9 and 10 => verano. recode(datos.mx1[,7], "1='invierno'; 2='invierno';
2012 Oct 01
2
Bug#674907: (no subject)
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 prevent the problem from occuring.
2017 Dec 18
2
asterisk and Hyper-V
Thank you for a quick answer, Dmitry! We have tried the settings you suggested but nothing helped. The machine is running 4.4.0-104 kernel, 4 cores, Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz, clocksource is hyperv_clocksource_tsc_page, timing module is res_timing_timerfd.so. We have also tried to set 50% Reserve - no luck :(. ??, 18 ???. 2017 ?. ? 10:49, Dmitriy Ermakov <demonihin at