Computer restarts with panic, busy timeout, IOBlockStorageDriver

Every couple of days my MBP (M1 Pro) restarts - I see for a split second a pink screen and then it reboots. Afterwards I see following error:


panic(cpu 1 caller 0xfffffe0016d8dc24): busy timeout[0], (60s): 'IOBlockStorageDriver' (1,1) @IOService.cpp:5770
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 23C71
Kernel version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:18 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6000
Fileset Kernelcache UUID: 89516519121B13EC9D63007F55C1F1FD
Kernel UUID: 3DE22D7D-A5F5-3B17-84BD-A58164C8B09B
Boot session UUID: EAE282C5-A03C-4C16-8D94-13667E3C3E5A
iBoot version: iBoot-10151.61.4
secure boot?: YES
roots installed: 0
Paniclog version: 14
KernelCache slide: 0x000000000e11c000
KernelCache base:  0xfffffe0015120000
Kernel slide:      0x000000000e124000
Kernel text base:  0xfffffe0015128000
Kernel text exec slide: 0x000000000f650000
Kernel text exec base:  0xfffffe0016654000
mach_absolute_time: 0x7a7ccbdd8f8
Epoch Time:        sec       usec
  Boot    : 0x65b1160c 0x000604d2
  Sleep   : 0x65b76601 0x000ac0f6
  Wake    : 0x65b76603 0x000c0db2
  Calendar: 0x65b768bc 0x00041c14

Zone info:
  Zone map: 0xfffffe10062d4000 - 0xfffffe30062d4000
  . VM    : 0xfffffe10062d4000 - 0xfffffe14d2fa0000
  . RO    : 0xfffffe14d2fa0000 - 0xfffffe166c938000
  . GEN0  : 0xfffffe166c938000 - 0xfffffe1b39604000
  . GEN1  : 0xfffffe1b39604000 - 0xfffffe20062d0000
  . GEN2  : 0xfffffe20062d0000 - 0xfffffe24d2f9c000
  . GEN3  : 0xfffffe24d2f9c000 - 0xfffffe299fc68000
  . DATA  : 0xfffffe299fc68000 - 0xfffffe30062d4000
  Metadata: 0xfffffe4f356a8000 - 0xfffffe4f3d6a8000
  Bitmaps : 0xfffffe4f3d6a8000 - 0xfffffe4f433cc000
  Extra   : 0 - 0

MacBook Pro 16″, macOS 14.2

Posted on Jan 29, 2024 1:10 AM

Reply
Question marked as Top-ranking reply

Posted on Feb 2, 2024 4:49 PM

I am following multiple lines of thought at the same time.


the first Is that your encryption add-ons could be inserting themselves in the system I/O stream at a point that could be causing delays, and that shows itself as that kernel panic.


the second is that your drive could be defective, thus the suggestions that you need to demonstrate failure(s) without add-ons present. Because getting Apple convinced your drive is defective will be difficult. You should run the diagnostic, but it generally only catches GROSS failures.


NB> I do not recommend you submit your Mac for service COLD. Without the ability to demonstrate the failure on demand, the Genius Bar technicans will run their diagnostics, see no failures, and return your Mac to you, "no failures detected". They are NOT trained to read panic reports.


A better route is to contact Apple support, ask for a Specialist who CAN read your Panic reports, and convince them to DIRECT an Apple service provider to change some stuff, likely the mainboard-with-drive. They can read what is already posted, if you alert them to it, but they do NOT take our word for conclusions. They have their own more rigorous processes.


Official Apple Support



the third is that if your drive DOES need to be changed, your files will NOT be returned to you, so 'having all the backups you want' is what you must have before you submit your Mac for drive replacement.

Similar questions

8 replies
Question marked as Top-ranking reply

Feb 2, 2024 4:49 PM in response to _wojtek

I am following multiple lines of thought at the same time.


the first Is that your encryption add-ons could be inserting themselves in the system I/O stream at a point that could be causing delays, and that shows itself as that kernel panic.


the second is that your drive could be defective, thus the suggestions that you need to demonstrate failure(s) without add-ons present. Because getting Apple convinced your drive is defective will be difficult. You should run the diagnostic, but it generally only catches GROSS failures.


NB> I do not recommend you submit your Mac for service COLD. Without the ability to demonstrate the failure on demand, the Genius Bar technicans will run their diagnostics, see no failures, and return your Mac to you, "no failures detected". They are NOT trained to read panic reports.


A better route is to contact Apple support, ask for a Specialist who CAN read your Panic reports, and convince them to DIRECT an Apple service provider to change some stuff, likely the mainboard-with-drive. They can read what is already posted, if you alert them to it, but they do NOT take our word for conclusions. They have their own more rigorous processes.


Official Apple Support



the third is that if your drive DOES need to be changed, your files will NOT be returned to you, so 'having all the backups you want' is what you must have before you submit your Mac for drive replacement.

