similar to: Time ISR: Time went backwards: ... (dom0)

Changeset 6902 Sep 18 13:37:23 inyoureyes kernel: 1: 5077390000000 Sep 18 13:37:23 inyoureyes kernel: Timer ISR/1: Time went backwards: delta=-34786504 cpu_delta=15257914 shadow=5076506780929 off=938478409 processed=50770Sep 18 13:37:23 inyoureyes kernel: 0: 5077480044418 Sep 18 13:37:23 inyoureyes kernel: 1: 5077430000000 Sep 18 13:37:23 inyoureyes kernel: Timer ISR/1: Time went backwards:

I''m using a NetBSD 3.1 dom0 with Xen 2.0.7 (so far as I know, the latest supported combination for the NetBSD platform). Linux domUs have their logs fill with messages like this: May 8 02:01:39 debian kernel: Timer ISR: Time went backwards: -316000 131542680000000 9684000 131542690000000 May 8 02:01:39 debian kernel: Timer ISR: Time went backwards: -277000 131542680000000 9723000

I have a high end IBM system with 4 HT CPUs, am running xen-unstable with only Dom0 active, and I get lots of "Timer ISR/n: Time went backwards" messages. This is a short segment from dmesg: Timer ISR/1: Time went backwards: -259000 4465110000000 9741000 4465120000000 Timer ISR/6: Time went backwards: -224000 4465110000000 9776000 4465120000000 Timer ISR/6: Time went backwards: -159000

Hi, I have a microarray dataset from Agilent chips. The data were really log ratio between test samples and a universal reference RNA. Because of the nature of log ratios, coefficient of variation (CV) doesn't really apply to this kind of data due to the fact that mean of log ratio is very close to 0. What kind of measurements would people use to measure the dispersion so that I can compare

Hello! I see that version 2.5 is still in beta2, with very interesting features for me (like improved support for TLS). Does anyone know when it will be launched stably? Any estimated date? Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190324/2960ffc6/attachment.html>

Is anyone successfully and stably using linux 2.6.16.27 or 2.6.16.28 or 2.6.16.29 with xen 3.0.2-2 package? regards Tomasz -- GPG key fingerprint: 3883 B308 8256 2246 D3ED A1FF 3A1D 0EAD 41C4 C2F0 GPG public key availabe on pgp.mit .edu keyserver _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I have one xen machine where dom0 libata and pcibacked domU eth0 share a physical IRQ. I thought that the disk was bad (cause the system was crashing and giveing me disk errors) and replaced it with an IDE disk connected to a pcibacked SATA-IDE combo card. Problem seems to have gone away. The machine runs stably and hasn''t crashed yet. Now I have another machine where I pciback usb.

Hi all, Does anyone know of a good solution to the following? I'm trying to find a good way to stably associate distinct ID numbers with different BB in a module. As long as the module's IR hasn't changed in any way whatsoever, I'd like to be guaranteed to always generate the same ID <--> BB mapping. Or if the mapping is ambiguous, because two or more mappings between

Hi To troubleshoot FreeBSD panics triggered by ISDN load on an asterisk system, we are looking to buy an ISDN call generator/simulator device. The minimum requirements include: - Not too expensive - PRI support (BRI support is a plus) - CCS+CRC4 farming + HDB3 coding - EuroISDN (DSS1) support. - A minimum of 4 ports (120 channels/concurrent calls) - Compatibility with Digium cards. - DUT in TE

i set up a samba on redhat with a 192.168.x.x ip and and alias of a real ip. on the lan i have win nt and win 2k with real ip that can access the samba without difficulty, but when the win 98/me workstations, with 192.168.x.x ip's, try to connect to the samba, it would be either very slow, or saying that the lan is busy, or cannot connect at all. then, in the samba, i'll see the log

Hi Alexander, thanks for your good work on the megatec_usb driver. I have made a few more (cosmetic) changes. Is the driver now working stably for your device? In particular, do the instant commands (and particularly "upsdrvctl -k") work properly? In this case, we could hopefully mark the device as "supported" and merge the driver to the main branch. There is still the

Hey everyone, I'm trying version 1.0rc2, via the rpm at ATrpms. I'm running on CentOS 4.3 on an Opteron system. I have this running stably on a 32 bit system, but I'm crashing constantly on a 64 bit system. Here's what I'm getting in my mail logs when I try to log in via IMAP: Aug 3 15:01:21 lisa dovecot: imap-login: Login: user=<scottz>, method=PLAIN,

Use isr field instead of direct access to ioaddr. This way generalizes easily to virtio 1.0. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/virtio/virtio_pci.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_pci.c b/drivers/virtio/virtio_pci.c index 9be59d9..ee1b54c 100644 --- a/drivers/virtio/virtio_pci.c +++

Use isr field instead of direct access to ioaddr. This way generalizes easily to virtio 1.0. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/virtio/virtio_pci.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_pci.c b/drivers/virtio/virtio_pci.c index 9be59d9..ee1b54c 100644 --- a/drivers/virtio/virtio_pci.c +++

Use isr field instead of direct access to ioaddr. This way generalizes easily to virtio 1.0. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/virtio/virtio_pci.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_pci.c b/drivers/virtio/virtio_pci.c index 9be59d9..ee1b54c 100644 --- a/drivers/virtio/virtio_pci.c +++

On Sun, Jul 13, 2014 at 10:26 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/13/2014 10:54 AM, syslinux-bot for Gene Cumm wrote: >> Commit-ID: 3741886cb700e1017d70f1753f013fa10f4d9272 >> Gitweb: http://www.syslinux.org/commit/3741886cb700e1017d70f1753f013fa10f4d9272 >> Author: Gene Cumm <gene.cumm at gmail.com> >> AuthorDate: Sun, 13 Jul 2014

On 07/13/2014 10:54 AM, syslinux-bot for Gene Cumm wrote: > Commit-ID: 3741886cb700e1017d70f1753f013fa10f4d9272 > Gitweb: http://www.syslinux.org/commit/3741886cb700e1017d70f1753f013fa10f4d9272 > Author: Gene Cumm <gene.cumm at gmail.com> > AuthorDate: Sun, 13 Jul 2014 11:18:50 -0400 > Committer: Gene Cumm <gene.cumm at gmail.com> > CommitDate: Sun, 13 Jul

All, Attached is a patch from Prarit Bhargava, who is not subscribed to the list (but CC''ed). His description follows: Add "Warning" to the "Time went backwards" message. Most QA groups (if not all) grep for specific messages in the syslog such as "Error", "Warning", "Oops". Time went backwards is a key error which can result in

The behaviour of default ISRs as provided by the BIOS varies wildly between platforms. Some will simply iret, some will send EOI, some will send EOI and disable the interrupt at the PIC, some will crash the machine due to single-bit errors in the ISR address. When PXENV_UNDI_ISR_IN_START returns PXENV_UNDI_ISR_OUT_NOT_OURS, send the EOI ourselves rather than risking the unpredictable behaviour

Hi all, Using a slow serial console with sync_console on SMP leaves me with an unusable system: it gets into a flood of Timer ISR/0: Time went backwards: delta=-3566279 cpu_delta=16433721 shadow=2019998373 off=420435384 processed=2444000000 cpu_processed=2424000000 0: 2424000000 1: 2444000000 messages which swamps the console and leaves things almost, but not quite, completely hung. It is a