iMac Pro restarting because of a problem?

I'd had a pretty good run of no kernel panics for a while until today. Now it's Bridge OS 2.3.1, otherwise it all looks the same. I'm hoping the silence means Apple's going to put out a fix any day now?

Not sure I understand your post. Do you mean that all was fine until Bridge OS 2.3.1?

Are you running 10.13.5 (17F77)?

Was there some kind of a supplemental update that triggered the new kernel panics?

How long had your system remained stable?

John

Ocean City, NJ

The last kernel panic log I posted was Bridge OS 2.3, now it's 2.3.1, that's all I was saying. Otherwise, at a brief glance, the kernel panic log looks the same. I'm not sure which update had 2.3.1, and yes I'm on 10.13.5 now. I've gone several weeks without a panic through a combination of always shutting the computer off when I'm done using it and just not using it as much recently. But I've been using it more the last few days and forgot to shut it off, and sometime when I was away from it, it had a kernel panic.

I'm having the exact same issue. iMac Pro 10-Core Vega 64GB RAM. I am also using a thunderbolt to TB3 adapter and interestingly the devices connected to it didn't start back up properly... This is my report...

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3.1 (15P5064)","timestamp":"2018-07-02 10:30:47.36 +0000","incident_id":"D1CEC7D6-E96A-4ABC-873A-9298F32326C2"}

{

"build" : "Bridge OS 2.3.1 (15P5064)",

"product" : "iBridge2,1",

"kernel" : "Darwin Kernel Version 17.6.0: Sat May 5 19:46:24 PDT 2018; root:xnu-4570.60.21~23\/RELEASE_ARM64_T8010",

"incident" : "D1CEC7D6-E96A-4ABC-873A-9298F32326C2",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-07-02 10:30:47.28 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff01baae984): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 15P5064\nKernel version: Darwin Kernel Version 17.6.0: Sat May 5 19:46:24 PDT 2018; root:xnu-4570.60.21~23\/RELEASE_ARM64_T8010\nKernelCache UUID: 82688F4A0C28C17581768EF79472E265\niBoot version: iBoot-4076.60.11\nsecure boot?: YES\nx86 EFI Boot State: 0xd\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide: 0x0000000015200000\nKernel text base: 0xfffffff01c204000\nEpoch Time: sec usec\n Boot : 0x5b31ea6a 0x0008cf17\n Sleep : 0x5b37646c 0x0001c272\n Wake : 0x5b39cbca 0x000669e9\n Calendar: 0x5b39febc 0x00019041\n\nPanicked task 0xffffffe0002a22b0: 2476 pages, 166 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe00066ea50, backtrace: 0xffffffe0167a3530, tid: 349\n\t\t lr: 0xfffffff01c3f96bc fp: 0xffffffe0167a3670\n\t\t lr: 0xfffffff01c2e15f4 fp: 0xffffffe0167a3680\n\t\t lr: 0xfffffff01c313a44 fp: 0xffffffe0167a39f0\n\t\t lr: 0xfffffff01c313dd4 fp: 0xffffffe0167a3a50\n\t\t lr: 0xfffffff01c315914 fp: 0xffffffe0167a3a70\n\t\t lr: 0xfffffff01baae984 fp: 0xffffffe0167a3ae0\n\t\t lr: 0xfffffff01bab0bc8 fp: 0xffffffe0167a3b80\n\t\t lr: 0xfffffff01baae13c fp: 0xffffffe0167a3c00\n\t\t lr: 0xfffffff01ba6daa4 fp: 0xffffffe0167a3c30\n\t\t lr: 0xfffffff01c7710b8 fp: 0xffffffe0167a3c60\n\t\t lr: 0xfffffff01c770a10 fp: 0xffffffe0167a3c90\n\t\t lr: 0xfffffff01c2ec500 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 78128 **\n",

"macOSPanicFlags" : "0x0",

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

"memoryStatus" :

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Apr 9 2018 19:30:51 version 9.130.18.10.32.3.0 FWID 01-ea787869

Bluetooth: Version 6.0.6f2, 3 services, 27 devices, 1 incoming serial ports

Network Service: Ethernet, Ethernet, en0

Network Service: Wi-Fi, AirPort, en1

PCI Card: pci17d3,1880, RAID Controller, Thunderbolt@67,0,0

PCI Card: UltraStudio Mini Monitor, Video, Thunderbolt@71,0,0

USB Device: USB 3.0 Bus

USB Device: 4-Port USB 3.0 Hub

USB Device: WorkflowCR2

USB Device: USB DONGLE

USB Device: USB 2.0 BILLBOARD

USB Device: Corsair Gaming M65 Pro RGB Mouse

USB Device: Magic Keyboard with Numeric Keypad

