From: Simon Kirby <sim@netnation.com>
To: linux-kernel@vger.kernel.org
Subject: [2.4.21-pre3] APIC routing broken on ASUS P2B-DS
Date: Mon, 27 Jan 2003 16:49:06 -0800 [thread overview]
Message-ID: <20030128004906.GA3439@netnation.com> (raw)
Something broke between 2.4.20 and 2.4.21-pre3 which is causing
interrupts to not be routed the second CPU. I saw the problem on one box
and copied the kernel to another which then had the same problem (both
ASUS P2B-DS boards, one with PIII CPUs, one with PII CPUs).
[sroot@devel:/]# cat /proc/interrupts
CPU0 CPU1
0: 114480 0 IO-APIC-edge timer
1: 2 0 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
8: 3 0 IO-APIC-edge rtc
16: 30707 0 IO-APIC-level eth0
19: 3260 0 IO-APIC-level aic7xxx
NMI: 0 0
LOC: 114405 114404
ERR: 0
MIS: 0
With 2.4.20:
[sroot@devel:/root]# cat /proc/interrupts
CPU0 CPU1
0: 23627 27340 IO-APIC-edge timer
1: 0 2 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
8: 2 1 IO-APIC-edge rtc
16: 1671 2 IO-APIC-level eth0
19: 965 979 IO-APIC-level aic7xxx
NMI: 0 0
LOC: 50893 50891
ERR: 0
MIS: 0
...If nobody knows what happened immediately, I'll try narrowing it down
to the patch.
Simon-
[ Simon Kirby ][ Network Operations ]
[ sim@netnation.com ][ NetNation Communications ]
[ Opinions expressed are not necessarily those of my employer. ]
next reply other threads:[~2003-01-28 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 0:49 Simon Kirby [this message]
2003-01-28 6:06 ` [2.4.21-pre3] APIC routing broken on ASUS P2B-DS Willy Tarreau
2003-02-02 1:28 ` [Nearly Solved]: " Willy Tarreau
2003-02-18 7:11 ` Jeff Garzik
2003-02-19 1:21 ` Willy Tarreau
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=20030128004906.GA3439@netnation.com \
--to=sim@netnation.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