From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: cmulcahy@avesi.com
Cc: Akira Tsukamoto <akira-t@suna-asobi.com>,
john stultz <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: athlon x2 + 2.6.14 + SMP = fast clock
Date: Mon, 21 Nov 2005 10:28:03 +0100 [thread overview]
Message-ID: <200511211028.04431.arekm@pld-linux.org> (raw)
In-Reply-To: <1132537722.9627.145.camel@harry>
On Monday 21 November 2005 02:48, Christopher Mulcahy wrote:
> I am using arch amd64.
>
> I applied this patch.
>
> http://bugzilla.kernel.org/attachment.cgi?id=6061&action=view
>
> It applies to 2.6.14.2 so long as you remove the static declaration of
> 'int disable_timer_pin_1'
>
> It appears to have solved my problem.
I wonder is this is x86_64 only problem?
I'm having the same problem on dual xeon 1.8GHz i686 with HT enabled, kernel
2.6.14.2-4smp. Clock runs twice fast. Previously I was using 2.6.11 kernel
with no such problem.
cmdline is: acpi=ht nmi_watchdog=1
Unfortunately I can't do any testing right now on this machine but I'll try
acpi_skip_timer_override cmdline option as soon as I can.
> Chris
00:00.0 Host bridge: Intel Corporation E7500 Memory Controller Hub (rev 03)
00:02.0 PCI bridge: Intel Corporation E7500/E7501 Hub Interface B PCI-to-PCI
Bridge (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #1) (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corporation 82801CA LPC Interface Controller (rev
02)
00:1f.1 IDE interface: Intel Corporation 82801CA Ultra ATA Storage Controller
(rev 02)
00:1f.3 SMBus: Intel Corporation 82801CA/CAM SMBus Controller (rev 02)
01:01.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100]
(rev 10)
01:02.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
02:1c.0 PIC: Intel Corporation 82870P2 P64H2 I/OxAPIC (rev 03)
02:1d.0 PCI bridge: Intel Corporation 82870P2 P64H2 Hub PCI Bridge (rev 03)
02:1e.0 PIC: Intel Corporation 82870P2 P64H2 I/OxAPIC (rev 03)
02:1f.0 PCI bridge: Intel Corporation 82870P2 P64H2 Hub PCI Bridge (rev 03)
03:03.0 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)
04:01.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet
Controller (Copper) (rev 01)
# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 47938745 0 0 0 IO-APIC-edge timer
2: 0 0 0 0 XT-PIC cascade
4: 41666 0 0 0 IO-APIC-edge serial
8: 3 0 0 0 IO-APIC-edge rtc
145: 0 0 0 0 IO-APIC-level
uhci_hcd:usb1
153: 49053282 0 0 0 IO-APIC-level eth0
169: 3839290 0 0 0 IO-APIC-level qla2300
177: 45129167 0 0 0 IO-APIC-level eth1
NMI: 47939763 47939734 47939732 47939731
LOC: 47943502 47944012 47944469 47944277
ERR: 0
MIS: 0
--
Arkadiusz Miśkiewicz PLD/Linux Team
http://www.t17.ds.pwr.wroc.pl/~misiek/ http://ftp.pld-linux.org/
next prev parent reply other threads:[~2005-11-21 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 20:40 athlon x2 + 2.6.14 + SMP = fast clock Christopher Mulcahy
2005-11-08 21:38 ` john stultz
2005-11-09 1:02 ` Christopher Mulcahy
2005-11-08 22:59 ` john stultz
2005-11-20 18:12 ` Akira Tsukamoto
2005-11-21 1:48 ` Christopher Mulcahy
2005-11-21 9:28 ` Arkadiusz Miskiewicz [this message]
2005-11-22 19:01 ` Akira Tsukamoto
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=200511211028.04431.arekm@pld-linux.org \
--to=arekm@pld-linux.org \
--cc=akira-t@suna-asobi.com \
--cc=cmulcahy@avesi.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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