16" MacBook Pro Kernal panic

[David Russ]

So I may have messed up. A bit of pop got on my trackpad net the bottom. I cleaned it up and it seemed to be fine but later I went to boot into bootcamp. Then It turned off by itself, fans got loud.

Booted up macOS and got this error:

{"caused_by":"unknown","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 4.4 (17P4281)","timestamp":"2020-04-24 00:21:06.00 +0000","incident_id":"D089CA46-9C52-44A2-A7EA-4BDE7A10AEB7"}
{
  "build" : "Bridge OS 4.4 (17P4281)",
  "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" : "D089CA46-9C52-44A2-A7EA-4BDE7A10AEB7",
  "crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
  "date" : "2020-04-24 00:21:05.97 +0000",
  "panicString" : "panic(cpu 1 caller 0xfffffff01ce2a19c): PUP PANIC - deserialize: saved state does not match current state. serialization cursor 0x2c9bc - pup-workloop(1)\ndeserialize: saved state does not match current state. serialization cursor 0x2c9bc\nRTKit: RTKit_iOS-1264.100.25.release - Client: not set\n!UUID: 5558537c-c1ee-338e-84c7-052296b7d20e\nTime: 0x000000010d53b9f6\n\nFaulting task stack frame:\n\nFaulting task

Does this seem hardware related or just a anomaly that ironically happened after this mini spill?

 

[cmaier]

It doesn’t look like a hardware issue, but you can never tell. If you reboot MacOS does it keep doing this? It looks like a bridgeos issue with the T2 chip that powers the touch strip.

 

[chrfr]

So I may have messed up. A bit of pop got on my trackpad net the bottom. I cleaned it up and it seemed to be fine but later I went to boot into bootcamp. Then It turned off by itself, fans got loud.

Booted up macOS and got this error:

{"caused_by":"unknown","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 4.4 (17P4281)","timestamp":"2020-04-24 00:21:06.00 +0000","incident_id":"D089CA46-9C52-44A2-A7EA-4BDE7A10AEB7"}
{
  "build" : "Bridge OS 4.4 (17P4281)",
  "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" : "D089CA46-9C52-44A2-A7EA-4BDE7A10AEB7",
  "crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
  "date" : "2020-04-24 00:21:05.97 +0000",
  "panicString" : "panic(cpu 1 caller 0xfffffff01ce2a19c): PUP PANIC - deserialize: saved state does not match current state. serialization cursor 0x2c9bc - pup-workloop(1)\ndeserialize: saved state does not match current state. serialization cursor 0x2c9bc\nRTKit: RTKit_iOS-1264.100.25.release - Client: not set\n!UUID: 5558537c-c1ee-338e-84c7-052296b7d20e\nTime: 0x000000010d53b9f6\n\nFaulting task stack frame:\n\nFaulting task

Does this seem hardware related or just a anomaly that ironically happened after this mini spill?

If it recurs then yes, I'd assume it's almost certain that the spill did damage. It doesn't take a lot of a sticky, acidic substance to make a computer malfunction.

 

[David Russ]

If it recurs then yes, I'd assume it's almost certain that the spill did damage. It doesn't take a lot of a sticky, acidic substance to make a computer malfunction.

I hasn't reoccured yet and so far I've used it for about 6 hours since the spill occurred... hopefully I'm good. Gotta be more careful I guess

 

[chrfr]

I hasn't reoccured yet and so far I've used it for about 6 hours since the spill occurred... hopefully I'm good. Gotta be more careful I guess

You'll definitely want to be more careful. Problems caused by liquids can also take some time to manifest. I had a user whose MacBook Pro suffered a wine spill and worked fine for almost a year before the corrosion caused it to fail.

 

[aaff]

Seems to be pretty widespread bug/error - I have gotten the same one on my imac pro, and it looks like it is connected to the T2 chip.

see this post in the mac mini forum: https://forums.macrumors.com/thread...e-210-after-security-update-2020-002.2228812/

 

[David Russ]

You'll definitely want to be more careful. Problems caused by liquids can also take some time to manifest. I had a user whose MacBook Pro suffered a wine spill and worked fine for almost a year before the corrosion caused it to fail.

Definitely will be.. Just last week some salsa got on my spacebar and I had to pop it out to clean it. I'm guessing the trackpad doesn't come out so easily