Public bug reported:
We sometimes see failures like the following:
method FAILED [MEDIUM] AMLLocksAcquired: Test 61, \_WAK left 1
method locks in an acquired state.
method
method ADVICE: Locks left in an acquired state generally
method indicates that the AML code is not releasing a lock. This
method can sometimes occur when a method hits an error condition#
method and exits prematurely without releasing an acquired lock.
method It may be occurring in the method being tested or other
method methods used while evaluating the method.
..but for some reason it seems to happen non-deterministically.
Probably a race somewhere. Needs fixing.
** Affects: fwts (Ubuntu)
Importance: Medium
Assignee: Colin King (colin-king)
Status: In Progress
** Changed in: fwts (Ubuntu)
Status: New => In Progress
** Changed in: fwts (Ubuntu)
Importance: Undecided => Medium
** Changed in: fwts (Ubuntu)
Assignee: (unassigned) => Colin King (colin-king)
** Summary changed:
- fwts: method test repoorts mutex lock failures in a seemingly
non-deterministic way with some firmware
+ fwts: method test reports mutex lock failures in a seemingly
non-deterministic way with some firmware
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017388
Title:
fwts: method test reports mutex lock failures in a seemingly non-
deterministic way with some firmware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1017388/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
