From: YhLu <YhLu@tyan.com>
To: "'Andi Kleen'" <ak@muc.de>
Cc: "'Mikael Pettersson'" <mikpe@csd.uu.se>,
"'jamesclv@us.ibm.com'" <jamesclv@us.ibm.com>,
"'Matt_Domsch@dell.com'" <Matt_Domsch@dell.com>,
"'discuss@x86-64.org'" <discuss@x86-64.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'suresh.b.siddha@intel.com'" <suresh.b.siddha@intel.com>
Subject: RE: 256 apic id for amd64
Date: Tue, 11 Jan 2005 11:11:45 -0800 [thread overview]
Message-ID: <3174569B9743D511922F00A0C943142307291407@TYANWEB> (raw)
On 2.4.28 84 bit
~ # cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 5302 19 0 0 IO-APIC-edge timer
1: 0 0 0 0 IO-APIC-edge keyboard
2: 0 0 0 0 XT-PIC cascade
4: 175 0 0 0 IO-APIC-edge serial
19: 3 0 0 0 IO-APIC-level ohci1394
22: 0 0 0 0 IO-APIC-level usb-ohci
23: 0 0 0 0 IO-APIC-level ehci_hcd
NMI: 147 139 110 77
LOC: 5063 5060 5061 5062
ERR: 406
MIS: 0
~ # cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 5612 19 0 0 IO-APIC-edge timer
1: 0 0 0 0 IO-APIC-edge keyboard
2: 0 0 0 0 XT-PIC cascade
4: 226 0 0 0 IO-APIC-edge serial
19: 3 0 0 0 IO-APIC-level ohci1394
22: 0 0 0 0 IO-APIC-level usb-ohci
23: 0 0 0 0 IO-APIC-level ehci_hcd
NMI: 147 139 110 77
LOC: 5373 5370 5371 5372
ERR: 406
MIS: 0
-----Original Message-----
From: YhLu
Sent: Tuesday, January 11, 2005 11:05 AM
To: YhLu; Andi Kleen
Cc: 'Mikael Pettersson'; jamesclv@us.ibm.com; Matt_Domsch@dell.com;
discuss@x86-64.org; linux-kernel@vger.kernel.org; suresh.b.siddha@intel.com
Subject: RE: 256 apic id for amd64
On 2.6.10 32 bit, it only crash core1/node0, still can go on but lost one
cpu.
~ # cat /proc/interrupts
CPU0 CPU1 CPU2
0: 47612 5 7643 IO-APIC-edge timer
2: 0 0 0 XT-PIC cascade
4: 365 0 1 IO-APIC-edge serial
8: 0 0 0 IO-APIC-edge rtc
17: 0 0 0 IO-APIC-level libata
18: 0 0 0 IO-APIC-level libata
19: 2 0 1 IO-APIC-level ohci1394
22: 0 0 0 IO-APIC-level ohci_hcd
23: 0 0 0 IO-APIC-level ehci_hcd
NMI: 0 0 0
LOC: 49259 49254 49253
ERR: 5729
MIS: 0
~ #
-----Original Message-----
From: Yinghai Lu [mailto:yhlu@tyan.com]
Sent: Tuesday, January 11, 2005 10:50 AM
To: 'Andi Kleen'
Cc: 'Mikael Pettersson'; 'jamesclv@us.ibm.com'; 'Matt_Domsch@dell.com';
'discuss@x86-64.org'; 'linux-kernel@vger.kernel.org';
'suresh.b.siddha@intel.com'
Subject: RE: 256 apic id for amd64
> It looks like the timer interrupt goes to the second CPU.
Even I don't lift the apic id for bsp, the MB with Nvidia chipset still can
not start core1/node0, from core0/node0 in kernel 2.6. But the 2.4.28 (32
bit, 64 bit) works well.
How come?
YH
next reply other threads:[~2005-01-11 19:00 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 19:11 YhLu [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-11 19:04 256 apic id for amd64 YhLu
2005-01-10 20:48 YhLu
2005-01-10 20:46 YhLu
2005-01-11 5:36 ` Andi Kleen
2005-01-10 20:37 YhLu
2005-01-10 20:09 YhLu
2005-01-10 20:18 ` Andi Kleen
2005-01-10 19:41 YhLu
2005-01-10 19:43 ` Andi Kleen
2005-01-11 0:42 ` James Cleverdon
2005-01-11 3:28 ` Siddha, Suresh B
2005-01-11 4:42 ` Andi Kleen
2005-01-10 18:48 YhLu
2005-01-10 18:45 ` Andi Kleen
2005-01-10 18:44 Andi Kleen
2005-01-11 4:04 ` Siddha, Suresh B
2005-01-11 4:39 ` Andi Kleen
2005-01-11 17:50 ` Andi Kleen
2005-01-08 2:53 YhLu
2005-01-09 23:56 ` James Cleverdon
2005-01-08 2:37 Mikael Pettersson
2005-01-08 15:46 ` Andi Kleen
2005-01-08 1:50 YhLu
2005-01-08 0:50 YhLu
2005-01-08 0:42 ` Andi Kleen
2005-01-08 0:28 YhLu
2005-01-08 0:26 ` James Cleverdon
2005-01-08 0:34 ` Andi Kleen
2005-01-08 0:04 YhLu
2005-01-08 0:12 ` James Cleverdon
2005-01-07 21:44 YhLu
2005-01-07 22:18 ` Andi Kleen
2005-01-07 21:14 YhLu
2005-01-07 21:12 ` Andi Kleen
2005-01-07 19:43 YhLu
2005-01-07 19:40 ` Andi Kleen
2005-01-07 18:27 YhLu
2005-01-07 19:29 ` Andi Kleen
2005-01-07 18:19 YhLu
2005-01-07 19:29 ` Andi Kleen
2005-01-07 2:53 YhLu
2005-01-07 12:24 ` Andi Kleen
2005-01-08 1:30 ` James Cleverdon
2005-01-07 1:06 YhLu
2005-01-07 12:44 ` Andi Kleen
2004-12-30 23:19 YhLu
2004-12-30 23:16 YhLu
2004-12-29 4:43 YhLu
2004-12-30 18:45 ` Andi Kleen
2004-12-30 22:56 ` Matt Domsch
2004-12-30 23:26 ` 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=3174569B9743D511922F00A0C943142307291407@TYANWEB \
--to=yhlu@tyan.com \
--cc=Matt_Domsch@dell.com \
--cc=ak@muc.de \
--cc=discuss@x86-64.org \
--cc=jamesclv@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=suresh.b.siddha@intel.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;
as well as URLs for NNTP newsgroup(s).