Re: xen-2.0 20040923 and previous: rpm crash in xenU

[Peri Hankey <mpah@thegreen.co.uk>]

The timer question seems to involve more than just the processor type:

------------todays build: xen0 running Mandrake 10: OK
[me@a4 testing]$ ./time-test
CPU speed = 2008 MHz
...............................................

[me@a4 testing]$ rpm -qa
mktemp-1.5-11mdk
libpwdb0-0.61.2-3mdk
make-3.80-5mdk
gettext-base-0.13.1-1mdk
ifplugd-0.21b-1mdk
libgdbm2-1.8.0-24mdk
...

-------------todays build: a41: xenU running Mandrake 10.0: FAIL
[me@a41 testing]$ ./time-test
CPU speed = 2008 MHz
nanosleep(20000us): gtod 0
.nanosleep(20000us): gtod 0
.nanosleep(20000us): gtod 0
.nanosleep(20000us): gtod 0

[me@a41 testing]$ rpm -qa
Floating point exception (core dumped)
[peri@a41 testing]$

--------------- todays build: a37: xenU running PLD Linux: OK
[me@a37 testing]$ ./time-test
CPU speed = 2008 MHz
............................................................

[peri@a37 testing]$ rpm -qa
FHS-2.3-1
basesystem-1.99-2
acl-2.2.22-2
cracklib-2.7-18
cracklib-dicts-2.7-18
make-3.80-5
pam-0.77.3-11
...

I don't think I've yet seen the rpm crash on the PLD Linux distribution. 
So it looks like a combination of Athlon with some subtle difference in 
the way the libraries are compiled.

But Flavio, are you saying that you have the rpm problem that I have but 
don't see the same test results as me?

And by the way, I was very interested to hear about your conectiva rpm 
for xen - is it downloadable?

Thanks to all
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