User profile for user: yuanshiming
yuanshiming Author
User level: Level 1
59 points

SOLUTION to panic(cpu 0 caller 0xffffff8011a16487): "AppleIntelFramebuffer::setPowerState

It turns out there's a lot of folks that are facing this issue (https://discussions.apple.com/thread/251221769)


A peak of the panic report:


panic(cpu 0 caller 0xffffff8011a16487): "AppleIntelFramebuffer::setPowerState(0xffffff8359b02000 : 0xffffff7f94fafd88, 1 -> 0) timed out after 45989 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296


So the unofficial solution is:  In system preferences -> energy saver -> power adapter -> turn display off after = NEVER.


My mac had the same issue as you can see here https://discussions.apple.com/thread/251221769


This solution has worked so far.

MacBook Pro with Touch Bar

Posted on Mar 31, 2020 11:05 PM

Reply
Question marked as Top-ranking reply
User profile for user: megabiteg
megabiteg
User level: Level 1
8 points

Posted on Sep 9, 2020 11:37 PM

Well I just found the solution for my case:


I noticed that someone mentioned that the driver involved in the panic has to do with graphics and sound via HDMI. I recently got a 4K monitor with sound integrated, and after the 10.15.6 update this problem started for me.


I tried the trick of disabling screen dimming and closing the lid and no dice. But when I disconnect the 4K monitor and let it sleep, now it doesn’t happen. What I believe that’s happening is that, when it attempts to switch audio inputs, while asleep the panic his happening.


im going to try setting the audio input to the screen before sleep and see if the problem happens. I’ll report back.

View in context

Similar questions

35 replies
User profile for user: RaphaeliteGirl
RaphaeliteGirl
User level: Level 1
20 points

Sep 23, 2020 5:47 PM in response to yuanshiming

Catalina 10.15.6 here on my 2018 MBP.


I still have this problem associated with the sleep/wake cycle.


I have a similar crash report:


panic(cpu 0 caller 0xffffff7f9c9333c5): "UPSB(MacBookPro15,1): thunderbolt power on failed 0xffffffff\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-370.141.1/IOPCIBridge.cpp:1398


I've disabled the Thunderbolt Bridge, done a PRAM reset, yet still the problem persists...


The only thing plugged into the Thunderbolt port is occasionally my official Apple charger. It crashes whether that's plugged in or not. 11 times today and counting...


I too paid £3,500 for this Macbook Pro and I'm sick of it, frankly. I've had Macs for over 20 years, and the last few years, they've gone rapidly downhill.


Off-topic slightly, the farcical repair process of having to send it to the Czech Republic where no-one, not even senior UK Apple experts can communicate with the repair team there, is appalling. They routinely wipe all machines even when replacing something as basic as a sticky keyboard. They even wiped my second, brand new, (but also faulty) backup MBP despite Apple UK cancelling its repair (at my request in case they wiped that too) before any work had started - wtff?


I've lost so much data, it's unreal. (Time Machine backups failed repeatedly before you swoop. I had to use the new loaned MBP as backup for my main one, and brilliantly, that too failed... 🥴)

Rest of crash log




Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

SOLUTION to panic(cpu 0 caller 0xffffff8011a16487): "AppleIntelFramebuffer::setPowerState

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up