On Altix (sn2) machines the "Error parsing MADT" message is misleading because the lack of IOSAPIC entries is expected. Since I am sure someone will ask, I have been told that the chance of this changing anytime soon is close to nil. Signed-off-by: George Beshers --- acpi.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff -purN linux-2.6.23/arch/ia64/kernel/acpi.c linux-2.6.23.b/arch/ia64/kernel/acpi.c --- linux-2.6.23/arch/ia64/kernel/acpi.c 2007-10-09 16:31:38.000000000 -0400 +++ linux-2.6.23.b/arch/ia64/kernel/acpi.c 2007-10-09 21:43:29.283569798 -0400 @@ -678,9 +678,14 @@ int __init acpi_boot_init(void) /* I/O APIC */ if (acpi_table_parse_madt - (ACPI_MADT_TYPE_IO_SAPIC, acpi_parse_iosapic, NR_IOSAPICS) < 1) - printk(KERN_ERR PREFIX - "Error parsing MADT - no IOSAPIC entries\n"); + (ACPI_MADT_TYPE_IO_SAPIC, acpi_parse_iosapic, NR_IOSAPICS) < 1) { + if (ia64_platform_is("sn2")) + printk(KERN_NOTICE + "SGI/SN machines do not have IOSAPIC entries\n"); + else + printk(KERN_ERR PREFIX + "Error parsing MADT - no IOSAPIC entries\n"); + } /* System-Level Interrupt Routing */