If during boot no ACPI 2.0 SLIT table is found we do not initialise
the NUMA node distance table, leaving all node distances as 0.
This causes IA-64 to fail the regression tests for libnuma. Also,
when we have a bad formatted table we will set all node distances
to 10. Both of these forms lose
+ printk(KERN_INFO Building NUMA distance from ACPI 2.0 SLIT\n);
This printk just looks like noise during boot. Surely this
is normal behavior on a NUMA system?
+ printk(KERN_INFO No SLIT table, defaulting NUMA distance\n);
But this one deserves more prominence than just KERN_INFO.
On 8/14/07, Luck, Tony [EMAIL PROTECTED] wrote:
Some help is needed with debugging of a hang.
A system hits BINIT once in a while and the processors are all
spinning on the address 0x0012C00 and if the HT is off the address
becomes 0x002A80. This is a physical address captured on