USB Device: 4-Port USB 2.0 Hub

USB Device: USB Audio Device

USB Device: XBOX ACC

USB Device: iBridge Bus

USB Device: Headset

USB Device: iBridge ALS

USB Device: iBridge FaceTime HD Camera (Built-in)

USB Device: iBridge

Thunderbolt Bus: iMac Pro, Apple Inc., 33.2

Thunderbolt Device: ARC8050, Areca, 3, 26.2

Thunderbolt Bus: iMac Pro, Apple Inc., 33.2

I sent my crash reports and sysdiafnose to an Apple outreach guy last week, he would not acknowledge anything other than they are gathering information at this point.

I’m guessing it’s the same for everyone else.

For all other people new to this issue I’ll say this again, it’s not your peripherals and it’s most likely not your hardware (had mine replaced twice), either sit still and wait for Apple to fix it or return it.

Anything else is a waste of your time.

So, I got a call from Apple Support about this issue on Friday. We talked for an hour, time in which I explained when it happens and when it doesn't happen. He was watching with me what I was doing, what settings I had enabled or disabled and he witnessed the crash with me. In my case if I have the power saving settings turned on + the apple watch login + asking for the password after sleep or lock it crashes either in sleep or when I export 4K video in Final Cut Pro. Once I disable all those settings the machine runs fine. It never restarts while sleeping and I am able to export my 4K videos. This gives me hope, because it could be only a software issue.

Wow, was doing fine there for about a month. No ReStarts.

No today, seemingly for no reason it happened again.

Getting ready to install the latest APPLE-SA-2018-7-9-4 macOS High Sierra 10.13.6 "security update" just released, but I'll wait a day or so just in case it ends up being buggy in and of itself, for good measure.

Was happy.

Now sad.

Here's the beginning of my crash report which I sent into Apple:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3.1 (15P5064)","timestamp":"2018-07-09 21:26:27.02 +0000","incident_id":"FAC2411E-8E14-42C5-862E-E97CAD421D7F"}

