You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once Node.js and npm are installed to OS X, unless you are at 10.11.4 or better trying to enumerate Tessel 2 devices on USB will deadlock in the kernel.
The node process will be stuck, and the CPU use for the kernel will spike to 100% and stay there. You will have to reboot the box to clear this up. Attempting to kill the locked node process just causes it to turn into a zombie process.
The kernel is spinning on something in the USB subsystem. I apologize for not getting the "sample" output these offending processes.
Upgrading to 10.11.4 (which I was not automatically notified of, otherwise I probably would have already accepted it!) solve the problem and allowed me to enumerate and provision the Tessel device via t2.
The text was updated successfully, but these errors were encountered:
Once Node.js and
npm
are installed to OS X, unless you are at 10.11.4 or better trying to enumerate Tessel 2 devices on USB will deadlock in the kernel.(See here: https://forums.tessel.io/t/tessel-on-os-x-el-capitan/2298)
The node process will be stuck, and the CPU use for the kernel will spike to 100% and stay there. You will have to reboot the box to clear this up. Attempting to kill the locked node process just causes it to turn into a zombie process.
The kernel is spinning on something in the USB subsystem. I apologize for not getting the "sample" output these offending processes.
Over on the Tessel forums I was referred to this USB OS X issue which seems relevant.
Upgrading to 10.11.4 (which I was not automatically notified of, otherwise I probably would have already accepted it!) solve the problem and allowed me to enumerate and provision the Tessel device via t2.
The text was updated successfully, but these errors were encountered: