I see this on 500 MHz Fire V100. [ 59.253164] calibrate_delay_direct() timer_rate_max=55726 timer_rate_min=55504 pre_start=329128453 pre_end=329184069 [ 59.283196] calibrate_delay_direct() timer_rate_max=55721 timer_rate_min=55503 pre_start=329295308 pre_end=329350920 [ 59.313228] calibrate_delay_direct() timer_rate_max=55722 timer_rate_min=55502 pre_start=329462156 pre_end=329517768 [ 59.343261] calibrate_delay_direct() timer_rate_max=55723 timer_rate_min=55505 pre_start=329629002 pre_end=329684616 [ 59.373293] calibrate_delay_direct() timer_rate_max=55718 timer_rate_min=55499 pre_start=329795855 pre_end=329851464 [ 59.373349] Calibrating delay using timer specific routine.. 11.14 BogoMIPS (lpj=55722) 11 bogomips seems ... slow. Older machines like Ultra 1, Ultra 5/10 show double the CPU clock speed as bogomips. Is it normal or is something clock-related broken? cpu : TI UltraSparc IIe (Hummingbird) fpu : UltraSparc IIe integrated FPU pmu : ultra12 prom : OBP 4.0.18 2002/05/23 18:22 type : sun4u ncpus probed : 1 ncpus active : 1 D$ parity tl1 : 0 I$ parity tl1 : 0 Cpu0ClkTck : 000000001dcd6500 MMU Type : Spitfire Netra X1 has it also similarly. My dmesg logs go back to August 2008 and it has been the same always (at least at about 2.6.25), so it's not anything recent. -- Meelis Roos (mroos@xxxxxxxx) -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
