Jul 17 12:50:46 orion1 acpidev: [ID 230966 kern.warning] WARNING: acpidev: failed to get MADT table in acpidev_walk_apic().
This doesn't mean ACPI failed to initialize, just that the MADT couldn't be found -- which is extremely weird.
Jul 17 12:50:46 orion1 unix: [ID 933431 kern.warning] WARNING: cpupm_init: processor 0: unable to get ACPI handle
This is a non-fatal error common on systems where CPU power management information is not present in the ACPI tables.
The interesting part is that max_ncpus=16 and ncpus=8. So why is that we end up skipping half the CPUs in start_other_cpus() even if we can't get MADT handle? I have attached /var/adm/messages, acpidump, summary and DATA files. Any workarounds for the time being?
If we had the apic ids of the cpus on your system we could fake up a MADT and you could them put that in /boot/acpi/tables, but that shouldn't be necessary; something else is going on.
--S _______________________________________________ on-discuss mailing list on-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/on-discuss
