On Thursday 29 January 2004 17:31, Andi Kleen wrote:
On Thu, 29 Jan 2004 16:19:57 +0000 "Eugene de Villiers" <edevilliers@hotmail.com> wrote:
[cc'ing back to suse-amd. Please keep discussions there]
<6>Scanning NUMA topology in Northbridge 24 <3>Node 0 using interleaving mode 1/0 <6>No NUMA configuration found <6>Faking a node at 0000000000000000-000000009fff0000 <4>Bootmem setup node 0 0000000000000000-000000009fff0000 <7>ACPI: have wakeup address 0x10000002000
The kernel is NUMA. It cannot access the northbridge of the second CPU, so NUMA support is turned off. That's some hardware problem at your side, maybe the second CPU or the motherboard are broken or not correctly plugged in.
I have the same here. Tyan Thunder K8W, with factory BIOS: <6>Scanning NUMA topology in Northbridge 24 <3>Node 0 using interleaving mode 1/0 <6>No NUMA configuration found <6>Faking a node at 0000000000000000-000000007fff0000 <4>Bootmem setup node 0 0000000000000000-000000007fff0000 The kernel is 2.6.1-X8664-1. But according to xosview my second CPU is really running, so seems to be plugged into the socket :-) dmesg has the following lines: Starting migration thread for cpu 0 Bringing up 1 CPU 1 IS NOW UP! Starting migration thread for cpu 1 CPUS done 2 There is a BIOS setting called "BIOS -> AML ACPI table", which is set to "Enabled" Helptext: "Set this value to allow the ACPI BIOS to add a pointer to an OEMB table in the Root System Description Table (RSDT). Note: OEMB table is used to pass POST data to the AML code during ACPI O/S operations." In memory config "Bank interleaving" and "Node interleaving" are disabled. May be this explains, why xengine displays only 200rpms (on a Matrox G550). Some problem in ACPI implementation or BIOS bug? Regards Frank