Public bug reported:
Fwts method test could put a little more context into each method/object
being tested when it hits a failure case. For example, at the moment, if
_OFF fails we get a terse error message:
"FAILED [MEDIUM]: Test 78, \_SB_.PCI0.PEG0.PEGP._OFF returned values,
but was method expected to return nothing."
We could have a little more advice on this, e.g.:
"This power resource control method puts the power resource into the OFF
state. Section 7.1.2 of version 4.0 of the ACPI specification states it
should return NO values, but in fact \_SB_.PCI0.PEG0.PEGP._OFF does
return a value. This is non-compliant code."
and perhaps a better explanation of the risk of the fault:
"Since this kernel is not expecting any return values then this bug is a
relatively low risk of causing a failure, however it is buggy AML and if
possible should be fixed."
** Affects: fwts (Ubuntu)
Importance: Wishlist
Status: New
** Changed in: fwts (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/859568
Title:
fwts: method test could give references to ACPI specifcation when it
detects non-compliant AML
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/859568/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
