Hey, I've got the same issue. My terminal indicates previous shutdown cause : -11 whenever I've an unexpected and abrupt shutdown. Did you manage to find a way to solve the issue ?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2018 MacBook Pros crashing with "Bridge OS" error
- Thread starter kryptticAZ
- Start date
- Sort by reaction score
Hey, I've got the same issue. My terminal indicates previous shutdown cause : -11 whenever I've an unexpected and abrupt shutdown. Did you manage to find a way to solve the issue ?
Mine will only crash (and even then not all the time) if you wake it from sleep and immediately plug in some USB device (hard drive, scanner, anything except the charger). I usually wake it up and then wait a couple seconds before plugging anything in to avoid that issue.
Interesting! My own issues have been with a Caldigit TS3+ with NO other equipment connected. In this case the TS3 is providing power to the MBP through the special Caldigit cable. I will try with another cable and separate power feed to the MBP and see how that works.
What seems to happens is some issue when the MBP is trying to wake equipment connected via Thunderbolt. The process times out and generates a kernel panic.
The interesting thing is that I have the same problem on my 2016 15" which does not have a T2 chip. But instead of the cryptic BridgeOs error report I just get a kernel panic report.
What seems to happens is some issue when the MBP is trying to wake equipment connected via Thunderbolt. The process times out and generates a kernel panic.
The interesting thing is that I have the same problem on my 2016 15" which does not have a T2 chip. But instead of the cryptic BridgeOs error report I just get a kernel panic report.
Hi Matram, I also have a newly purchased MBP 2018 with a Caldigit TS3+. I am getting daily kernel panics while sleeping, and today got one a few minutes after waking. I have switched off all the Powernap type stuff. Are you using a Thunderbolt T3 to T2 adaptor? best Tommy Banana
I using the T3 cable provided with the TS3+, no adaptor.
Interestingly, with latest beta 5 of 10.15.4, I am no longer able to reproduce the problem on my 15".
I will continue testing on my 15".
I assume we will soon see the official release of 10.15.4, I will then try on my 16".
Interestingly, with latest beta 5 of 10.15.4, I am no longer able to reproduce the problem on my 15".
I will continue testing on my 15".
I assume we will soon see the official release of 10.15.4, I will then try on my 16".
I am attaching CalDigit Ts3+ the same way, but using T3>T2 for a Firewire audio interface. I could upgrade that if it was the problem but it would be a total pain.
Is 10.15.4 stable? Might give it a go...
Is 10.15.4 stable? Might give it a go...
Back in 2018 when I first got my 2018 MBP15, I also got a TS3+ with it. When it was connected to the TS3+, it would crash/reboot every night without fail with the bridgeOS error. Once I removed the TS3+ and connected the power and monitors directly, the issue went away. It's not crashed/rebooted itself with the bridgeOS even one single time. I ended up just returning the TS3+ rather than waste more time futzing with it. Others have sworn up and down that the TS3+ wasn't to blame, since it works fine for them. Maybe I got a defective unit... it's possible... but I just got tired of wasting a lot of time trying to figure out if the problem was elsewhere, when clearly removing it fixed the problem.
I upgraded my 2019 MacBook Pro to 10.15.4 Tuesday afternoon, and yesterday morning after working for awhile, I did the lock screen, and closed the lid - no hibernation or anything. I came back, and it restarted with a crash in Adobe Creative Cloud.
About an hour ago I just left my laptop, and it turns the display off after 15 minutes; no hibernate or other energy options. I came back, and it restarted again! Second crash with a restart in 2 days, on a laptop that NEVER crashes - not had one in 6 months (I watch for them in the log).
I am guessing this is not app related, as I have crashes in two apps in 2 days. Is this the infamous Bridge crash? Or should I post this thread in the Catalina forum?
CRASH 1:
Process: node [1689]
Path: /Library/Application Support/Adobe/*/CCLibrary.app/Contents/libs/node
Identifier: node
Version: ???
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: node [1689]
User ID: 501
Date/Time: 2020-03-24 16:30:41.185 -0400
OS Version: Mac OS X 10.15.4 (19E266)
Report Version: 12
Bridge OS Version: 4.4 (17P4263)
Anonymous UUID: 3D686A5D-8EFA-445B-B4CF-E8933A98546A
Time Awake Since Boot: 290 seconds
System Integrity Protection: enabled
Crashed Thread: 14 VulcanMsgRecv
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1689]
-----------
CRASH 2:
Process: WindowServer [272]
Path: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Identifier: WindowServer
Version: 600.00 (450.9)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: WindowServer [272]
User ID: 88
Date/Time: 2020-03-26 09:39:49.618 -0400
OS Version: Mac OS X 10.15.4 (19E266)
Report Version: 12
Bridge OS Version: 4.4 (17P4263)
Anonymous UUID: AE4B0726-8112-455B-A328-661A3EF39EC5
Sleep/Wake UUID: 174360AC-11E6-459A-A13C-3A3877FD481E
Time Awake Since Boot: 37000 seconds
Time Since Wake: 2100 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
About an hour ago I just left my laptop, and it turns the display off after 15 minutes; no hibernate or other energy options. I came back, and it restarted again! Second crash with a restart in 2 days, on a laptop that NEVER crashes - not had one in 6 months (I watch for them in the log).
I am guessing this is not app related, as I have crashes in two apps in 2 days. Is this the infamous Bridge crash? Or should I post this thread in the Catalina forum?
CRASH 1:
Process: node [1689]
Path: /Library/Application Support/Adobe/*/CCLibrary.app/Contents/libs/node
Identifier: node
Version: ???
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: node [1689]
User ID: 501
Date/Time: 2020-03-24 16:30:41.185 -0400
OS Version: Mac OS X 10.15.4 (19E266)
Report Version: 12
Bridge OS Version: 4.4 (17P4263)
Anonymous UUID: 3D686A5D-8EFA-445B-B4CF-E8933A98546A
Time Awake Since Boot: 290 seconds
System Integrity Protection: enabled
Crashed Thread: 14 VulcanMsgRecv
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1689]
-----------
CRASH 2:
Process: WindowServer [272]
Path: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Identifier: WindowServer
Version: 600.00 (450.9)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: WindowServer [272]
User ID: 88
Date/Time: 2020-03-26 09:39:49.618 -0400
OS Version: Mac OS X 10.15.4 (19E266)
Report Version: 12
Bridge OS Version: 4.4 (17P4263)
Anonymous UUID: AE4B0726-8112-455B-A328-661A3EF39EC5
Sleep/Wake UUID: 174360AC-11E6-459A-A13C-3A3877FD481E
Time Awake Since Boot: 37000 seconds
Time Since Wake: 2100 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
This looks like it's Adobe's issue. There was just a Creative Cloud Desktop app update earlier this week.
I thought it might be too @chrfr, so actually yesterday I uninstalled Adobe CC because I wasn't using it - only Acrobat. So I was surprised when I got the second crash, Windows Server? Is that maybe Parallels, as I use it? And if so, isn't it odd that it's two apps? But if this isn't the Bridge crash, should I post this in the Catalina forum? Thanks!
It's not a kernel panic, so this isn't the correct thread.
Windowserver is the process that the entire user interface runs in.
Agreed. I don't think this error is a kernel panic. You might turn off "automatic graphics switching" and see if that helps, though.
I had had a crash with 10.15.4 and the latest 17P4263 firmware:
{"caused_by":"macos","macos_version":"Mac OS X 10.15.4 (19E266)","os_version":"Bridge OS 4.4 (17P4263)","macos_system_state":"running","incident_id":"E3D44722-F5F2-4D64-90FD-0310A6B6EC72","timestamp":"2020-03-31 23:25:15.00 +0000","bug_type":"210"}
{
"build" : "Bridge OS 4.4 (17P4263)",
"product" : "iBridge2,14",
"kernel" : "Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2\/RELEASE_ARM64_T8010",
"incident" : "E3D44722-F5F2-4D64-90FD-0310A6B6EC72",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2020-03-31 23:25:15.37 +0000",
"panicString" : "panic(cpu 1 caller 0xfffffff00b0537b4): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 17P4263\nmacOS version: 19E266\nKernel version: Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2\/RELEASE_ARM64_T8010\nKernel UUID: 3695E9D9-323E-350E-9A6E-65819BE397D7\niBoot version: iBoot-5540.105.2\nsecure boot?: YES\nx86 EFI Boot State: 0x16\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x1\nx86 Previous Power Transitions: 0x70604000100\nPCIeUp link state: 0x89473611\nPaniclog version: 13\nKernel slide: 0x000000000301c000\nKernel text base: 0xfffffff00a020000\nmach_absolute_time: 0x6fedf444046\nEpoch Time: sec usec\n Boot : 0x5e7eed35 0x0008b89f\n Sleep : 0x5e80c77e 0x000813d9\n Wake : 0x5e80c79e 0x000c12cf\n Calendar: 0x5e83d137 0x000ad1fa\n\nPanicked task 0xffffffe0000e4200: 3291 pages, 220 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0004b0fd8, backtrace: 0xffffffe0159e34b0, tid: 332\n\t\t lr: 0xfffffff00a8e4764 fp: 0xffffffe0159e34f0\n\t\t lr: 0xfffffff00a8e45c0 fp: 0xffffffe0159e3560\n\t\t lr: 0xfffffff00a9fee7c fp: 0xffffffe0159e3610\n\t\t lr: 0xfffffff00aead62c fp: 0xffffffe0159e3620\n\t\t lr: 0xfffffff00a8e3f28 fp: 0xffffffe0159e3990\n\t\t lr: 0xfffffff00a8e4280 fp: 0xffffffe0159e39e0\n\t\t lr: 0xfffffff00b71a934 fp: 0xffffffe0159e3a00\n\t\t lr: 0xfffffff00b0537b4 fp: 0xffffffe0159e3a30\n\t\t lr: 0xfffffff00b044be4 fp: 0xffffffe0159e3aa0\n\t\t lr: 0xfffffff00b046b0c fp: 0xffffffe0159e3b50\n\t\t lr: 0xfffffff00b04431c fp: 0xffffffe0159e3be0\n\t\t lr: 0xfffffff00b00b780 fp: 0xffffffe0159e3c10\n\t\t lr: 0xfffffff00ae1aabc fp: 0xffffffe0159e3c50\n\t\t lr: 0xfffffff00ae1a340 fp: 0xffffffe0159e3c90\n\t\t lr: 0xfffffff00aeb8514 fp: 0x0000000000000000\n\n",
"panicFlags" : "0x102",
"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 113840 **\n",
"macOSPanicFlags" : "0x0",
"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",
So not fixed yet. Maybe I'll need to take my machine in. Brand new 16" MBP
{"caused_by":"macos","macos_version":"Mac OS X 10.15.4 (19E266)","os_version":"Bridge OS 4.4 (17P4263)","macos_system_state":"running","incident_id":"E3D44722-F5F2-4D64-90FD-0310A6B6EC72","timestamp":"2020-03-31 23:25:15.00 +0000","bug_type":"210"}
{
"build" : "Bridge OS 4.4 (17P4263)",
"product" : "iBridge2,14",
"kernel" : "Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2\/RELEASE_ARM64_T8010",
"incident" : "E3D44722-F5F2-4D64-90FD-0310A6B6EC72",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2020-03-31 23:25:15.37 +0000",
"panicString" : "panic(cpu 1 caller 0xfffffff00b0537b4): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 17P4263\nmacOS version: 19E266\nKernel version: Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2\/RELEASE_ARM64_T8010\nKernel UUID: 3695E9D9-323E-350E-9A6E-65819BE397D7\niBoot version: iBoot-5540.105.2\nsecure boot?: YES\nx86 EFI Boot State: 0x16\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x1\nx86 Previous Power Transitions: 0x70604000100\nPCIeUp link state: 0x89473611\nPaniclog version: 13\nKernel slide: 0x000000000301c000\nKernel text base: 0xfffffff00a020000\nmach_absolute_time: 0x6fedf444046\nEpoch Time: sec usec\n Boot : 0x5e7eed35 0x0008b89f\n Sleep : 0x5e80c77e 0x000813d9\n Wake : 0x5e80c79e 0x000c12cf\n Calendar: 0x5e83d137 0x000ad1fa\n\nPanicked task 0xffffffe0000e4200: 3291 pages, 220 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0004b0fd8, backtrace: 0xffffffe0159e34b0, tid: 332\n\t\t lr: 0xfffffff00a8e4764 fp: 0xffffffe0159e34f0\n\t\t lr: 0xfffffff00a8e45c0 fp: 0xffffffe0159e3560\n\t\t lr: 0xfffffff00a9fee7c fp: 0xffffffe0159e3610\n\t\t lr: 0xfffffff00aead62c fp: 0xffffffe0159e3620\n\t\t lr: 0xfffffff00a8e3f28 fp: 0xffffffe0159e3990\n\t\t lr: 0xfffffff00a8e4280 fp: 0xffffffe0159e39e0\n\t\t lr: 0xfffffff00b71a934 fp: 0xffffffe0159e3a00\n\t\t lr: 0xfffffff00b0537b4 fp: 0xffffffe0159e3a30\n\t\t lr: 0xfffffff00b044be4 fp: 0xffffffe0159e3aa0\n\t\t lr: 0xfffffff00b046b0c fp: 0xffffffe0159e3b50\n\t\t lr: 0xfffffff00b04431c fp: 0xffffffe0159e3be0\n\t\t lr: 0xfffffff00b00b780 fp: 0xffffffe0159e3c10\n\t\t lr: 0xfffffff00ae1aabc fp: 0xffffffe0159e3c50\n\t\t lr: 0xfffffff00ae1a340 fp: 0xffffffe0159e3c90\n\t\t lr: 0xfffffff00aeb8514 fp: 0x0000000000000000\n\n",
"panicFlags" : "0x102",
"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 113840 **\n",
"macOSPanicFlags" : "0x0",
"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",
So not fixed yet. Maybe I'll need to take my machine in. Brand new 16" MBP
Just chiming in here with my story. I've had BAD MAGIC crashes since the day I got my 2019 16" MBP in Nov. 2019. I quickly learned not to plug in my external SSD within a few seconds of waking up the Mac to avoid the Bad Magic kernel panic ("BMkp"). Besides that, the only time I experience the BMkp is when shutting down, where it will hang for several minutes before briefly revving the fans to maximum and then restarting. I don't use the webcam so I can't comment on any issues there.
I tried all the usual tips like resetting SMC and NVRAM, and running Apple Diagnostics, and it made no difference. I called Apple Support back in December about this when it became clear that I had a recurring problem, and the support guy had never heard of this "bad magic" stuff before. I made no effort to continue talking to Support again after that. My Googling of the issue told me that Apple has no idea what is going on at the lower levels such as the Apple Store and basic support. If their real engineers are working on fixing this then it's being kept as mum as possible in the meantime.
I am slowly learning that the key to avoiding the BMkp on shutdown is either (a) unplugging USB-C accessories first (I typically only have two things plugged in: the power cable and an older keyboard and mouse running through a USB-A-to-C converter), and/or (b) shutting down every night rather than my traditional practice of not shutting down more than once a week, and keeping my Mac asleep at night. This was working well, and then I left my Mac on for about 3 days (sleeping it at night and waking it up each morning), only to experience the BMkp when I finally tried to shut it down. Two days uptime seems to be the limit, but that's just a rule of thumb. I haven't yet determined if there's a specific program I'm running or accessory I'm using that makes this more likely to happen. It mainly seems to be the time factor that determines whether I will crash on shutdown.
FYI, my T2 chip is the j152fap according to install.log. In my skimming of this thread I haven't seen anyone with that T2 model before, so I thought I would mention it.
If I may opine for a minute, I'm extremely doubtful that any of you guys are going to benefit from taking your Mac in for service, as it seems that Apple is completely ignorant of the problem at lower levels of the organization and completely in denial of the problem at the upper levels, and the "Geniuses" are simply making random attempts to solve the problem by replacing logic boards, etc. If you like depriving yourself of your Mac for days only to get back another malfunctioning system, feel free, but I'm not doing anything until Apple comes clean about BadMagicGate and promises to fix the actual problem (whatever it may be) at their cost.
I tried all the usual tips like resetting SMC and NVRAM, and running Apple Diagnostics, and it made no difference. I called Apple Support back in December about this when it became clear that I had a recurring problem, and the support guy had never heard of this "bad magic" stuff before. I made no effort to continue talking to Support again after that. My Googling of the issue told me that Apple has no idea what is going on at the lower levels such as the Apple Store and basic support. If their real engineers are working on fixing this then it's being kept as mum as possible in the meantime.
I am slowly learning that the key to avoiding the BMkp on shutdown is either (a) unplugging USB-C accessories first (I typically only have two things plugged in: the power cable and an older keyboard and mouse running through a USB-A-to-C converter), and/or (b) shutting down every night rather than my traditional practice of not shutting down more than once a week, and keeping my Mac asleep at night. This was working well, and then I left my Mac on for about 3 days (sleeping it at night and waking it up each morning), only to experience the BMkp when I finally tried to shut it down. Two days uptime seems to be the limit, but that's just a rule of thumb. I haven't yet determined if there's a specific program I'm running or accessory I'm using that makes this more likely to happen. It mainly seems to be the time factor that determines whether I will crash on shutdown.
FYI, my T2 chip is the j152fap according to install.log. In my skimming of this thread I haven't seen anyone with that T2 model before, so I thought I would mention it.
If I may opine for a minute, I'm extremely doubtful that any of you guys are going to benefit from taking your Mac in for service, as it seems that Apple is completely ignorant of the problem at lower levels of the organization and completely in denial of the problem at the upper levels, and the "Geniuses" are simply making random attempts to solve the problem by replacing logic boards, etc. If you like depriving yourself of your Mac for days only to get back another malfunctioning system, feel free, but I'm not doing anything until Apple comes clean about BadMagicGate and promises to fix the actual problem (whatever it may be) at their cost.
I reached out to CalDigit support about this and they replied they are aware of an issue in Catalina that relates to external docks and sleeping. They said that the issue has also been acknowledge by Apple and that they are working on a fix. Due to the circumstances relating to the spread of Corona virus, they expect the fix to be available in about 2 months.
I've removed my TS3+ dock from my setup to test it out. However, that seemed to triggere at least 2 more kernel panics in 2 days (normally, I would only see it like once every 1-2 weeks). I still had my LG UltraFine 5K attached. From today I'm running with out this too to see if this stabilises the system. If it is an issue relating to the sleep state and external peripherals it's worth checking out for me at least
2018 MacMini (but only bought at the beginning of March), i7, 32GB, 1TB.
I really only get this when it's sleeping. Wake it up the next day and it's at the login-screen again.
It also seems to happen fairly early after falling asleep.
I think it has never crashed while I was doing actual work.
My only peripheral on USB-C is the display (and that probably includes some sort of hub, because I can get USB on the display). It's an EIZO EV3285.
I am on Mojave, simply because I like the dashboard-widgets and I'd lose those on upgrade to Catalina (which doesn't have a great record on stability on its own, either) and none of the headline-features of Catalina really appeal to me.
I don't have power-nap enabled.
Given the price-point of this thing, it is a bit annoying.
I really only get this when it's sleeping. Wake it up the next day and it's at the login-screen again.
It also seems to happen fairly early after falling asleep.
Code:
{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.6 (18G4032)","os_version":"Bridge OS 4.4 (17P4263)","macos_system_state":"sleep","incident_id":"3143A57D-779C-413D-8AAA-7F435649D3F1","timestamp":"2020-04-10 22:10:16.00 +0000","bug_type":"210"}
Code:
9A6167E6-17EA-412A-AC50-785346496D64 localbridge iBridge2,5 J174AP 4.4 (17P4263/17.16.14263.0.0,0) -I think it has never crashed while I was doing actual work.
My only peripheral on USB-C is the display (and that probably includes some sort of hub, because I can get USB on the display). It's an EIZO EV3285.
I am on Mojave, simply because I like the dashboard-widgets and I'd lose those on upgrade to Catalina (which doesn't have a great record on stability on its own, either) and none of the headline-features of Catalina really appeal to me.
I don't have power-nap enabled.
Given the price-point of this thing, it is a bit annoying.
Last edited:
Hello, I have 2018 mini i5, 32GB RAM, bought in 2018, I am still on Mojave just like You and after last security update to Mojave I have identical error message after wake from sleep
Hi,
can anyone read this log for me?
Catalina 10.15.4
macbook pro 2018 2.6ghz
panic(cpu 0 caller 0xfffffff00f0c24d4): "i2c1::_checkBusStatus SCL is stuck low; last write status 00010108 int shadow 00010100 xfer 00000000 fifo 00000000 for device audio-tas5770L-spkr-woofer-r"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleS5L8940X/AppleS5L8940X-169.0.1/AppleS5L8940XI2C.cpp:351
Debugger message: panic
Memory ID: 0xff
OS version: 17P4263
macOS version: 19E266
Kernel version: Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2/RELEASE_ARM64_T8010
Kernel UUID: 3695E9D9-323E-350E-9A6E-65819BE397D7
iBoot version: iBoot-5540.105.2
secure boot?: YES
x86 EFI Boot State: 0xe
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0xec
x86 Previous Power Transitions: 0x70604000200
PCIeUp link state: 0x94721614
Paniclog version: 13
Kernel slide: 0x0000000006e70000
Kernel text base: 0xfffffff00de74000
mach_absolute_time: 0x9b8ffb52
Epoch Time: sec usec
Boot : 0x5e933b4e 0x000ed480
Sleep : 0x5e933b95 0x00029a86
Wake : 0x5e933cb6 0x0002687c
Calendar: 0x5e933cd8 0x000923dc
Panicked task 0xffffffe0011f4600: 664 pages, 9 threads: pid 40: bridgeaudiod
Panicked thread: 0xffffffe00157b4d0, backtrace: 0xffffffe015ba2920, tid: 1203
lr: 0xfffffff00e738764 fp: 0xffffffe015ba2960
lr: 0xfffffff00e7385c0 fp: 0xffffffe015ba29d0
lr: 0xfffffff00e852e7c fp: 0xffffffe015ba2a80
lr: 0xfffffff00ed0162c fp: 0xffffffe015ba2a90
lr: 0xfffffff00e737f28 fp: 0xffffffe015ba2e00
lr: 0xfffffff00e738280 fp: 0xffffffe015ba2e50
lr: 0xfffffff00f56e8f8 fp: 0xffffffe015ba2e70
lr: 0xfffffff00f0c24d4 fp: 0xffffffe015ba2ef0
lr: 0xfffffff00f0c1d38 fp: 0xffffffe015ba2f80
lr: 0xfffffff00f0c18d4 fp: 0xffffffe015ba2fb0
lr: 0xfffffff00f0c1570 fp: 0xffffffe015ba2ff0
lr: 0xfffffff00ed78d04 fp: 0xffffffe015ba3010
lr: 0xfffffff00ed78b6c fp: 0xffffffe015ba3040
lr: 0xfffffff00ec70ec4 fp: 0xffffffe015ba30b0
lr: 0xfffffff00ed79530 fp: 0xffffffe015ba3110
lr: 0xfffffff00f058898 fp: 0xffffffe015ba3190
lr: 0xfffffff00f058698 fp: 0xffffffe015ba3220
lr: 0xfffffff00f0596e8 fp: 0xffffffe015ba3250
lr: 0xfffffff00f536844 fp: 0xffffffe015ba3280
lr: 0xfffffff00f536998 fp: 0xffffffe015ba3290
lr: 0xfffffff00f06df4c fp: 0xffffffe015ba32c0
lr: 0xfffffff00ec70ec4 fp: 0xffffffe015ba3330
lr: 0xfffffff00f04e158 fp: 0xffffffe015ba33d0
lr: 0xfffffff00f05307c fp: 0xffffffe015ba3480
lr: 0xfffffff00f052d40 fp: 0xffffffe015ba34d0
lr: 0xfffffff00f052a0c fp: 0xffffffe015ba3530
lr: 0xfffffff00ec6e970 fp: 0xffffffe015ba3580
lr: 0xfffffff00f07b6a8 fp: 0xffffffe015ba35e0
lr: 0xfffffff00ec70ec4 fp: 0xffffffe015ba3650
lr: 0xfffffff00f07b450 fp: 0xffffffe015ba36d0
lr: 0xfffffff00ec9f00c fp: 0xffffffe015ba3860
lr: 0xfffffff00e8228d0 fp: 0xffffffe015ba3980
lr: 0xfffffff00e73df24 fp: 0xffffffe015ba39e0
lr: 0xfffffff00e713cf0 fp: 0xffffffe015ba3a60
lr: 0xfffffff00e72bc7c fp: 0xffffffe015ba3b10
lr: 0xfffffff00e849760 fp: 0xffffffe015ba3bd0
lr: 0xfffffff00e852fd4 fp: 0xffffffe015ba3c80
lr: 0xfffffff00ed0162c fp: 0xffffffe015ba3c90
lr: 0x0000000192a27198 fp: 0x0000000000000000
can anyone read this log for me?
Catalina 10.15.4
macbook pro 2018 2.6ghz
panic(cpu 0 caller 0xfffffff00f0c24d4): "i2c1::_checkBusStatus SCL is stuck low; last write status 00010108 int shadow 00010100 xfer 00000000 fifo 00000000 for device audio-tas5770L-spkr-woofer-r"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleS5L8940X/AppleS5L8940X-169.0.1/AppleS5L8940XI2C.cpp:351
Debugger message: panic
Memory ID: 0xff
OS version: 17P4263
macOS version: 19E266
Kernel version: Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2/RELEASE_ARM64_T8010
Kernel UUID: 3695E9D9-323E-350E-9A6E-65819BE397D7
iBoot version: iBoot-5540.105.2
secure boot?: YES
x86 EFI Boot State: 0xe
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0xec
x86 Previous Power Transitions: 0x70604000200
PCIeUp link state: 0x94721614
Paniclog version: 13
Kernel slide: 0x0000000006e70000
Kernel text base: 0xfffffff00de74000
mach_absolute_time: 0x9b8ffb52
Epoch Time: sec usec
Boot : 0x5e933b4e 0x000ed480
Sleep : 0x5e933b95 0x00029a86
Wake : 0x5e933cb6 0x0002687c
Calendar: 0x5e933cd8 0x000923dc
Panicked task 0xffffffe0011f4600: 664 pages, 9 threads: pid 40: bridgeaudiod
Panicked thread: 0xffffffe00157b4d0, backtrace: 0xffffffe015ba2920, tid: 1203
lr: 0xfffffff00e738764 fp: 0xffffffe015ba2960
lr: 0xfffffff00e7385c0 fp: 0xffffffe015ba29d0
lr: 0xfffffff00e852e7c fp: 0xffffffe015ba2a80
lr: 0xfffffff00ed0162c fp: 0xffffffe015ba2a90
lr: 0xfffffff00e737f28 fp: 0xffffffe015ba2e00
lr: 0xfffffff00e738280 fp: 0xffffffe015ba2e50
lr: 0xfffffff00f56e8f8 fp: 0xffffffe015ba2e70
lr: 0xfffffff00f0c24d4 fp: 0xffffffe015ba2ef0
lr: 0xfffffff00f0c1d38 fp: 0xffffffe015ba2f80
lr: 0xfffffff00f0c18d4 fp: 0xffffffe015ba2fb0
lr: 0xfffffff00f0c1570 fp: 0xffffffe015ba2ff0
lr: 0xfffffff00ed78d04 fp: 0xffffffe015ba3010
lr: 0xfffffff00ed78b6c fp: 0xffffffe015ba3040
lr: 0xfffffff00ec70ec4 fp: 0xffffffe015ba30b0
lr: 0xfffffff00ed79530 fp: 0xffffffe015ba3110
lr: 0xfffffff00f058898 fp: 0xffffffe015ba3190
lr: 0xfffffff00f058698 fp: 0xffffffe015ba3220
lr: 0xfffffff00f0596e8 fp: 0xffffffe015ba3250
lr: 0xfffffff00f536844 fp: 0xffffffe015ba3280
lr: 0xfffffff00f536998 fp: 0xffffffe015ba3290
lr: 0xfffffff00f06df4c fp: 0xffffffe015ba32c0
lr: 0xfffffff00ec70ec4 fp: 0xffffffe015ba3330
lr: 0xfffffff00f04e158 fp: 0xffffffe015ba33d0
lr: 0xfffffff00f05307c fp: 0xffffffe015ba3480
lr: 0xfffffff00f052d40 fp: 0xffffffe015ba34d0
lr: 0xfffffff00f052a0c fp: 0xffffffe015ba3530
lr: 0xfffffff00ec6e970 fp: 0xffffffe015ba3580
lr: 0xfffffff00f07b6a8 fp: 0xffffffe015ba35e0
lr: 0xfffffff00ec70ec4 fp: 0xffffffe015ba3650
lr: 0xfffffff00f07b450 fp: 0xffffffe015ba36d0
lr: 0xfffffff00ec9f00c fp: 0xffffffe015ba3860
lr: 0xfffffff00e8228d0 fp: 0xffffffe015ba3980
lr: 0xfffffff00e73df24 fp: 0xffffffe015ba39e0
lr: 0xfffffff00e713cf0 fp: 0xffffffe015ba3a60
lr: 0xfffffff00e72bc7c fp: 0xffffffe015ba3b10
lr: 0xfffffff00e849760 fp: 0xffffffe015ba3bd0
lr: 0xfffffff00e852fd4 fp: 0xffffffe015ba3c80
lr: 0xfffffff00ed0162c fp: 0xffffffe015ba3c90
lr: 0x0000000192a27198 fp: 0x0000000000000000
Last edited:
If you're really worried about corruption, the only way to to be sure is store all your data on a FreeNAS (or general ZFS storage) with mirroring or RAID Z2 and use SMB to access it.
My data is not valuable enough to justify that expense, especially if you go and make it All-Flash (because if you're really serious, you have to buy enterprise-level SSDs....)
So, we live with the limitations of macOS and its associated hardware, because we really like macOS and hope that if the next bugfix doesn't finally fix it (promise!), the next version surely will (really!).
;-)
My data is not valuable enough to justify that expense, especially if you go and make it All-Flash (because if you're really serious, you have to buy enterprise-level SSDs....)
So, we live with the limitations of macOS and its associated hardware, because we really like macOS and hope that if the next bugfix doesn't finally fix it (promise!), the next version surely will (really!).
;-)