This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] xen-2.0 20040923 and previous: rpm crash in xenU

To: Peri Hankey <mpah@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xen-2.0 20040923 and previous: rpm crash in xenU
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 24 Sep 2004 13:41:07 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Fri, 24 Sep 2004 13:47:05 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Fri, 24 Sep 2004 12:05:42 BST." <4153FF86.1000805@xxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
I'd certainly recommend upgrading to a more recent xen2.0 release
and trying to repeat.

You're not sending large amounts of output from dom0 to a serial
line are you? I've observed this causing time (in all domains) to
be somewhat jerky, but this is to be expected as the serial line
is intended only for synchronous debug output.

Are dom0 and domU both on the same CPU? I presume you're using 2.6?


> I have previously mentioned a floating point exception in rpm which 
> seemed at one point to be connected with block-device handling in xenU 
> systems, as both problems occurred at the same time. As I now get only 
> the rpm floating point exception (sporadically), I have examined it further:
> ... # strace rpm
> [lots of strace output omitted]
> gettimeofday({1096021305, 741150}, NULL) = 0
> nanosleep({0, 20000000}, {1076798912, 1075195904}) = 0
> gettimeofday({1096021305, 741150}, NULL) = 0
> --- SIGFPE (Floating point exception) @ 0 (0) ---
> +++ killed by SIGFPE +++
> Does anyone else have problems of this kind? It may of course be a bug 
> in rpm but I would then expect it to appear in xen0 as well. This did 
> happen,but only in xen2.0-20040909 and xen2.0-20040910.
> So the implication (to me) is that there is a problem which sometimes 
> causes rpm to crash in gettimeofday, which did affect both xen0 and xenU 
>    in xen2.0-20040909 and xen2.0-20040910, and which now only affects xenU.
> Any ideas?

This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
Xen-devel mailing list