kernel panic, MBP 16" 2019, 11.2.3

Question

Level 2

218 points

kernel panic, MBP 16" 2019, 11.2.3

This is the 1st kernel panic on this Mac. I plugged in a sleeping MBP to power. Plugged in an external hard drive, via a dongle, to the MBP, while it was still asleep. Opened the Mac to wake it, the drive did not mount, I heard a whooshing sound, maybe was the fan, and screen went blank. Then it rebooted. The whooshing sound, never heard that before. Other than the external drive, I have a keyboard and ethernet plugged int the dongle. I do use an ext. monitor, but it was not plugged in.

Is this anything to worry about? Log below.

panic(cpu 1 caller 0xfffffff027173c44): x86 CPU CATERR detected

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 18P4347

macOS version: 20D91

Kernel version: Darwin Kernel Version 20.3.0: Tue Jan 5 18:50:06 PST 2021; root:xnu-7195.80.35~4/RELEASE_ARM64_T8010

Kernel UUID: C7A021A0-C976-37C8-B2E7-A18B3A7CD973

iBoot version: iBoot-6723.80.19

secure boot?: YES

x86 EFI Boot State: 0xd

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x5

x86 Previous Power Transitions: 0x10001000100

PCIeUp link state: 0x89473614

Paniclog version: 13

Kernel slide: 0x000000001f23c000

Kernel text base: 0xfffffff026240000

mach_absolute_time: 0xf339c5c9d94

Epoch Time: sec usec

Boot : 0x60686f0f 0x00022442

Sleep : 0x6083519b 0x00044f06

Wake : 0x60835244 0x000459b6

Calendar: 0x6083526e 0x000ed7ac

Panicked task 0xffffffe19b9a0308: 3568 pages, 222 threads: pid 0: kernel_task

Panicked thread: 0xffffffe19bb0f760, backtrace: 0xffffffe80226b710, tid: 397

lr: 0xfffffff02696c494 fp: 0xffffffe80226b750

lr: 0xfffffff02696c2f0 fp: 0xffffffe80226b7c0

lr: 0xfffffff026a92d7c fp: 0xffffffe80226b890

lr: 0xfffffff026f815fc fp: 0xffffffe80226b8a0

lr: 0xfffffff02696c024 fp: 0xffffffe80226bc20

lr: 0xfffffff02696c024 fp: 0xffffffe80226bc80

lr: 0xfffffff027962b34 fp: 0xffffffe80226bca0

lr: 0xfffffff027173c44 fp: 0xffffffe80226bcd0

lr: 0xfffffff027162238 fp: 0xffffffe80226bd30

lr: 0xfffffff027164178 fp: 0xffffffe80226bdc0

lr: 0xfffffff0271618e0 fp: 0xffffffe80226be50

lr: 0xfffffff027051960 fp: 0xffffffe80226be80

lr: 0xfffffff026eddbc0 fp: 0xffffffe80226bec0

lr: 0xfffffff026edd440 fp: 0xffffffe80226bf00

lr: 0xfffffff026f8c5a0 fp: 0x0000000000000000

MacBook Pro 16″, macOS 11.2

Posted on Apr 23, 2021 4:19 PM

Reply

Answer 1

Best reply

Grant Bennet-Alder

Level 10

127,939 points

Apr 24, 2021 5:29 PM in response to marc cardwell

What you have sounds fine, I was just hoping NOT to hear, " I keep all my files online" and "I backed them up last year whether I needed to or not".

So if you need to later on, you have a Trusted Backup (or maybe two by different methods), so you could ERASE your drive and re-Install MacOS on a a blank drive, then import your files back over from your backup. That's what passes for an "Erase and Install" these days.

Reply

Answer 2

marc cardwell Author

Level 2

218 points

Apr 23, 2021 5:58 PM in response to Grant Bennet-Alder

When i navigate to that folder, and sort by Date, I don't see a .panic file. I see what's in the screenshot below. I got there by pasting your text into "go to folder", but when i navigate to the same place: Go Menu, hold Option, go to Library, Logs. DiagnosticReports, I see different files! (2nd screenshot) (I hate to confuse any issues, but that really is weird to me)

