Kernel panic after latest osx Sierra update

As per the article : macOS Sierra: If your Mac restarts and a message appears

If your Mac restarts unexpectedly, an error known as a kernel panic occurred. After the restart, you’ll see a message that your computer restarted because of a problem.

The most likely cause is faulty software. A kernel panic can also be caused by damaged or incompatible hardware, including external devices attached to your Mac.

Note: To print these instructions before you start, click the Share button in the Help window, then choose Print.

If the kernel panic is caused by a known problem, the faulty software is identified. To make sure that this software doesn’t continue to cause kernel panics, move it to the Trash.

If the faulty software is not identified and your Mac continues to experience kernel panics, try the following:

• Restart your Mac in safe mode. If it successfully starts up in safe mode, choose Apple menu > App Store, click Updates, then install any available updates.
• Uninstall any plug-ins or other enhancement software from manufacturers other than Apple. If you recently updated macOS or an app, plug-ins and other software that worked in the past may no longer be compatible. Read the manufacturer’s documentation (including Read Me notes) to be sure the software is compatible with your version of macOS.
• Disconnect all USB and FireWire devices, except for the Apple keyboard and mouse. Remove hardware upgrades from other manufacturers, such as random-access memory (RAM) and Peripheral Component Interconnect (PCI) cards. Then try restarting your Mac.If this resolves the issue, reconnect one device at a time, restarting your Mac after reconnecting each one, until you determine which device is causing the problem.
• Reset parameter random-access memory (PRAM).
• Use Apple Diagnostics or Apple Hardware Test. These apps can tell you if hardware you installed, such as additional memory, is incompatible, improperly installed, or defective.
• Use Disk Utility to repair your startup disk or your disk permissions.

If the steps above don’t help, try reinstalling macOS.

Note: If you moved or renamed a system file or folder, you must reinstall macOS—it won’t work to just replace or rename the item.

See if you can boot into Safe Mode, and if you can, uninstall whatever installed the netusb controller kernel extension.

However, the -x boot-args tells the system to boot into Safe Mode always, so I'm not sure you would be able to boot into Safe Mode

Use safe mode to isolate issues with your Mac - Apple Support

Hi everyone,

I was able to fix this problem (tl.uds.netusb.controller kernel panic on boot) by removing a kernel extension named kudstplink.kext (which seems to be related to TP-Link)

Although this extension folder's been last modified since Feb 2016, the problem first appeared in May 2017, after a operating system update.

Here's what I did to fix the issue:

1. I booted my computer in Recovery Mode (hold the Command and R keys)
2. Under Utilities, I opened a Terminal and typed the following:
   1. cd /Volumes/Macintosh HD (go to your hard drive)
   2. mv /System/Library/Extensions/kudstplink.kex /Users/YOUR_USERNAME/ (move kernel extension somewhere else

Quit recovery mode and it should now reboot.

Note that having previously installed (even if uninstalled) TP-Link printer controller application might be the cause:

http://forum.tp-link.com/showthread.php?82784-Archer-D7-USB-printer-controller-n ot-working-with-OS-X-El-Captain/page2

Hope this helps,

Kernel Panics are primarily caused by hardware faults and third-party kernel extensions. Apps do not cause them.

Your picture indicates a kernel extension in the backtrace which would point to that as being incompatible with the update.

It looks like the name is tl.uds.netusb.controller

I can't figure out what it is, but it may be for a NetGear router--not sure why it would need a kernel extension, though.

The files don't necessarily have the same name as what shows up in the kernel panic. It is on your system, though, as it shows being in the backtrace. It would be in /System/Library/Extensions or /Library/Extensions.

It also could be loaded by something that starts up in /Library/LaunchDaemons or /Library/LaunchAgents.

I have an iMac 27 mid 2011. Since 10.12.1, I tried a few updates, every time, I got kernel panic, and restored back to 10.12.1. This weekend, I tried 10.12.6 again, it finally worked. The only difference was I disconnected all USB devices. That might matter. Now, I am on macOS High Sierra 10.13.2, everything works perfectly, and even faster.