From: Corey Minyard <minyard@acm.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NMI watchdog not ticking at the right intervals
Date: Fri, 25 Oct 2002 14:54:11 -0500 [thread overview]
Message-ID: <3DB9A163.1050306@acm.org> (raw)
In-Reply-To: <200210251802.UAA18166@harpo.it.uu.se>
Mikael Pettersson wrote:
>On Fri, 25 Oct 2002 09:09:10 -0500, Corey Minyard wrote:
>
>
>>As I have been working on my NMI patch, I have noticed that the NMI
>>watchdog does not seem to be ticking correctly. I've tried 2.4 and 2.5
>>kernels, and I get the same results. From my reading of the code, it
>>should tick once a second. However, I have had the time between ticks
>>vary from around 33 to over 100 seconds. Tbe time between ticks is
>>different on every boot, but is consistent once booted. Is there some
>>divider register that's not getting initialized?
>>
>>Here's my cpuinfo:
>>
>>processor : 0
>>cpu_package : 0
>>vendor_id : GenuineIntel
>>cpu family : 6
>>model : 11
>>model name : Intel(R) Pentium(R) III Mobile CPU 1066MHz
>>
>>
>
>(Me thinks "speedstep?")
>
>Do you boot with nmi_watchdog=1 or 2?
>
It's set to 2 (local APIC). Actually, when I set it to 1 (in 2.5) the
code overrides it and sets it to 2. But 2 is what it is running with now.
>The perfctr + local-APIC driven NMI watchdog is dependent
>on the CPU's clock frequency. If this changes, the NMI rate
>will change accordingly.
>
>The NMI rate may also be affected by APM/ACPI and how often
>the kernel executes HLT.
>
This board is not doing speed stepping. It's running derated for
reliability.
But that makes me think of something...
If I put a program into an infinite loop, then it will step every second
like it is supposed to. That makes sense now.
Thanks,
-Corey
next prev parent reply other threads:[~2002-10-25 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 18:02 Mikael Pettersson
2002-10-25 19:54 ` Corey Minyard [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-25 14:09 Corey Minyard
2002-10-25 17:47 ` george anzinger
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=3DB9A163.1050306@acm.org \
--to=minyard@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome