#
✕ nick:noopwafel
#asahi-re · 2026-03-22 10:15
noopwafeleither way this solves (in practice) my problem so thankyou <3
#asahi-re · 2026-03-22 10:13
noopwafelthat is with a tracer enabled, so probably valid for it to complain, but that is not the usual failure, and based on the log maybe I can workaround that by disabling idle somehow..
#asahi-re · 2026-03-22 10:11
noopwafeltried a couple more times and got a Lock failure in _cpuIdle : https://noopwafel.net/asahi/m3-pmgr-log-panic.txt
#asahi-re · 2026-03-22 10:06
noopwafelthat .. actually boots fine :) race conditions \o/ https://noopwafel.net/asahi/m3-pmgr-log-good.txt if it's interesting/useful despite this
#asahi-re · 2026-03-22 09:36
noopwafel"ApplePMGR: void ApplePMGR::_syncDeviceStatusChange(DeviceStatusChangeData *, UInt32):11702 " "_syncDeviceStatusChange takes too long execTime 45418 us threshold 30000 us PsLevelChangeTime 45406 us turningOn 1 threadSlept 0" @ApplePMGR.cpp:11702
#asahi-re · 2026-03-22 09:36
noopwafel[cpu0] #### MacOS paniced
#asahi-re · 2026-03-22 09:36
noopwafelon the M1 that is perfect but on the M3 it is not enough..
#asahi-re · 2026-03-22 09:24
noopwafeldoes anyone know if there's any kind of disable/hack for the ApplePMGR timing asserts? from irc logs, marcan mentioned pmgr-disable-energy-panic for the energy panics