From: john stultz <johnstul@us.ibm.com>
To: Miroslaw KLABA <totoro@totoro.be>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Double Interrupt with HT
Date: Tue, 16 Dec 2003 15:50:31 -0800 [thread overview]
Message-ID: <1071618630.1013.11.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <1071615336.3fdf8d6840208@ssl0.ovh.net>
On Tue, 2003-12-16 at 14:55, Miroslaw KLABA wrote:
> I had the problem with 2.4.22, 2.4.22-ac4, 2.4.23 and 2.4.24-pre1.
Ok, so its been around awhile. Do you remember what was the last 2.4
kernel where you did not see this problem?
> The problem is that all the kernel is working "twice the speed".
> The command "while true; do date; sleep 1; done;" shows that the date is growing
> 2 seconds per second... :/
> I found a patch for irqbalance for 2.4.23, and now I don't have the problem
> anymore with the clock.
> http://www.hardrock.org/kernel/2.4.23/irqbalance-2.4.23-jb.patch
Hmm. Just skimming that patch, I notice it won't work on clustered apic
systems. They've dropped the following chunk from set_ioapic_affinity
and forgot to re-add it.
- /* pick a single cpu for clustered xapics */
- if(clustered_apic_mode == CLUSTERED_APIC_XAPIC){
- int cpu = ffs(mask)-1;
- mask = cpu_to_physical_apicid(cpu);
- }
Further I can't see how it fixes the problem, but it may just be working
around the issue. I'd be interested in what the patch author thinks.
> I think it is a bug with the via chipset, but I'm not able to get deeper in the
> kernel code.
Could be, but I suspect interrupt routing isn't happening properly at
boot time. The irqbalance code just forces it to be readjusted correctly
once your up and running.
thanks
-john
next prev parent reply other threads:[~2003-12-16 23:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 14:58 Double Interrupt with HT Miroslaw KLABA
2003-12-15 17:16 ` Herbert Poetzl
2003-12-15 17:31 ` Miroslaw KLABA
2003-12-16 19:31 ` john stultz
2003-12-16 22:55 ` Miroslaw KLABA
2003-12-16 23:50 ` john stultz [this message]
2003-12-17 3:03 ` Miroslaw KLABA
2003-12-18 3:22 ` john stultz
2003-12-18 12:14 ` Miroslaw KLABA
2003-12-18 13:51 ` Zwane Mwaikambo
2003-12-18 16:35 ` Miroslaw KLABA
2003-12-18 16:42 ` William Lee Irwin III
2003-12-18 17:31 ` William Lee Irwin III
2003-12-18 17:21 ` Zwane Mwaikambo
2003-12-19 0:32 ` Miroslaw KLABA
2003-12-19 0:38 ` Zwane Mwaikambo
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=1071618630.1013.11.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=totoro@totoro.be \
/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;
as well as URLs for NNTP newsgroup(s).