Messages in this thread | | | From | YhLu <> | Subject | RE: 256 apic id for amd64 | Date | Tue, 11 Jan 2005 11:11:45 -0800 |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |