|
Description
|
Originally identified by Intel's Aubrey Li, this issue is now being identified on
other Sun platforms.
We're seeing the now infamous "_PSS not found" messages in the system logs on systems
whose BIOS actually *are* exporting _PSS objects. Example message:
Sep 14 20:31:16 ban3s21d0s0 cpudrv: [ID 805513 kern.info] NOTICE: cpu_acpi: _PSS package not found.
Sep 14 20:31:16 ban3s21d0s0 cpudrv: [ID 978953 kern.warning] WARNING: cpu_acpi: error parsing _PSS for CPU instance 1
The thing that distinguishes this particular bug from other such occurences of the
message is that an iasl dump of the ACPI tables shows that the _PSS objects belong
to a Processor Object for which there is an Alias defined. For example:
Scope (_PR)
{
Processor (P001, 0x01, 0x00000810, 0x06) {}
Alias (P001, CPU1)
Processor (P002, 0x02, 0x00000000, 0x00) {}
Alias (P002, CPU2)
.
.
.
}
.
.
.
Scope (\_PR.P001)
{
Method (_PSS, 0, NotSerialized)
{
If (LEqual (And (CFGD, 0x4000), 0x00))
{
Return (NPSS)
}
Return (SPSS)
}
.
.
.
}
Obviously, a _PSS exists for processor 1, but cpudrv is unable to find it.
|
