From: Peri Hankey <mpah@thegreen.co.uk>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: Flavio Leitner <fbl@conectiva.com.br>, xen-devel@lists.sourceforge.net
Subject: Re: xen-2.0 20040923 and previous: rpm crash in xenU
Date: Tue, 28 Sep 2004 11:33:53 +0100 [thread overview]
Message-ID: <41593E11.4020300@thegreen.co.uk> (raw)
In-Reply-To: <E1CByG8-0004p9-00@mta1.cl.cam.ac.uk>
Is there any kind of workaround for this nanosleep problem?
-- Peri
Ian Pratt wrote:
>>On Sat, Sep 25, 2004 at 07:48:44PM +0100, Peri Hankey wrote:
>>
>>
>>>---------------- xen0 ------------------------
>>>[me@xen0 testing]$ ./time-test
>>>find_cpu_speed: error parsing /proc/cpuinfo for cpu MHz. Assume 2400
>>>MhzCPU speed = 2400 MHz
>>>...........................................................................................................
>>>...........................................................................................................
>>>... (lots of dots)
>>>---------------- xenU ------------------------
>>>[me@xenU testing]$ ./time-test
>>>find_cpu_speed: error parsing /proc/cpuinfo for cpu MHz. Assume 2400
>>>MhzCPU speed = 2400 MHz
>>>nanosleep(20000us): gtod 0
>>>.nanosleep(20000us): gtod 0
>>>.nanosleep(20000us): gtod 0
>>>.nanosleep(20000us): gtod 0
>>>
>>>
>>Running on xen0 or xenU doesn't make any difference, just lots
>>of dots
>>
>>
>
>That's the behaviour we see on all of our machines i.e. nanosleep
>works fine. I think Peri's problem may be Athlon related,
>
>
>
>>and that parser error.
>>
>>
>
>The find_cpu_speed printf shouldn't happen any more -- we no
>longer clear the TSC bit in the set of features the CPU reports,
>hence there should be a 'MHz' line in /proc/cpuinfo
>
>
>Ian
>
>
>
>
>-------------------------------------------------------
>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
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>
>
>
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-09-28 10:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 11:05 xen-2.0 20040923 and previous: rpm crash in xenU Peri Hankey
2004-09-24 12:41 ` Ian Pratt
2004-09-24 12:53 ` Peri Hankey
2004-09-24 13:22 ` Flavio Leitner
2004-09-25 10:34 ` Ian Pratt
2004-09-25 18:48 ` Peri Hankey
2004-09-27 15:54 ` Ian Pratt
2004-09-27 16:17 ` Flavio Leitner
2004-09-27 16:21 ` Ian Pratt
2004-09-27 16:28 ` Flavio Leitner
2004-09-27 17:04 ` Peri Hankey
2004-09-27 17:18 ` Flavio Leitner
2004-09-28 10:33 ` Peri Hankey [this message]
2004-09-28 12:39 ` Ian Pratt
2004-09-28 13:57 ` Peri Hankey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41593E11.4020300@thegreen.co.uk \
--to=mpah@thegreen.co.uk \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=fbl@conectiva.com.br \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.