On Fri, 14 Dec 2007, Jiri Slaby wrote: > On 12/14/2007 11:01 AM, Arun Thomas wrote: > > On Dec 14, 2007 4:53 AM, Andrew Morton <[EMAIL PROTECTED]> wrote: > >> On Fri, 14 Dec 2007 04:10:31 -0500 "Arun Thomas" <[EMAIL PROTECTED]> wrote: > >> > > some time before: > [ 20.101392] Calibrating delay using timer specific routine.. > 5989.01 BogoMIPS (lpj=11978034) > > >>> [ 20.185881] Initializing CPU#1 > >>> [ 527.926587] Calibrating delay using timer specific routine.. > >>> 200566.59 BogoMIPS (lpj=401133185) > >> Silly question: is that delay actually observeable by a human, > >> or is it just a leap in the printk timestamping? > > > > Good question. Yes, it's human-observable. The kernel "hangs" for 8 > > mins by my wall clock, and then it continues to boot up. > > By the way, the same processor here, but > Calibrating delay using timer specific routine.. 5984.76 BogoMIPS > (lpj=11969527) > for the second core. > > The calibration is some kind of weird there. > > If any info needed from me, feel free to ask (x86_64 here). No problems with > it > here AFAIK.
The problem is caused by an SMI during the calibration routine. We really need to come up with a solid solution which does not rely on the periodic timer coming in, when there is something else (HPET, pm_timer) available. I have a look into this. Arun, do you have an USB keyboard plugged in ? If not, can you connect one and check, whether it changes things or not ? Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/