Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Creep89

macrumors 6502
Original poster
Mar 9, 2012
314
407
Okay, this one is weird. Was playing Football Manager 2017, leading Bayern Munich 4:0 and then.. Nothing. Black screen and my 15" MacBook Pro Late 2016 rebooted (2.7Ghz, 512GB SSD, Radeon Pro 460).

Looking at what caused the issue, I found this one:

Code:
{"os_version":"Watch OS 3.0 (14Y363)","incident_id":"9E9A7834-C280-4491-8EFA-069569DFCF9F","timestamp":"2016-12-06 18:43:08.08 +0000","bug_type":"210"}
{
  "panicString" : "Debugger message: WDT timeout\n9s ago: 2702m10000004\/3 2702l3 2602m10000004\/3 2602l3 2502m10000004\/3 2501l3 2401m10000004\/3 2401l3 2301m10000004\/3 \nMemory ID: 0x1\nOS version: 14Y363\nKernel version: Darwin Kernel Version 16.1.0: Thu Sep 29 20:11:11 PDT 2016; root:xnu-3789.24.3~1\/RELEASE_ARM_T8002\niBoot version: iBoot-3406.20.16\nsecure boot?: YES\nPaniclog version: 5\nKernel slide:     0x000000000fc00000\nKernel text base: 0x8fc01000\nEpoch Time:        sec       usec\n  Boot    : 0x5841e71a 0x0005ab31\n  Sleep   : 0x5846fb5a 0x000513dc\n  Wake    : 0x5846fc36 0x000b4a5c\n  Calendar: 0x5847069b 0x00020fe4\n\nTotal cpu_usage: 14343780\nThread task pri cpu_usage\n0x801fb640 kernel_task 0 6131375\n0x80296640 kernel_task 0 6124338\n\nPanicked task 0x801e61c0: 9385 pages, 100 threads: pid 0: kernel_task\nPanicked thread: 0x801fb640, backtrace: 0x8ffe7af8\n\t\t  lr: 0x8fcda839  fp: 0x8ffe7b28\n\t\t  lr: 0x9011c1c9  fp: 0x8ffe7f98\n\t\t  lr: 0x9066d6cd  fp: 0x8ffe7fa8\n\t\t  lr: 0x906882e5  fp: 0x8ffe7fe8\n\t\t  lr: 0x8ff4d7ed  fp: 0x8ffe7ff8\n\t\t  lr: 0x8fc05ae0  fp: 0x8f2ebfa8\n\t\t  lr: 0x8fc0749c  fp: 0x00000000\n\n      \n",
  "product" : "iBridge1,1",
  "incident" : "9E9A7834-C280-4491-8EFA-069569DFCF9F",
  "build" : "Watch OS 3.0 (14Y363)",
  "date" : "2016-12-06 18:43:06.82 +0000",
  "crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
  "kernel" : "Darwin Kernel Version 16.1.0: Thu Sep 29 20:11:11 PDT 2016; root:xnu-3789.24.3~1\/RELEASE_ARM_T8002",
  "memoryStatus" : {"memoryPressure":{"pagesWanted":0,"pagesReclaimed":0},"decompressions":0,"compressorSize":0,"jetsamLevel":0,"memoryPages":{"fileBacked":8106,"inactive":1136,"active":3264,"wired":25792,"speculative":4620,"throttled":2328,"purgeable":2,"free":88616},"compressions":0,"busyBufferCount":0,"pageSize":4096},
  "processByPid" : {
[...]

So TouchBar crashed my whole MacBook? Does anyone else encounter this kind of problem?
 

xraydoc

Contributor
Oct 9, 2005
10,964
5,425
192.168.1.1
The touch bar itself didn't crash the machine, but OSX's handling of an error returned by the touch bar did. So likely the result of two bugs - one in the touch bar's OS and one in the Mac's OS.

Yeah, Sierra still has a ton o' bugs that need fixing, including several related to the touch bar.
 

Creep89

macrumors 6502
Original poster
Mar 9, 2012
314
407
Thanks for the detailed explanation. Wow. So many bugs like you just said.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.