Kernel Panic every time I close computer

Apple just released Big Sur 11.6.5 and now all the problems I had before seem to be gone on my 2020 Intel MacBook Air. If you haven't updated it's definitely worth a try. Hopefully it will solve all of our problems.

Maybe they actually listened to us? ; )

I have this problem—even if I never launch Music (and my user doesn't have a "Login Item" for it either, but there might be something started by `launchd`, haven't checked), so I'm not sure, as others have observed, that's it related to Music.

I usually plug my Mac into an external monitor using a USB-C to HDMI cable. It appears (but this is a very empirical observation) that the reboot on sleep is less likely to happen when I don't let the Mac go to sleep while connected to an external monitor.

And Big Sur 11.6.5 didn't help for you? It certainly did for me. No problem at all so far, no matter which applications I have started. According to an article in Tidbits the update ”address multiple AppleScript- and kernel-privilege-related issues”.

https://tidbits.com/watchlist/macos-big-sur-11-654-and-security-update-2022-003-catalina/

I haven't tried 11.6.5 yet. I'll give it a try soon, and report back. TbC, the details of the kernel panic I am receiving are as follows (edited to not exceed 5,000 character limit):

panic(cpu 0 caller 0xffffff801486041a): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.driver.AppleIntelICLLPGraphicsFramebuffer. Thread 0x363a1.
Backtracing specified thread

[...]

Process name corresponding to current thread: kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20G417

Kernel version:
Darwin Kernel Version 20.6.0: Wed Jan 12 22:22:42 PST 2022; root:xnu-7195.141.19~2/RELEASE_X86_64
Kernel UUID: AC246285-86E1-3150-8730-749944ED0D5B
KernelCache slide: 0x0000000013e00000
KernelCache base:  0xffffff8014000000
Kernel slide:      0x0000000013e10000
Kernel text base:  0xffffff8014010000
__HIB  text base: 0xffffff8013f00000
System model name: MacBookPro16,2 (Mac-5F9802EFE386AA28)
System shutdown begun: NO
Hibernation exit count: 0

System uptime in nanoseconds: 15702860105583
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00000e481b660b9f
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x0000000794c02673 0x0000000000000000
last started kext at 244868054415: >AudioAUUC	1.70 (addr 0xffffff7faec2c000, size 12288)
loaded kexts:

[...]

Well, no reason to dig deeper into that, as 11.6.5 – suggested even before your first post – most likely will solve your problem. The error message looks very familiar to me, and I haven't seen it after updating.

I agree; if it's a hardware issue then it's affected a ton of their stock which also isn't great...I myself have experienced this on two different macbooks. Also just FYI I'm having this issue consistently on Monterey so upgrading is unlikely to help.

Solved (for me).

I have an LG UltraFine 5K connected to my crashing MacBook Pro (15", 2017) via the LG-provided cable. Kernel panics on sleep transition for about 9 months. Exact message varied by MacOS version but it was always fingering com.apple.iokit.IOGraphicsFamily.

Suspected a cable issue for a while and ended up buying the excellent 70 cm Anker Thunderbolt 4 cable. No panics in over 2 weeks and as an added bonus, the MacBook is back to waking up *immediately*.

Here's my log:

Post the panic log here in the Additional Text Area (document icon).

Useless. I reported this problem many times, no solution. Apple is cankered.

Sorry mate, no clue how to read panic itself :(

If an upgrade and a rollback both resolve the problem, then I would assume it was something in the update. If the problem still appears after upgrading, I’d assume it is hardware.

It's not a small bug that a mac crashes every time it sleeps and should have never happened.

[Edited by Moderator]

Same here! It happens with Apple Music all the time. If I don't open the app it's fine.