From: Arjan van de Ven <arjanv@redhat.com>
To: Will Dinkel <wdinkel@atipa.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86_64 interrupts handled by CPU0 only
Date: 07 May 2003 22:46:17 +0200 [thread overview]
Message-ID: <1052340377.1404.4.camel@laptop.fenrus.com> (raw)
In-Reply-To: <1052326953.22518.184.camel@zappa>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
On Wed, 2003-05-07 at 19:02, Will Dinkel wrote:
> Are all interrupts supposed to be handled by CPU0 on x86_64, or is
> something amiss? I'm getting the following on Mandrake Corporate Server
> 2.1:
>
> ---
> [root@lab180 root]# uname -r -v -m -o
> 2.4.19-31mdksmp #1 SMP Thu Apr 17 09:34:46 EDT 2003 x86_64 GNU/Linux
> [root@lab180 root]# cat /proc/interrupts
> CPU0 CPU1
> 0: 447602 0 IO-APIC-edge timer
> 1: 424 0 IO-APIC-edge keyboard
> 2: 0 0 XT-PIC cascade
> 12: 851 0 IO-APIC-edge PS/2 Mouse
> 14: 25038 1 IO-APIC-edge ide0
> 15: 4930 1 IO-APIC-edge ide1
> 19: 0 0 IO-APIC-level usb-ohci, usb-ohci
> 24: 105196 0 IO-APIC-level ioc0, eth0
> 25: 46 0 IO-APIC-level ioc1
> NMI: 2235 3808
> LOC: 447494 447555
> ERR: 0
> MIS: 0
> ---
>
> I see this behavior on systems using either the MSI or Tyan dual-opteron
> boards. I also see it on RedHat's preview x86_64 distribution (kernel
> version 2.4.20-9.2).
please use irqbalanced ;)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-05-07 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 17:02 x86_64 interrupts handled by CPU0 only Will Dinkel
2003-05-07 20:46 ` Arjan van de Ven [this message]
2003-05-10 20:47 ` Pavel Machek
[not found] <1052326953.22518.184.camel@zappa.suse.lists.linux.kernel>
2003-05-07 21:12 ` 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=1052340377.1404.4.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wdinkel@atipa.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