I have a new MBPro and have been afflicted with Kernel Panic. I have lost the use of the computer already for weeks at a time with no resolution. The hard drive was wiped clean and reinstalled (with difficulty because 2 Time Machine backups failed). Something is wrong with the Monterey and/or the MBP. I had my last MBP since 2014 with no serious problems at all. Tonight 2 kernel panic crashes. Is there no solution in sight?
smoking gun alert:
"panicString" : "panic(cpu 2 caller 0xfffffe001a4556d8): [data.kalloc.16]: element modified after free (off:0, val:0x0000000000003c47, sz:16,
That says a dynamically-allocated memory location changed spontaneously after it was declared free.
That correlates with RAM memory errors,
and your other report (of a completely different problem) supports that assertion because it is not converging on a specific problem in a specific bit of software.
To make progress, you will need to contact support. The first responders will want you to work through some common debugging procedures. When you worked through that processes, ask for a specialist.
Specialists are more knowledgeable but FAR less patient. You can refer them to panic reports you posted on the forums, but NO ONE will believe any conclusions others (including me) have made -- they want to decide for themselves.
.
smoking gun alert:
"panicString" : "panic(cpu 2 caller 0xfffffe001a4556d8): [data.kalloc.16]: element modified after free (off:0, val:0x0000000000003c47, sz:16,
That says a dynamically-allocated memory location changed spontaneously after it was declared free.
That correlates with RAM memory errors,
and your other report (of a completely different problem) supports that assertion because it is not converging on a specific problem in a specific bit of software.
To make progress, you will need to contact support. The first responders will want you to work through some common debugging procedures. When you worked through that processes, ask for a specialist.
Specialists are more knowledgeable but FAR less patient. You can refer them to panic reports you posted on the forums, but NO ONE will believe any conclusions others (including me) have made -- they want to decide for themselves.
.
Kernel panic is not ONE problem, it is one of thousands of possible problems. To make progress, we may need to look at a report.
Kernel 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 start or 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.
One more item that is important is the names of any third-party Extensions you have added. They are shown FIRST in the extensions loaded section
If the above is just "word-salad" to you, just ask and Readers can explain a bit more.
screenshot is a good start, but does not tell what software has been added.
This shows you are running the latest MacOS 12.2.1, on the latest hardware 2021 M1 MacBook Pro.
The panic assured because of a Multiple-processor cooperation problem, possibly including graphics processors as well as CPUs, and possibly a mass Storage device.
One processor locked an exclusion signal or "lock byte" and another processor sat and waited for it to come clear before proceeding. Too long time went by and a timer fired, indicating a processor had wandered off without releasing the lock byte.
Are you having any other wonky symptoms besides these panics?
can you fetch a complete panic report from the location I noted above, and post the whole thing?
One thing they will ask for is that you run the diagnostic. This checks for GROSS errors.
"No Fault Found" is not the same as "all is well".
Here is my word-salad:
{"bug_type":"210","timestamp":"2022-03-06 21:47:13.00 -0500","os_version":"macOS 12.2.1 (21D62)","incident_id":"443B1A3A-AB8C-49F5-ABD1-A27AE338AC66"}
{
"build" : "macOS 12.2.1 (21D62)",
"product" : "MacBookPro18,3",
"kernel" : "Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20\/RELEASE_ARM64_T6000",
"incident" : "443B1A3A-AB8C-49F5-ABD1-A27AE338AC66",
"crashReporterKey" : "007118DC-23E6-80AF-E154-21AEEB1A735B",
"date" : "2022-03-06 21:47:13.42 -0500",
"panicString" : "panic(cpu 3 caller 0xfffffe00193a453c): Spinlock[0xfffffe2fff58e3c0] timeout after 12588384 ticks; current state: 0x3c47, start time: 69809022105, now: 69821610489, timeout: 12582912 @locks.c:723\nDebugger message: panic\nMemory ID: 0x6\nOS release type: User\nOS version: 21D62\nKernel version: Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20\/RELEASE_ARM64_T6000\nFileset Kernelcache UUID: FA4EB485BA9DC1EBAA5D0E80232A48CC\nKernel UUID: BADF56F4-2876-3FF4-AC12-F25E78B09AA1\niBoot version: iBoot-7429.81.3\nsecure boot?: YES\nPaniclog version: 13\nKernelCache slide: 0x0000000011a1c000\nKernelCache base: 0xfffffe0018a20000\nKernel slide: 0x0000000012250000\nKernel text base: 0xfffffe0019254000\nKernel text exec slide: 0x0000000012338000\nKernel text exec base: 0xfffffe001933c000\nmach_absolute_time:
shorten it to the first few pages, and/or do not include anything after the words, "binary images"
I sure realize this. I did a remote diagnostic already that showed a problem with the touch pad that when the machine went to Apple just didn't show up. I never expected this kind of mess from Apple.
I do have screen shots. Will that do the trick? My computer was even with Apple but they could not reproduce the problem.
I can't post the report as it's more than the max allowed here.
use this Icon in the Reply window to get a window that will accept it all:
Hopefully this will work. I couldn't get to "binary images," as that was too many characters. I just guess at this segment.
Thanks so much for getting me this far! I appreciate your patience and assistance here.
Kernal panic (again)
