Bug 202551 - ACPI, Exception, AE_ERROR, Could not acquire mutex
Summary: ACPI, Exception, AE_ERROR, Could not acquire mutex
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: 10.1-RELEASE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-acpi mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-21 17:22 UTC by Kris
Modified: 2016-10-24 21:17 UTC (History)
3 users (show)

See Also:


Attachments
Screen when problem is reported (408.13 KB, image/jpeg)
2015-08-21 17:22 UTC, Kris
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kris 2015-08-21 17:22:00 UTC
Created attachment 160184 [details]
Screen when problem is reported

User performs system shutdown (power off) - (irrespectively - through desktop manager or console), everything is fine until computer is supposed to turn off. Then it takes couple of seconds and the error is reported.  Unfortunately error message does not survive reboot so it is shown in attached picture only, taken from screen.

Not deterministic problem, with following traits:
- appears randomly but more than once every 10 shutdown at average 
- does not seem to be related to system up time. It was observed after few minutes of system uptime as well as after days of uptime
- does not seem to be related to any particular activities / tasks system had been performing during uptime

Misleading information is that system was going to reboot. That is not the case - system was going down for halt and turn off.

When it occurs computer remains in that state, does not turn off, CPU utilization must be high (fan is spinning like a crazy). Any key stroke would initiate system reboot.

Please let me know what (and how) further symptoms can be collected

Regards
Kris
Comment 1 Aleksander Alekseev 2016-08-16 09:58:15 UTC
Could be related to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
Comment 2 jakub_lach 2016-10-24 21:17:55 UTC
(In reply to Kris from comment #0)

bug #213759 is a duplicate I think. Very similar symptoms, I have a photo too, but could somehow retrieve the massage from log.