From: "dada1" <dada1@cosmosbay.com>
To: "James Harper" <james.harper@bigpond.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: SMP and CPU1 not showing interrupts in /proc/interrupts
Date: Sun, 23 Feb 2003 11:52:01 +0100 [thread overview]
Message-ID: <01a601c2db29$98fd89d0$c700a8c0@edumazet> (raw)
In-Reply-To: <3E589799.3000105@bigpond.com>
I too had such interrupt distribution...
In my case, absolutely no interrupts was taken by CPU1, even the timer...
and I recall that timer interrupts should hit all the CPUS or strange things
can appear.
But, curiously, a
echo 3 >/proc/irq/0/smp_affinity
solved the problem for me (for IRQ 0 only of course)
I say curiously because the old smp_affinity value was 0xffffffff, so
masking the unused bits should have no effect.
Eric
> somewhere between about 2.5.53 and 2.5.62 my /proc/interrupts has gone
> from an approximately even distribution of interrupts between CPU0 and
> CPU1 to grossly uneven:
>
> CPU0 CPU1
> 0: 13223321 2233217 IO-APIC-edge timer
> 1: 13442 0 IO-APIC-edge i8042
> 2: 0 0 XT-PIC cascade
> 3: 291874 0 IO-APIC-edge serial
> 8: 3 0 IO-APIC-edge rtc
> 9: 0 0 IO-APIC-edge acpi
> 14: 18932 0 IO-APIC-edge ide0
> 15: 14 0 IO-APIC-edge ide1
> 16: 190607 1 IO-APIC-level eth0, nvidia
> 17: 3214 0 IO-APIC-level bttv0
> 18: 14249 1 IO-APIC-level ide2
> 19: 121942 0 IO-APIC-level uhci-hcd, wlan0
> NMI: 0 0
> LOC: 15458218 15458423
> ERR: 0
> MIS: 0
>
> if i really hit the system hard then CPU1 will start accruing interrupts
> but in a mostly idle state CPU1 just sits on its bum and lets CPU0
> handle them all, with the exception of irq #0, for some reason.
>
> any ideas?
>
> thanks
>
> James
>
next prev parent reply other threads:[~2003-02-23 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 9:42 James Harper
2003-02-23 10:21 ` Andrew Morton
2003-02-23 10:52 ` dada1 [this message]
2003-02-23 13:52 ` Arjan van de Ven
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='01a601c2db29$98fd89d0$c700a8c0@edumazet' \
--to=dada1@cosmosbay.com \
--cc=james.harper@bigpond.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
all inboxes | Powered by JetHome®