On 7/26/07, Aubrey Li <[EMAIL PROTECTED]> wrote: > On 7/26/07, Kaiwai Gardiner <[EMAIL PROTECTED]> wrote: > > On 26/07/07, Aubrey Li <[EMAIL PROTECTED]> wrote: > > > > > On 7/26/07, Mark Haywood <[EMAIL PROTECTED]> wrote: > > > > First of all, if I'm reading your messages correctly, you've got two > > > > drivers trying to perform CPU power management at the same time? You > > > > should probably remove or disable to frkit powernow driver. I think you > > > > might as well remove it as I believe it only supports single processor > > > > systems and you have two processors. > > > > > > I got the similar error on my side, > > > > > > # dmesg | grep PSS > > > Jul 26 02:31:12 aubrey-nevada cpudrv: [ID 684953 kern.notice] NOTICE: > > > cpu_acpi: _PSS package not found. > > > Jul 26 02:31:12 aubrey-nevada cpudrv: [ID 616227 kern.warning] > > > WARNING: cpu_acpi: error parsing _PSS for CPU instance 1 > > > Jul 26 02:31:19 aubrey-nevada cpudrv: [ID 684953 kern.notice] NOTICE: > > > cpu_acpi: _PSS package not found. > > > Jul 26 02:31:19 aubrey-nevada cpudrv: [ID 616227 kern.warning] > > > WARNING: cpu_acpi: error parsing _PSS for CPU instance 0 > > > Jul 26 02:31:19 aubrey-nevada cpudrv: [ID 684953 kern.notice] NOTICE: > > > cpu_acpi: _PSS package not found. > > > Jul 26 02:31:19 aubrey-nevada cpudrv: [ID 616227 kern.warning] > > > WARNING: cpu_acpi: error parsing _PSS for CPU instance 1 > > > Jul 26 02:31:25 aubrey-nevada cpudrv: [ID 684953 kern.notice] NOTICE: > > > cpu_acpi: _PSS package not found. > > > Jul 26 02:31:25 aubrey-nevada cpudrv: [ID 616227 kern.warning] > > > WARNING: cpu_acpi: error parsing _PSS for CPU instance 0 > > > Jul 26 02:31:25 aubrey-nevada cpudrv: [ID 684953 kern.notice] NOTICE: > > > cpu_acpi: _PSS package not found. > > > Jul 26 02:31:25 aubrey-nevada cpudrv: [ID 616227 kern.warning] > > > WARNING: cpu_acpi: error parsing _PSS for CPU instance 1 > > > > > > > > > > > Both drivers seemed to be having issues with the ACPI _PSS object. > > > > Usually when I see problems like this it is due to one of two things. > > > > > > > > 1 - Enhanced SpeedStep has not been enabled in the BIOS setup. > > > > > > The problem is my default ACPI Version Features is ACPI V1.0 in the BIOS. > > > When change it to ACPI V3.0, the warning is gone. > > > > Is it possible to change it in in HP gear? or is it ACPI v1.0 by default? > > I don't think so. _PSS object is added in ACPI V3.0B, which is > released on October 10, 2006. From your acpi info, it's not supported. > > >[EMAIL PROTECTED]:~> cat /proc/acpi/info > >version: 20060127 >
Oops, _PSS objects should be added in from ACPI V2.0a. So definitely the ACPI implementation on your machine is V1.0. I assume your BIOS returns valid _PSS objects. > > > > > > > > > > 2 - The BIOS is not returning valid _PSS objects. > > > > > > > > The first is easy to check for. > > > > > > > > The second usually requires dumping the ACPI tables with a utility like > > > > iasl and then inspecting the output to see what the _PSS definitions > > > > look like. Unfortunately, you need to know something about what they are > > > > supposed to look like in order to tell what, if anything, is wrong with > > > > them. > > > > > > > > What kind of system do you have? > > > > > > > > > > The warning probably remains if Matthew's system is a bit old. > > > > > > Well, its around 3 months old but has the latest BIOS update (F.27) from HP. > > You just lose one functionality(Processor Performance State) of power > management, I believe both SLED 10 SP1 and Windows Vista are not > support this feature yet. Anyway, > your system can still run happily. > > -Aubrey > Intel OpenSolaris Team. > _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org