https://bugzilla.kernel.org/show_bug.cgi?id=215733
Oscar Priego (oscar.prie...@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |oscar.prie...@gmail.com
--- Comment #8 from Oscar Priego (oscar.prie...@gmail.com) ---
this is straight firmware issue, the vendor is not being able to be resolved
from ACPI, and when it tries to release the mutex, the thread is not identified
as owner, even when the device is the same (get's duplicated in ACPI, god knows
why), so the system tries to have 2 different instances of the same device
while there were some operations running in the background in one of those,
getting a lost connection in the middle of it, and hanging that AML code
execution, then the newer instance (thread) of the device in the acpi tries to
release the mutex but is not able to, as it is not the owner, something is
hiccuping the device while starting over, and leaving behind some unfinished
operations, the device gets referenced twice and not able to perform operations
in that AML code.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
