All of lore.kernel.org
 help / color / mirror / Atom feed
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 14:57:59 +0100	[thread overview]
Message-ID: <41596DE7.7000608@thegreen.co.uk> (raw)
In-Reply-To: <E1CCHGu-0003uj-00@mta1.cl.cam.ac.uk>

Here's a summary of results so far. I wasn't able to try your test on 
the fedora xenU system as it was a minimal install - I was planning to 
install extras as needed using poldek (like yum or urpmi, from PLD, 
minimal external dependencies, very handy - but it relies on rpm to do 
the actual installs).

using xen-20040927 (changelog in today's unstable doesn't suggest there 
would be much difference):

xen0 (mandrake 10.0 - 2.6.8.1-xen0)    time-test OK      rpm: OK             /lib/libc.so.6 -> libc-2.3.3.so

xenU (mandrake 10.0 - 2.6.8.1-xenU)    time-test FAIL    rpm: CRASH          /lib/libc.so.6 -> libc-2.3.3.so
xenU (fedora-2      - 2.6.8.1-xenU)    time-test ????    rpm: CRASH          /lib/libc.so.6 -> libc-2.3.3.so 
xenU (PLD Linux     - 2.6.8.1-xenU)    time-test OK      rpm: OK             /lib/libc.so.6 -> libc-2.3.3.so
xenU (Debian Sarge  - 2.6.8.1-xenU)    time-test OK      rpm: NOT AVAILABLE  /lib/libc.so.6 -> libc-2.3.2.so  

No very clear pattern - on the face of it it looks as if the same 
library version produces different results. I suppose that could be a 
result of different compiler flags and optimisation levels.

I don't know if that helps much.

-- Peri

Ian Pratt wrote:

>>Is there any kind of workaround for this nanosleep problem?
>>    
>>
>
>It's a bug, and one that's probably trivial to fix if we can pin
>down the combination of CPU and libraries etc that provoke it.
>
>Are you using the latest unstable tree? Does my test program
>still indicate a problem for you? If so, please post the output
>of /proc/cpuinfo, and information about your distribution and
>libraries.
>
>Like the only other pending bug (the network panic bug) it seems
>only to effect a minority of users, and we can't seem to
>reproduce it locally. Until we get more information I'm afraid
>there's not a lot we can do beyond simply reviewing the code.
>
>Thanks,
>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

      reply	other threads:[~2004-09-28 13:57 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
2004-09-28 12:39           ` Ian Pratt
2004-09-28 13:57             ` Peri Hankey [this message]

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=41596DE7.7000608@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.