All of lore.kernel.org
 help / color / mirror / Atom feed
From: Howard Chu <hyc@symas.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: APIC frequency too slow on HP dv5z
Date: Thu, 02 Oct 2008 02:05:45 -0700	[thread overview]
Message-ID: <48E48EE9.9090900@symas.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0810021052410.5549@apollo.tec.linutronix.de>

Thomas Gleixner wrote:
> On Tue, 30 Sep 2008, Howard Chu wrote:
>
>> More often than not, on a warm boot I see something like this
>>
>> msg.new:[    1.940031] Using local APIC timer interrupts.
>> msg.new:[    1.944031] APIC timer calibration result 466046
>> msg.new:[    1.944031] Detected 0.466 MHz APIC timer.
>> msg.new:[    1.944031] APIC frequency too slow, disabling apic timer
>>
>> On cold boots it may see 12.5MHz, or may not...
>>
>> [    2.000584] Using local APIC timer interrupts.
>> [    2.004067] APIC timer calibration result 12500236
>> [    2.004080] Detected 12.500 MHz APIC timer.
>>
>> I haven't figured out yet what the pattern is behind the behavior. Has anyone
>> else seen this kind of problem before?
>
> Hmm, strange. Which kernel version ?

I only started paying attention recently. 2.6.27-rc4 thru rc7 for sure. I'm 
running rc7 right now, that's what those log snippets are from.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/

  reply	other threads:[~2008-10-02  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 19:55 APIC frequency too slow on HP dv5z Howard Chu
2008-10-02  8:53 ` Thomas Gleixner
2008-10-02  9:05   ` Howard Chu [this message]
2008-10-02  9:13     ` Thomas Gleixner
2008-10-02 22:56       ` Howard Chu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48E48EE9.9090900@symas.com \
    --to=hyc@symas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.