From: tab@snarc.org (Vincent Hanquez)
To: nils toedtmann <xen-devel@nils.toedtmann.net>
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
Robin Green <greenrd@presidium.org>,
xen-devel@lists.sourceforge.net
Subject: Re: unstable binaries
Date: Tue, 15 Mar 2005 20:16:35 +0100 [thread overview]
Message-ID: <20050315191635.GA12564@snarc.org> (raw)
In-Reply-To: <20050307204720.GA10159@gandalf.intern.marcant.net>
On Mon, Mar 07, 2005 at 09:47:20PM +0100, nils toedtmann wrote:
> Ok, after lots of compiling, rebooting & testing, i got this picture:
>
> The error "wget: retr.c:293: calc_rate: Assertion `msecs >= 0' failed."
> is still present with xen-2.0-testing ("ChangeSet@1.1755, 2005-03-04
> 00:57:22"), but now i have to trigger them by higher load. I was not
> able to reproduce it on a vanilla kernel with same config (besides
> ARCH specific options).
> <<<test_output>>>
> nanosleep02 1 FAIL : Remaining sleep time 4010000 usec doesn't match with the expected 3999236 usec time
> nanosleep02 1 FAIL : child process exited abnormally
> incrementing stop
> <<<execution_status>>>
> duration=1 termination_type=exited termination_id=1 corefile=no
> cutime=0 cstime=0
> <<<test_end>>>
the failure is just a precision range problem. increasing the nanosleep
USEC_PRECISION to 10 times more make the test suceed.
Now running with HZ = 1000 make the precision problem disappear (at the
expense of awakening the test 700ns too soon and still failing ..)
Could you try running with HZ = 1000 to see if there are still problems
with your programs ?
Also the strace output of the wget program failing might be handy to
know if there's a link with nanosleep at least.
--
Vincent Hanquez
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-15 19:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 14:38 unstable binaries Ian Pratt
2005-03-04 13:29 ` nils toedtmann
2005-03-07 20:47 ` nils toedtmann
2005-03-15 19:16 ` Vincent Hanquez [this message]
2005-03-16 10:18 ` Nils Toedtmann
2005-03-16 10:57 ` Vincent Hanquez
-- strict thread matches above, loose matches on Subject: below --
2005-03-16 11:57 Ian Pratt
2005-03-16 10:34 Ian Pratt
2005-03-16 11:16 ` Nils Toedtmann
2005-03-11 16:59 Michael Rice
2005-03-07 22:01 Ian Pratt
2005-03-02 22:28 Ian Pratt
2005-03-02 17:54 Ian Pratt
2005-03-02 22:15 ` nils toedtmann
2005-03-02 23:49 ` nils toedtmann
2005-03-03 14:25 ` nils toedtmann
2005-03-03 22:54 ` Tommi Virtanen
2005-03-04 12:39 ` Robin Green
2005-03-04 13:27 ` nils toedtmann
2005-03-04 13:30 ` Robin Green
2005-03-02 14:42 nils toedtmann
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=20050315191635.GA12564@snarc.org \
--to=tab@snarc.org \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=greenrd@presidium.org \
--cc=xen-devel@lists.sourceforge.net \
--cc=xen-devel@nils.toedtmann.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.