Configuring Solaris ACPI at boot-time
As part of the new Solaris ACPI subsystem integrated as part of Newboot, I've added a new bit to the "acpi-user-options" boot option.
Historically, acpi-user-options=0x2 has been the only publicly documented option, and is used to disable Solaris use of ACPI for CPU enumeration and interrupt routing. Generally speaking, the pattern has historically been to set acpi-user-options=0x2 if there's any problem at all, just to see if the system works better. Changes made in Solaris 10 have made ACPI use in Solaris much more robust, so disabling use of ACPI should not be required as frequently as in previous releases.
Beginning with Newboot, integrated into Solaris source in April (2005), acpi-user-options has changed in a couple of ways:
The previous ACPI subsystem did not put the system into “ACPI” mode, but left the system in “Legacy” mode, where the system BIOS retains control of the system. The new Solaris ACPI subsystem based on ACPI CA now places the system in ACPI mode by default.
acpi-user-options=0x8 causes the new Solaris ACPI subsystem to leave the system in Legacy mode. This is the first option one should try if ACPI-related issues are suspected.
acpi-user-options=0x4 is present in Solaris 10, and causes both the previous Solaris ACPI subsystem and the new subsystem to partially disable use of ACPI – but Hyper-Threaded CPUs are still enumerated using ACPI tables. This is the second option one should use if ACPI-related issues are suspected.
acpi-user-options=0x2 is present in Solaris 10, and causes both the previous Solaris ACPI subsystem and the new subsystem to disable the use of ACPI.
Generally speaking, the new Solaris ACPI subsystem seems to do very well by default. I'll blog separately about some issues I've diagnosed that appeared to be ACPI-related but turned out to be to something else (BIOS issues, actually).
Posted by danasblog [ACPI] ( June 14, 2005 10:21 AM ) Permalink | Comments[8]

Posted by Tony Schultz on February 14, 2006 at 02:34 PM PST #
Posted by Dana H. Myers on March 06, 2006 at 12:44 PM PST #
Posted by Huub van Niekerk on August 09, 2006 at 01:29 AM PDT #
Posted by Dana H. Myers on August 30, 2006 at 03:23 PM PDT #
Posted by Adrianus B. Kurnadi on September 22, 2006 at 03:45 AM PDT #
Hi Dana,
I have search in the internet about the bug I mentioned on my comment above.
I find similar bugs in this url :
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=5047712
But in my case the hardware is a bit different :
vendor 0x8086 device 0x265c
Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller.
I think maybe similar approach can be done to fix this bug
Do you know how I can post bug report for Solaris/OpenSolaris ?
Posted by 202.59.168.198 on January 28, 2008 at 01:40 AM PST #
Adrianus, I do not believe the bug you are seeing with your Acer is the same as CR 5047712; the symptoms you describe sound like an "interrupt routing" problem. Am I correct to understand that acpi-user-options=0x8 makes your Acer boot Solaris correctly, but the Wi-Fi button no longer works?
Posted by Dana H. Myers on January 28, 2008 at 08:54 AM PST #
Thanks!
The user-acpi-options was useful in working around a first time boot problem on Nexenta Core Platform v1.0:
We saw errors with 'Gen-ATA ' error code: 0x3 repeating.
The user-acpi-options=0x2 and 0x8 both allowed the Solaris kernel to boot properly.
Documented at:
https://bugs.launchpad.net/nexenta/+bug/192823
Posted by lent on February 26, 2008 at 11:58 AM PST #