Re: Laptop ACPI poweroff failed after main-c255826 -> main-c255850

On 2021-01-13 16:03, David Wolfskill wrote:
> On Tue, Jan 12, 2021 at 07:37:28AM -0800, David Wolfskill wrote:
>> On Tue, Jan 12, 2021 at 05:31:30PM +0200, Andriy Gapon wrote:
>>> On 2021-01-11 14:55, David Wolfskill wrote:
>>>> pci3: unknown notify 0x2
>>>> ACPI Error: AE_ERROR, Thread 100002 could not acquire Mutex [ACPI_MTX_Caches] (0c4) (20201113/utmutex-434)
>>>
>>> Looks like that was some sort of a race or otherwise transient condition
>>> that lead to the _PTS (prepare-to-sleep) failure.
>>>
>>>> ACPI Error: Aborting method \_PTS due to previous error (AE_NO_MEMORY) (20201113/psparse-689)
>>>> acpi0: AcpiEnterSleepStatePrep failed - AE_NO_MEMORY
>>> ....
>>
>> That's certainly plausible -- as I noted a bit earlier today, there was
>> no recurrence  after this morning's main-c255850-g16079c7233be ->
>> main-c255894-g8b1839548750 update.
>>
>> Should I encounter a recurrence, I will plan to get another screenshot,
>> then bring the machine back up and re-try the poweroff (and then report
>> my findings).
>> ....
> 
> I had a recurrence this morninig, after the update from:
> 
> FreeBSD g1-55.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT #120 main-c255894-g8b1839548750-dirty: Tue Jan 12 05:23:50 PST 2021     root_at_g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY  amd64 1300134 1300134
> 
> to:
> 
> FreeBSD g1-55.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT #121 main-c255921-gec2700e01532-dirty: Wed Jan 13 05:06:22 PST 2021     root_at_g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY  amd64 1300135 1300135
> 
> 
> New swcreenshot is in https://www.catwhisker.org/~david/FreeBSD/head/c255921;
> the previous one is in https://www.catwhisker.org/~david/FreeBSD/head/c255850.
> 
> They look quite similar to me.
> 
> After grabbing the screenshot, I rebooted again, but the poweroff
> just worked normally on re-try.
> 
> I believe that this is evidence in favor of a "race condition" diagnosis.
> (In precisely what, I don't know,)

I haven't followed source changes too closely as of recent.
It might be a good idea to check for recent imports of ACPICA updates.


-- 
Andriy Gapon