|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] xen-2.0 20040923 and previous: rpm crash in xenU
Thanks for sending the test - one point of interest is that my /proc/cpuinfo doesn't match your expectations - presumably an AMD Athlon(tm) XP 2400+ is running at 2400MHz. The main point however is that the results are indeed different in the two domains: ---------------- xen0 ------------------------ [me@xen0 testing]$ ./time-testfind_cpu_speed: error parsing /proc/cpuinfo for cpu MHz. Assume 2400 MhzCPU speed = 2400 MHz ........................................................................................................... ........................................................................................................... ... (lots of dots) [me@xen0 testing]$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 8 model name : AMD Athlon(tm) XP 2400+ stepping : 1 cache size : 256 KB fdiv_bug : no hlt_bug : yes f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yesflags : fpu msr pae mce cx8 apic sep mca cmov pat pse36 mmx sse syscall mmxext 3dnowext 3dnow bogomips : 4010.80 ---------------- xenU ------------------------ [me@xenU testing]$ ./time-testfind_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 .nanosleep(20000us): gtod 0 .nanosleep(20000us): gtod 0 .nanosleep(20000us): gtod 0 .nanosleep(20000us): gtod 0 ... (lots of gtod 0s) [me@xenU testing]$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 8 model name : AMD Athlon(tm) XP 2400+ stepping : 1 cache size : 256 KB fdiv_bug : no hlt_bug : yes f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yesflags : fpu msr pae mce cx8 apic sep mca cmov pat pse36 mmx sse syscall mmxext 3dnowext 3dnow bogomips : 3263.69I hope this will help nail it down - I notice also that the bogomips measure is different. No time for more just now - but I have a more general question about lvm2 cows and snapshots, which I will put in a separate message. 'A snapshot is not a cow' as the liftman said to Babar the Elephant. In fact the problem is that snapshots hold on to each other's tails. Thanks for your help. Peri Ian Pratt wrote: 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: ------------------------------------------------------- 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@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |