It's not really deleted until the garbage collection erase the full VSS store (remember the 4KB sector) and re-writes just the valid entries from the circular log. Garbage collection sometimes take up to 11 reboots to fully complete.
You might want to install your MATT card before your Mac bricks to preserve your original flash chip.
No, your value right now is very good, but your issue is usually related to NVIDIA web drivers saving a binary blob that makes modern AMD GPUs crazy under certain conditions.
For a dual CPU MacPro after SoftwareUpdates, yes.
I've should written a clarification on this before, I've talked about this before years ago with @joevt and never discussed it again.
| Type of PanicInfoLog | type A | type B |
| Content: | Just a pointer to a file saved on /Library/Logs/DiagnosticReports | Full crash log, compressed, saved inside the NVRAM entry |
| Erasable: | Yes, with deep NVRAM reset. | No, permanent or at least not removable by deep NVRAM reset. Not yet know if normal garbage collection removes it over time. |
| Can fill the VSS store if happening in a loop: | Usually no, it's a very tiny entry. | Yes, some entries are over 3KB and one dump had 23 saved over the two VSS stores. |
| Often found or not: | This is the everyday crash dump, frequently found on BootROM image dumps. | It was rare to be found present in a dump before BigSur, now is becoming common with Monterey. |
Sure, I'll send it on Monday. This is the signature to detect it:
#
# AAPL,PanicInfoLog signature B
#
0 string \x41\x00\x41\x00\x50\x00\x4C\x00\x2C\x00\x50\x00\x61\x00\x6E\x00\x69\x00\x63\x00\x49\x00\x6E\x00\x66\x00\x6F\x00\x30\x00\x30\x00\x30 NVRAM PanicInfo Log B
Yes, that’s what I do simply because I like knowing that my logic board is still fully functional even without the MATT card. It makes no difference in practice, though.
Until yesterday @Macschrauber tool didn't detected the second type at all, so you couldn't had it shown on his tool.
forums.macrumors.com
it had detected both types of Panic Logs but did not differ them.
It now counts Type A and B and shows both.
Healthy NVRAM normal behaviour on 4,1->5,1 machines
As it seems to get problematic having a lot of compressed text contained Panic Logs the dumper now counts them separately. Type A: a pointer to a file, not problematic Type B: the kernel panic text in multiple compressed parts. Alex have seen very large kernel panics in the nvram after a...
Firmware 144.0.0.0 (latest)
old Bootblock of MP51.007F.B03
12 Memory Configs (ok)
1 xml (ok)
0 iCloud Tokkens (ok)
0 Microsoft Certificates (ok)
1 BluetoothActiveControllerInfos (ok)
1 BluetoothInternalControllerInfos (ok)
0 current-network (ok)
4 AAPL Path Properties (ok)
Invalid VSS Store 1 header (very bad!)
VSS2 is empty (ok after triple nvram reset or recent firmware rebuilt)
34688 Bytes free space of 65472Firmware 144.0.0.0 (latest)
old Bootblock of MP51.007F.B03
25 + 3 Memory Configs (caution)
0 + 0 xml (ok)
0 + 0 iCloud Tokkens (ok)
0 + 0 Microsoft Certificates (ok)
1 + 1 BluetoothActiveControllerInfos (ok)
1 + 1 BluetoothInternalControllerInfos (ok)
1 + 1 current-network (ok)
5 + 1 AAPL Path Properties (ok)
3520 Bytes free space of 65472Firmware 144.0.0.0 (latest)
old Bootblock of MP51.007F.B03
12 Memory Configs (ok)
1 xml (ok)
0 iCloud Tokkens (ok)
0 Microsoft Certificates (ok)
1 BluetoothActiveControllerInfos (ok)
1 BluetoothInternalControllerInfos (ok)
0 current-network (ok)
4 AAPL Path Properties (ok)
VSS2 is empty (ok after triple nvram reset or recent firmware rebuilt)
34688 Bytes free space of 65472Ah, interesting. I’ve not experienced that issue - are you still offering a BootROM reconstruction, Alex? Should probably just DM.
. Is that critical and how do I fix this ?
Firmware 144.0.0.0 (latest)
old Bootblock of MP51.007F.B03
Boot0001 is EFI\OC\OpenCore.efi
10 Memory Configs (ok)
0 xml (ok)
2 Kernel Panic Dumps Type A: Pointer Type
0 iCloud Tokkens (ok)
0 Microsoft Certificates (ok)
3 BluetoothActiveControllerInfos (not ok)
2 BluetoothInternalControllerInfos (ok)
0 current-network (ok)
2 AAPL Path Properties (ok)
42368 Bytes free space of 65472
Correct, I used ToggleSIP in OpenCore boot picker to disable it.
Thank, this is very helpful. If I really get into a habbit of flashing on a regular basis I would rather not swap graphic cards all the time. I do have a HD7950 with MacROM lying around though.
After the forced garbage collection you have the expected value for a long running NVRAM volume with a similar config of the one on your signature. The NVRAM is now the Achilles hell of MacPro5,1 and you have track it for some time, if your available space is frequently in the low tens or even worse (OCLP have more entries on the NVRAM than pure OC) time to think on getting a upgraded/never booted BootROM image.