fwts: method test reports mutex lock failures in a seemingly non-deterministic way with some firmware
Bug #1017388 reported by
Colin Ian King
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fwts (Ubuntu) |
Fix Released
|
Medium
|
Colin Ian King | ||
Precise |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
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-determinist
Changed in fwts (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Colin King (colin-king) |
summary: |
- fwts: method test repoorts mutex lock failures in a seemingly non- + fwts: method test reports mutex lock failures in a seemingly non- deterministic way with some firmware |
To post a comment you must log in.
Bug occurs because of non-serialized control methods incrementing and decrementing the semaphore counts and not being protected by a mutex. Patch sent to the mailing list.