From: Willy Tarreau <willy@w.ods.org>
To: Simon Kirby <sim@netnation.com>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [2.4.21-pre3] APIC routing broken on ASUS P2B-DS
Date: Tue, 28 Jan 2003 07:06:29 +0100 [thread overview]
Message-ID: <20030128060629.GA19346@alpha.home.local> (raw)
In-Reply-To: <20030128004906.GA3439@netnation.com>
On Mon, Jan 27, 2003 at 04:49:06PM -0800, Simon Kirby wrote:
> 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
Hi !
Well, yesterday I've noticed the same problem here on an Asus A7M266-D. I
haven't had time to test every previous version, but I've searched through the
archives, and other similar reports have been posted since December. I believe
that some people did have it with 2.4.21pre2 too.
Your report narrows the problem down to fewer releases than what I saw first,
and if I have time I'll test 2.4.20 and 2.4.21pre1 here.
BTW, I don't know if -ac exhibits the same problem. Alan, would you check your
SMP box, please ?
Cheers,
Willy
next prev parent reply other threads:[~2003-01-28 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 0:49 [2.4.21-pre3] APIC routing broken on ASUS P2B-DS Simon Kirby
2003-01-28 6:06 ` Willy Tarreau [this message]
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=20030128060629.GA19346@alpha.home.local \
--to=willy@w.ods.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sim@netnation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.