{

"binaryImages" : [

[

"82688f4a-0c28-c175-8176-8ef79472e265",

18446743936270598144,

"U"

],

[

"00000000-0000-0000-0000-000000000000",

0,

"A"

],

[

"a577b904-cd85-3ba8-9b65-4d5a1d11128a",

6442450944,

"S"

]

],

"build" : "Bridge OS 2.3.1 (15P5064)",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-07-09 21:26:25.26 +0000",

"incident" : "FAC2411E-8E14-42C5-862E-E97CAD421D7F",

"kernel" : "Darwin Kernel Version 17.6.0: Sat May 5 19:46:24 PDT 2018; root:xnu-4570.60.21~23\/RELEASE_ARM64_T8010",

"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 988560 **\n",

"macOSPanicFlags" : "0x4",

"macOSPanicString" : "Panic(CPU 13, time 249756182142415): NMIPI for unresponsive processor: TLB flush timeout, TLB state:0x0\nRAX: 0x000000000000005f, RBX: 0xffffff8018699cb0, RCX: 0x00000000000005f0, RDX: 0x0000000000100005\nRSP: 0xffffff83c7113d90, RBP: 0xffffff83c7113dc0, RSI: 0x0000000000000000, RDI: 0xffffff80186996a0\nR8: 0xffffffffffffffff, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000000\nR12: 0xffffff805a40f4f0, R13: 0xffffff80567e8d28, R14: 0xffffff80186996a0, R15: 0xffffff8018699cb0\nRFL: 0x0000000000000086, RIP: 0xffffff8017e8e9de, CS: 0x0000000000000008, SS: 0x0000000000000010\nBacktrace (CPU 13), Frame : Return Address\n0xffffff83b2ce8f70 : 0xffffff8017f87314 \n0xffffff83b2ce8fd0 : 0xffffff8017e1f336 \n0xffffff83c7113dc0 : 0xffffff8017e877fb \n0xffffff83c7113e30 : 0xffffff8017e875c6 \n0xffffff83c7113e80 : 0xffffff8017e1f453 \n0xffffff83c7113fa0 : 0xffffff8017e1e3c8 \n\nBSD process name corresponding to current thread: kernel_task\n\nMac OS version:\n17F77\n\nKernel version:\nDarwin Kernel Version 17.6.0: Tue May 8 15:22:16 PDT 2018; root:xnu-4570.61.1~1\/RELEASE_X86_64\nKernel UUID: CC1699EE-71B5-3AF1-AAA3-6DBD16222B92\nKernel slide: 0x0000000017c00000\nKernel text base: 0xffffff8017e00000\n__HIB text base: 0xffffff8017d00000\nSystem model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)\n\nSystem uptime in nanoseconds: 249757497720689\nlast loaded kext at 192840133990187: $TMSafetyNet\t8 (addr 0xffffff7f9bbd5000, size 12288)\nlast unloaded kext at 192839424333168: $TMSafetyNet\t8 (addr 0xffffff7f9bbd5000, size 8192)\nloaded kexts:\n$TMSafetyNet\t8\n>!AUpstreamUserClient\t3.6.5\n@kext.AMDFramebuffer\t1. 6.6\n@kext.AMDRadeonX5000\t1.6.6\n>!AGraphicsDevicePolicy\t3.18.52\n@filesystems .autofs\t3.0\n@AGDCPluginDisplayMetrics\t3.18.52\n>!AHV\t1\n|IOUserEthernet\t1.0 .1\n|IO!BSerialManager\t6.0.6f2\n>AGPM\t110.23.37\n>!

Has anyone updated from 10.13.5 to the newly released 10.13.6 yet?

Any improvements, any problems?

John

Ocean City, NJ

==== ==== ==== ==== ==== ==== ====

UPDATE ALERT FROM APPLE:

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA256

APPLE-SA-2018-7-9-4 macOS High Sierra 10.13.6, Security Update

2018-004 Sierra, Security Update 2018-004 El Capitan

macOS High Sierra 10.13.6, Security Update 2018-004 Sierra, and

Security Update 2018-004 El Capitan are now available and address

the following:

AMD

Available for: macOS High Sierra 10.13.5

Impact: A malicious application may be able to determine kernel

memory layout

Description: An information disclosure issue was addressed by

removing the vulnerable code.

CVE-2018-4289: shrek_wzw of Qihoo 360 Nirvan Team

APFS

Available for: macOS High Sierra 10.13.5

Impact: An application may be able to execute arbitrary code with

kernel privileges

Description: A memory corruption issue was addressed with improved

memory handling.

CVE-2018-4268: Mac working with Trend Micro's Zero Day Initiative

ATS

Available for: macOS High Sierra 10.13.5

Impact: A malicious application may be able to gain root privileges

Description: A type confusion issue was addressed with improved

memory handling.

CVE-2018-4285: Mohamed Ghannam (@_simo36)

CFNetwork

Available for: macOS High Sierra 10.13.5

Impact: Cookies may unexpectedly persist in Safari

Description: A cookie management issue was addressed with improved

checks.

CVE-2018-4293: an anonymous researcher

CoreCrypto

Available for: OS X El Capitan 10.11.6, macOS Sierra 10.12.6

Impact: A malicious application may be able to break out of its

sandbox

Description: A memory corruption issue was addressed with improved

input validation.

CVE-2018-4269: Abraham Masri (@cheesecakeufo)

DesktopServices

Available for: macOS Sierra 10.12.6

Impact: A local user may be able to view sensitive user information

Description: A permissions issue existed in which execute permission

was incorrectly granted. This issue was addressed with improved

permission validation.

CVE-2018-4178: Arjen Hendrikse

IOGraphics

Available for: macOS High Sierra 10.13.5

Impact: A local user may be able to read kernel memory

Description: An out-of-bounds read issue existed that led to the

disclosure of kernel memory. This was addressed with improved input

validation.

CVE-2018-4283: @panicaII working with Trend Micro's Zero Day

Initiative

Kernel

Available for: OS X El Capitan 10.11.6, macOS Sierra 10.12.6, macOS

High Sierra 10.13.5

Impact: Systems using Intel® Core-based microprocessors may

potentially allow a local process to infer data utilizing Lazy FP

state restore from another process through a speculative execution

side channel

Description: Lazy FP state restore instead of eager save and restore

of the state upon a context switch. Lazy restored states are

potentially vulnerable to exploits where one process may infer

register values of other processes through a speculative execution

side channel that infers their value.

An information disclosure issue was addressed with FP/SIMD register

state sanitization.

CVE-2018-3665: Julian Stecklina of Amazon Germany, Thomas Prescher of

Cyberus Technology GmbH (cyberus-technology.de), Zdenek Sojka of

SYSGO AG (sysgo.com), and Colin Percival

libxpc

Available for: OS X El Capitan 10.11.6, macOS Sierra 10.12.6, macOS

High Sierra 10.13.5

Impact: An application may be able to gain elevated privileges

Description: A memory corruption issue was addressed with improved

memory handling.

CVE-2018-4280: Brandon Azad

libxpc

Available for: macOS High Sierra 10.13.5

Impact: A malicious application may be able to read restricted memory

Description: An out-of-bounds read was addressed with improved input

validation.

CVE-2018-4248: Brandon Azad

LinkPresentation

Available for: macOS High Sierra 10.13.5

Impact: Visiting a malicious website may lead to address bar spoofing

Description: A spoofing issue existed in the handling of URLs. This

issue was addressed with improved input validation.

CVE-2018-4277: xisigr of Tencent's Xuanwu Lab (tencent.com)

Additional recognition

Help Viewer

We would like to acknowledge Wojciech Reguła (@_r3ggi) of SecuRing

for their assistance.

Help Viewer

We would like to acknowledge Wojciech Reguła (@_r3ggi) of SecuRing

for their assistance.

Help Viewer

We would like to acknowledge Wojciech Reguła (@_r3ggi) of SecuRing

for their assistance.

Help Viewer

We would like to acknowledge Wojciech Reguła (@_r3ggi) of SecuRing

for their assistance.

Kernel

We would like to acknowledge juwei lin (@panicaII) of Trend Micro

working with Trend Micro's Zero Day Initiative for their

assistance.

Security

We would like to acknowledge Brad Dahlsten of Iowa State University

for their assistance.

I updated to 10.13.6 last night (UK), as I'd had a message from the Mac Rumors forum that it fixes the issue of (non-auto adjusted) screen brightness resetting to 90% after a reboot. Sure enough, that issue is now resolved.

One other thing I've noticed is that my two external drives (a LaCie 2-Big Thunderbolt on a 2-3 adaptor, and a WD Elements on USB) now spin down and go to sleep, when I sleep the iMac Pro (previously, they would repeatedly spin down, then fire up again, then spin down, and so on ... even though the iMac Pro was sleeping).

Can't comment on the Kernel Panics shutdowns/restarts, as I've not had any now for several weeks (in fact, since I wiped the machine and re-installed 10.13.4 from Internet Recovery). That said, I haven't given mine any hard work to do (no 4K video conversions or encoding). For the last few weeks, I've had Powernap enabled, as well as 'wake for network access' and 'put hard drives to sleep when possible' - all the things that, early on, I'd disabled to try to prevent the shutdowns.

At the risk of tempting fate, mine seems to be stable at present. May even re-enble 'unlock with Apple Watch'...

John/newmediagroup - Please don't copy/paste public documents - all of us following this thread get an email with your entire post. Further, what you copy/pasted was only the security update content of the 10.13.6 release which wouldn't typically address any of the issues any here are experiencing... it is the bug fixes / updates that you/we are interested in.

lienffur - Thanks for letting us know that the brightness bug is fixed in 10.13.6. Saw that in the dedicated thread for that issue too. Yay. Small things. ;-) Good news on your external drives spinning down, too! Thanks!