Reply

Answer 3

marc cardwell Author

Level 2

218 points

Apr 23, 2021 5:16 PM in response to Grant Bennet-Alder

Hi, thanks for helping! I copied all that was in that dialog box. I'm looking in Console app, I thought kernel panic reports would be in there, but don't see anything dated today.

In the left pane, I see Devices (my Mac), Reports (Crash, Log, Diagnostic, Mac Analytics, system log)

I closed that window, with the kernel panic, after submitting a report, is there a way to see all the report somewhere else?

Reply

Answer 4

Apr 23, 2021 5:33 PM in response to marc cardwell

Panic Reports are stored at:

/Library/Logs/DiagnosticReports

If you copy and paste that string into:

Finder > Go menu > Go to Folder

it will take you to where those reports are stored.

They are named with Date&Time and end in .panic

If you find one, please post the entire report here, by using the “additional text” Icon in the reply footer (looks like a paper with writing).

Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.

There are three quick take-aways from any panic report.

1) The panic-reason,

2) the extensions present at the "scene of the crime", and

3) the BSD process in which the problem occurred.

Apple-Silicon panic reports have a somewhat different look, but many of the same parts.

Reply

Answer 5

Apr 24, 2021 5:34 AM in response to marc cardwell

When you type "Library" into the Goto Folder box, it sends you to :

~/Library, a folder inside your userid folder. that's not where you want to be.

Isn't that special -- they changed it all around.

what's in the one that starts with 'panic'?

Reply

Answer 6

marc cardwell Author

Level 2

218 points

Apr 24, 2021 6:54 AM in response to Grant Bennet-Alder

Ugh, I feel foolish. Your method method (copy / paste /Library/Logs/DiagnosticReports) into Go to Folder , DID take me to the system folder. MY way, option-click while in the Go menu took me to my User folder. I should have known that.

That being said, I'm confused by you saying "paste the whole thing" and "don't post more than about 20 lines..." SO, I'll paste the first bit below, from the file called panic-full-2021-04-23-230440.0003.ips . I'm happy to paste the full thing, if needed.

{"caused_by":"macos","macos_version":"Mac OS X 11.2.3 (20D91)","os_version":"Bridge OS 5.2 (18P4347)","macos_system_state":"running","incident_id":"66F527F6-4A14-4A5E-8F13-188EDF02CB5F","timestamp":"2021-04-23 23:04:40.00 +0000","bug_type":"210"}

{

"build" : "Bridge OS 5.2 (18P4347)",

"product" : "iBridge2,14",

"kernel" : "Darwin Kernel Version 20.3.0: Tue Jan 5 18:50:06 PST 2021; root:xnu-7195.80.35~4\/RELEASE_ARM64_T8010",

"incident" : "66F527F6-4A14-4A5E-8F13-188EDF02CB5F",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2021-04-23 23:04:40.12 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff027173c44): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0x6\nOS release type: User\nOS version: 18P4347\nmacOS version: 20D91\nKernel version: Darwin Kernel Version 20.3.0: Tue Jan 5 18:50:06 PST 2021; root:xnu-7195.80.35~4\/RELEASE_ARM64_T8010\nKernel UUID: C7A021A0-C976-37C8-B2E7-A18B3A7CD973\niBoot version: iBoot-6723.80.19\nsecure boot?: YES\nx86 EFI Boot State: 0xd\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x5\nx86 Previous Power Transitions: 0x10001000100\nPCIeUp link state: 0x89473614\nPaniclog version: 13\nKernel slide: 0x000000001f23c000\nKernel text base: 0xfffffff026240000\nmach_absolute_time: 0xf339c5c9d94\nEpoch Time: sec usec\n Boot : 0x60686f0f 0x00022442\n Sleep : 0x6083519b 0x00044f06\n Wake : 0x60835244 0x000459b6\n Calendar: 0x6083526e 0x000ed7ac\n\nPanicked task 0xffffffe19b9a0308: 3568 pages, 222 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe19bb0f760, backtrace: 0xffffffe80226b710, tid: 397\n\t\t lr: 0xfffffff02696c494 fp: 0xffffffe80226b750\n\t\t lr: 0xfffffff02696c2f0 fp: 0xffffffe80226b7c0\n\t\t lr: 0xfffffff026a92d7c fp: 0xffffffe80226b890\n\t\t lr: 0xfffffff026f815fc fp: 0xffffffe80226b8a0\n\t\t lr: 0xfffffff02696c024 fp: 0xffffffe80226bc20\n\t\t lr: 0xfffffff02696c024 fp: 0xffffffe80226bc80\n\t\t lr: 0xfffffff027962b34 fp: 0xffffffe80226bca0\n\t\t lr: 0xfffffff027173c44 fp: 0xffffffe80226bcd0\n\t\t lr: 0xfffffff027162238 fp: 0xffffffe80226bd30\n\t\t lr: 0xfffffff027164178 fp: 0xffffffe80226bdc0\n\t\t lr: 0xfffffff0271618e0 fp: 0xffffffe80226be50\n\t\t lr: 0xfffffff027051960 fp: 0xffffffe80226be80\n\t\t lr: 0xfffffff026eddbc0 fp: 0xffffffe80226bec0\n\t\t lr: 0xfffffff026edd440 fp: 0xffffffe80226bf00\n\t\t lr: 0xfffffff026f8c5a0 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x902",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 39159 (Uncompressed 119408) **\n",

