127      iPhone_iPad_Mac_apple

System Crashes when using Thunderbolt Ethernet ...

Since updating to 10.12.4, I can no longer use my Thunderbolt Ethernet adapter.  Plugging in the Thunderbolt Ethernet adapter (with a network cable attached) causes the system to panic and crash (black screen with gray power logo in the background, and white text indicating system crash).

When the ethernet cable is not plugged in to the thunderbolt ethernet adapter, the system stays running.  But seconds after plugging in the ethernet cable, the system will panic.  I have tried several different network cables, and a different switch, and different ports on the switch, the result is the same.  No other systems connected to the switch are experiencing the same issue (I don't have another system with a thunderbolt-ethernet adapter on this switch -- the other systems are an iMac, HP printer, Cisco phone).

This used to work pre 10.12.4, but after the update, the problem started appearing.

I have tried SMC reset, and NVRAM reset

So to complete the resolution, to remove those pesky com.citrix.* and com.deterministicnetworks.* kernel extensions, I needed to uninstall the Citrix Plug-In by running the Uninstall.app in /Library/Application Support/Citrix

Does it do it on every Thunderbolt port on the macbook or just one of them? What was the last few messages in the Console.app window BEFORE the crash??

Good luck...

Does it on every thunderbolt port.  (BTW, I tried it on the iMac running El Capitan and it worked fine).

Let me reproduce the problem again and will post an update with the console logs from system.log.

Here's the contents of system.log prior to the reboot.  I'm guessing that the message that says "bootlog[0]: BOOT_TIME ..." is when the system booted.

Contents of Log is in: https://pastebin.com/embed_js/t8f9sqtB

Unfortunately there is not much info there - just entries about postfix errors at 12:32:07 on Apr 3 and last entry before booting at 12:32:09 regarding some sort of complaint about vpn interface. The system booted up at 12:33:22 on Apr 3 (about 1 minute and 13 seconds after that last message. Wonder if there might be more info using "log" Terminal command? Something like:

    log show --style syslog --start '2017-04-03 12:32:00' --end '2017-04-03 12:33:23' --info

Do a "man log" if you wish to see what the different options above are for. Make sure to simply copy/paste the above command into a Terminal window. If you get anything different than what you already posted at pastebin.com please post again.

Good luck...

No relevant entries either using the log command.  I even did "--debug".  I just saw a bunch of IMAP and Webkit related messages.  I think the crash happens so hard that the system is unable to log any related messages.

I did send the crash reports to apple (and also logged a bug at bugreport.apple.com).  I'm hoping apple is able to reproduce and fix this soon.

I have the same issue. It is easy to reproduce. Starting in "safe mode" allows the adaptor to be used, but repairing disc and disabling startup items (I have none) does not solve the problem when using the adaptor during regular startup. Just wanted to share this additional data point. My crash reports have also been sent to Apple.

It's good to know that I'm not alone in this (I'm not glad that you're experiencing the problem, but at least it's not unique to me).  I will try the "safe mode".

I tried uninstalling my Cisco Anyconnect VPN software just in case it was interfering with it, but the problem continued even after removing the software completely.

Thanks to your hint I think I might have resolved the issue on my macbook pro.  In "safe mode" I took a list of all kernel extensions that were loaded using "kextstat".  Then in normal boot mode, I also took the list of all kernel extensions loaded using the same command.

Then I compared them to get the list of kernel extensions loaded during normal boot that is not loaded during safe mode.  Those are my suspects.  I also eliminated the "com.apple.*" ones since I don't suspect apple's kernel extensions to be doing this kind of thing (they do test them together --- I hope).

So I was left with the following:

com.sns.driver.SNSArchitectureModel

com.deterministicnetworks.driver.dniregistry

com.deterministicnetworks.driver.dne

com.citrix.driver.net6im

com.sns.driver.Xtarget

com.sns.driver.SnsiSCSI

com.Cycling74.driver.Soundflower

net.lundman.kernel.dependencies

net.lundman.spl

net.lundman.zfs

org.virtualbox.kext.VBoxDrv

org.virtualbox.kext.VBoxUSB

org.virtualbox.kext.VBoxNetFlt

org.virtualbox.kext.VBoxNetAdp

com.McAfee.FMPSysCore

com.intelsecurity.FileCore

com.McAfee.AVKext

com.McAfee.SFKext

My prime suspects are the ones that have "net" in their names, so that would be "deterministicnetworks" and the "VBoxNet"  ones.  Sure enough when I removed all of the org.virtualbox and com.deterministicnetworks, the problem disappeared.  So it was a matter of trial and error to figure out which one of virtualbox or the deterministicnetworks was the cause.

I've narrowed it down to "com.deterministicnetworks.driver.*".  When I unload those two and the "com.citrix.driver.net6im" (the citrix one was necessary to unload because first in order to unload the com.deterministicnetworks* extensions) then the problem went away.

I need to figure out what application installed that citrix and deterministicnetworks kernel extensions and delete those.

Oh and by the way, in case anyone needs to know how to unload these:

# kextunload -b com.citrix.driver.net6im

# kextunload -b com.deterministicnetworks.driver.dniregistry

# kextunload -b com.deterministicnetworks.driver.dne

Thanks again to BHEvans for pointing me to the fact that it works in safe mode.

Uninstall MacAfee. It tends to interfere with the computer's operation while providing minimal to no benefit.

McAfee Uninstall               Resources is near bottom of the page

McAfee is required by my employer to connect this laptop to their network.  So can't uninstall that.  Besides it wasn't the one causing the issue.  It was the citrix and deterministicnetworks kernel extensions.

So to complete the resolution, to remove those pesky com.citrix.* and com.deterministicnetworks.* kernel extensions, I needed to uninstall the Citrix Plug-In by running the Uninstall.app in /Library/Application Support/Citrix

This is great information. I did note that uninstalling citrix will remove the kext's you noted. The only non apple kext's that I had were citrix. I do need citrix for work, and installed the latest version (which replaces the kext's). The latest version came out just a couple of weeks ago hopefully plays better with updated kernel extensions. I will know tomorrow at work.

Additionally, on my home network, there were no problems using the ethernet adapter, but at work had the reliable crash with network adapter. Don't get that at all. Will update in am regarding newer citrix kext's and success (or not) with newer citrix.

No luck for me. Removed all 3 with # kextunload -b.... commands and used downloaded citrix uninstaller. Pesky com.citrix.driver.net6im remained and still (apparently) causes the crash while on my work network. Will wait for next OS X update and poke around the citrix site.

Did you try using the adapter after unloading those 3 kexts?  Did it work?

Try to get Citrix support involved to get them to troubleshoot/debug the issue as it seems it's a Citrix problem.

最后更新：2017-09-18 21:53:39

  上一篇： i want to be able to save a series of outlook m...

  下一篇： Mail does not open encrypted attachment from ou...