I updated as soon as I saw it was available. No problems with the upgrade so far. Too early to really say if it’s had an impact on the kernel panics, none so far but mine have varied from every few days to every few weeks.

I am on 10.13.6 and still experiencing the random restarts. Apple previously replaced my 18-core iMac Pro with a new one and I immediately started experiencing the random restarts on the new machine. This is obviously a major bug pertaining to the iMac Pro. It occurs for me nearly every time I export a video out of Final Cut Pro.

Random ejecting of RAID arrays attached via ThunderBolt 3 is also an issue. It happens nonstop with a RAID 0 configured with Disk Utility's RAID Assistant—on both 18-core iMac Pro machines I have had.

Are your kernel panics while you’re away from the computer or during some specific task? On the previous macOS version I was getting kernel panics while away a little more often than once a week. I’ve had none since installing the latest update, but it’s only been a little over a week, too early for me to come to any conclusions.

The random shutdowns/restarts happen the majority of the time when exporting from Final Cut Pro. It's literally a crapshoot as to whether or not an export will succeed or cause the iMac Pro to reboot. Just the other day, I had over 10 random shutdowns during exporting in a 24-hour period. At this point, it's really hard to call them "random," because I know that exporting from FCPX is likely going to cause the system to shut down and reboot. Per Twitter, I'm not the only one experiencing this behavior during export.

Thanks both. I've also had kernel panics since the machine was new, through several macOS updates (until now, knock on wood). I've seen two main semi-reproducible causes reported -- first, as I've been experiencing, when I step away from the computer and it's not doing anything, after some period of time it has a kernel panic. Second, several people report fairly reproducible kernel panics when exporting video from Final Cut Pro. These are not the only ones, but these are the two most common I've seen discussed.

swivet reports that the 10.13.6 update has't changed anything with the Final Cut Pro kernel panics. Has anyone experienced the kernel panics while the computer is doing nothing since the 10.13.6 update? And maybe in either case if you could post the first few lines of the kernel panic log You should be able to find kernel panic logs form recent kernel panics here: /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge

I've still had no "while I'm away" kernel panics since the update, going on about a week and a half now. But at one point I went at least three weeks without one, and then started having them every few days.

Thanks.