"macOSPanicFlags" : "0x0",

"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",

"memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"pageSize":16384,"memoryPressure":false,"memoryPages":{"active":9598,"throttled":0,"fileBacked":14092,"wired":5756,"purgeable":46,"inactive":4553,"free":5239,"speculative":5292}},

"processByPid" : {

Reply

Answer 7

Apr 24, 2021 10:21 AM in response to marc cardwell

RE: PANIC reports. Please post the entire PANIC report.

Other reports there, things like analytics and hang, that feature debugging symbols for programmers. They consist of pages and pages and pages of symbols and calling sequences and unwinding the stack. THOSE are the ones to limit to 20 lines.

Reply

Answer 8

Apr 24, 2021 12:12 PM in response to marc cardwell

The only "helpful stuff in that report is this:

"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",

This error seems to involve the T2 chip.

recommendations are to re-Install MacOS completely,

then if no joy contact support to have your computer serviced.

.

Reply

Answer 9

marc cardwell Author

Level 2

218 points

Apr 24, 2021 12:54 PM in response to Grant Bennet-Alder

Oy, really, that's the recommendation? I'm not doubting you, but where does one go for that kind of info? Are you an Apple dev?

This has only happened once, AFAIK, if it was your Mac, would you re-install the OS soon? Wait?

I had to re-install the OS and restore from a TM back up on my previous MBP, a late 2011 (bricked due to an installation of a Wacom tablet driver)... I don't remove the steps but it wasn't that bad.

Reply

Answer 10

Apr 24, 2021 2:53 PM in response to marc cardwell

Personally, I would never act on something that has happened ONCE.

--------

Being an Apple Developer does not get you access to Insider information, and if it did, Non-disclosure agreements would mean I could not tell anyone about it. Where I get this information is being here on the forums and reading and internalizing what others are posting and doing additional searches, as I have for a while nearly every day for the last 20 years. Other Readers "keep me honest" by challenging me if I post stuff that is not supportable.

--------

Personally, I would never act on something that has happened ONCE.

-------

But if you had to re-Install, what is the date of your most recent backup, and by what method?

Reply

Answer 11

marc cardwell Author

Level 2

218 points

Apr 25, 2021 5:14 AM in response to Grant Bennet-Alder

When my previous MBP was bricked, and I had to boot from the recovery drive, I think I restored from a TM backup (possibly I just re-installed the OS from recovery, can't remember). Not sure if I erased, but don't think so.

I started w/ System 6-something, and the concept of not having bootable floppies or CDs still seems weird.

Thanks for you help and expertise on this!

Reply