linux-kernel - Re: PROBLEM: E6850 has an 8+ minute delay during boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.0.99999.0712141140310.10584@localhost.localdomain>
Date:	Fri, 14 Dec 2007 11:43:37 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Jiri Slaby <jirislaby@...il.com>
cc:	Arun Thomas <arun.thomas@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>
Subject: Re: PROBLEM: E6850 has an 8+ minute delay during boot

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 <akpm@...ux-foundation.org> wrote:
> >> On Fri, 14 Dec 2007 04:10:31 -0500 "Arun Thomas" <arun.thomas@...il.com> 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/