Feb 2, 2024 1:43 PM in response to Grant Bennet-Alder

Grant Bennet-Alder wrote:

what I take away from your Etrecheck report is that you are doing a lot of work with gpg encryption, and creating and moving files with that encryption. the tools used are less common.

Hmm... I wouldn't say pgp2 is that unusuall... and it's helpful for a lot of stuff. At the very bare minimum signing git commits...



But what MIGHT be happening is that using some of those tools MIGHT be causing delays in your I/O system reads or writes, producing a kernel panic.


I don't see much activity from gpg. Besides, would it be possible to single command/application would block whole disk I/O?



--------
At a minimum, you must be certain you are using the absolute latest versions of all those add-ons, as there have been recent changes to MacOS, some in the File System, that have derailed a LOT of third-party stuff.


Yes, I do have because, apart from MBP and macOS I don't use any of the Apple software as I don't like it (to put it mildly ;-) ). I manage almost all apps that I have installed via homebrew.


And everything is updated daily (if I use the computer that day). gpg is up-to-date:

$ gpg2 --version
gpg (GnuPG/MacGPG2) 2.2.41
libgcrypt 1.8.10
Copyright (C) 2022 g10 Code GmbH



to get Apple to provide a replacement drive, you would need to demonstrate a panic or diagnostic failure WITHOUT all your file system oriented add-ons present, such as in Safe Mode, where none are loaded automatically.

¿what is the date of your most recent backup, and by what method?


I sync most essential data to local seafile (on raspberrypi) and via syncthing to same RPi. Almost everything else is in some remote servers (mails, git repositories) so I don't make a backup of those.

Jan 30, 2024 9:28 AM in response to _wojtek

what I take away from your Etrecheck report is that you are doing a lot of work with gpg encryption, and creating and moving files with that encryption. the tools used are less common.


But what MIGHT be happening is that using some of those tools MIGHT be causing delays in your I/O system reads or writes, producing a kernel panic.


--------

At a minimum, you must be certain you are using the absolute latest versions of all those add-ons, as there have been recent changes to MacOS, some in the File System, that have derailed a LOT of third-party stuff.


to get Apple to provide a replacement drive, you would need to demonstrate a panic or diagnostic failure WITHOUT all your file system oriented add-ons present, such as in Safe Mode, where none are loaded automatically.


¿what is the date of your most recent backup, and by what method?

Jan 29, 2024 6:34 PM in response to _wojtek

It really helps if you post the entire Kernel Panic report here using the "Additional Text" icon which looks like a piece of paper on the forum editing toolbar. Post several different Kernel Panic logs so we can see if there is any pattern to them. Kernel Panic logs are located in "/Library/Logs/DiagnosticReports" with file names beginning with "kernel", or ending in ".panic". If there are none in this folder, then check the "Retired" subfolder.


Also, run EtreCheck and post the report here so we can examine it for clues.



Jan 30, 2024 9:19 AM in response to _wojtek

the beauty of complete Panic logs is that they offer a VERY detailed look at exactly what happened at one instant in time.


the beauty of Etrecheck diagnostics information list is that it is a DIGEST, that allows for Big Picture look at all problems have occurred recently, and is good for spotting Trends.


One other thing Etrecheck shows immediately is fragments of program that have not been removed properly, under the heading "Clean up". And clean those all up you should, because having PART of a package still installed can cause unsolvable issues.



Jan 30, 2024 8:52 AM in response to HWTech

It really helps if you post the entire Kernel Panic report here using the "Additional Text"


HWTech wrote:

It really helps if you post the entire Kernel Panic report here using the "Additional Text" icon which looks like a piece of paper on the forum editing toolbar.

I did attached but I'm not sure why it's not shown



hopefully this time (above)


Post several different Kernel Panic logs so we can see if there is any pattern to them. Kernel Panic logs are located in "/Library/Logs/DiagnosticReports" with file names beginning with "kernel", or ending in ".panic". If there are none in this folder, then check the "Retired" subfolder.

Oddly enough I didn't have any in main folder (only apps, no panics) but there were two in Retired.

Is it safe to share them? They seem quite big and not sure if there aren't any personal information there


$ ls -lah /Library/Logs/DiagnosticReports/Retired/ | grep .panic
-rw-rw-rw-  1 root _analyticsusers 3.1M Jan 24 14:52 panic-full-2024-01-24-145230.0002.panic
-rw-rw-rw-  1 root _analyticsusers 2.4M Jan 29 09:59 panic-full-2024-01-29-095928.0002.panic




Also, run EtreCheck and post the report here so we can examine it for clues.




The report seems kinda vague... Major issues lists "Kernel panics - This system has experienced kernel panics. This could be a sign of hardware failure." without more details...

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.

Computer restarts with panic, busy timeout, IOBlockStorageDriver

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