From: Bernd Paysan <bernd.paysan@gmx.de>
To: Andi Kleen <ak@suse.de>
Cc: suse-amd64@suse.com, linux-kernel@vger.kernel.org
Subject: Re: [suse-amd64] False "lost ticks" on dual-Opteron system (=> timer twice as fast)
Date: Tue, 10 May 2005 13:54:53 +0200 [thread overview]
Message-ID: <200505101355.00341.bernd.paysan@gmx.de> (raw)
In-Reply-To: <20050510111223.GH25612@wotan.suse.de>
[-- Attachment #1: Type: text/plain, Size: 2029 bytes --]
On Tuesday 10 May 2005 13:12, Andi Kleen wrote:
> > So that explains why nobody sees this problem. But the TSC-based
> > fallback timekeeping is still broken on SMP systems with PowerNow and
> > distributed IRQ handling, which both together seem to be rare enough
> > ;-).
>
> There is a patch pending for the TSC problem - using the pmtimer instead
> in this case.
>
> But the distributed timer interrupt problem is weird. It should not
> happen. You sure it was IRQ 0 that was duplicated and not "LOC" ?
Yes. Only one CPU actually gets and handles the timer interrupt, but which
one is somewhat random (for about 10 seconds, it's the same CPU, then it
switches over).
> When you watch -n1 cat /proc/interrupts does the rate roughly match
> up to 1000Hz?
Yes, and this is confirmed over longer time:
# grep timer /proc/interrupts; uptime
0: 40347440 40582285 IO-APIC-edge timer
1:26pm an 22:28, 1 user, Durchschnittslast: 0,00, 0,01, 0,04
# echo $[(3600*22+28*60)*1000] $[40347440+40582285]
80880000 80929725
Given that uptime is only accurate to the minute, this sounds very
reasonable. The distribution also is close to 50:50. That's (almost) true
for all interrupt sources:
# cat /proc/interrupts
CPU0 CPU1
0: 40523846 40753939 IO-APIC-edge timer
1: 3 189 IO-APIC-edge i8042
8: 261 280 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
15: 364369 364479 IO-APIC-edge ide1
169: 59195 55498 IO-APIC-level 3w-9xxx
177: 618198 604643 IO-APIC-level 3w-9xxx
185: 8195891 8147619 IO-APIC-level aic79xx, eth1
193: 0 30 IO-APIC-level aic79xx
201: 0 0 IO-APIC-level ohci_hcd, ohci_hcd
NMI: 1184 1013
LOC: 81273966 81271958
ERR: 0
MIS: 0
--
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-10 11:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 12:45 Bernd Paysan
2005-05-08 13:40 ` [suse-amd64] " Andi Kleen
2005-05-08 16:22 ` Bernd Paysan
2005-05-09 10:53 ` Bernd Paysan
2005-05-09 13:17 ` Bernd Paysan
2005-05-10 10:53 ` Ed Tomlinson
2005-05-10 13:32 ` Andi Kleen
2005-05-10 11:12 ` Andi Kleen
2005-05-10 11:36 ` Bernd Paysan
2005-05-10 11:54 ` Bernd Paysan [this message]
2005-05-10 13:07 ` Andi Kleen
2005-05-10 13:15 ` Bernd Paysan
2005-05-10 13:21 ` Andi Kleen
2005-05-10 13:39 ` Arjan van de Ven
2005-05-21 19:42 ` Hendrik Visage
2005-05-21 20:54 ` Scott Robert Ladd
[not found] ` <428F9FA6.1000800@coyotegulch.com>
[not found] ` <d93f04c70505211500216d8614@mail.gmail.com>
2005-05-23 11:50 ` Scott Robert Ladd
2005-05-23 23:04 ` Hendrik Visage
2005-05-25 17:06 ` Andi Kleen
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=200505101355.00341.bernd.paysan@gmx.de \
--to=bernd.paysan@gmx.de \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=suse-amd64@suse.com \
/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
all inboxes | Powered by JetHome®