You might face a PSOD after/during the USB disconnect. If you have, you might see a PSOD with backtrace similar to below:
cpu17:33399)@BlueScreen: #GP Exception 13 in world 33399:vmklinux_9:h @ 0x41802c42b8e8
cpu17:33399)Code start: 0x41802c400000 VMK uptime: 3:16:17:26.592
cpu17:33399)0x439113b9b830:[0x41802c42b8e8]DLM_malloc@vmkernel#nover+0x31c stack: 0x41802c7ae9c0
cpu17:33399)0x439113b9b880:[0x41802c42d22b]DLM_memalign@vmkernel#nover+0x7f stack: 0x80
cpu17:33399)0x439113b9b8b0:[0x41802c429c13]Heap_AlignWithTimeoutAndRA@vmkernel#nover+0xf3 stack: 0x15
cpu17:33399)0x439113b9b940:[0x41802cb3c423][email protected]#9.2+0x2b stack: 0x0
cpu17:33399)0x439113b9b960:[0x41802ccf8807]ehci_qtd_alloc@#+0x17 stack: 0x5a3432352e32353a
cpu17:33399)0x439113b9b990:[0x41802ccf8fb4]qh_urb_transaction@#+0x318 stack: 0xffffffff21fa08d8
cpu17:33399)0x439113b9ba10:[0x41802ccff1f2]ehci_urb_enqueue@#+0x5e stack: 0x0
cpu17:33399)0x439113b9bac0:[0x41802ccdc151][email protected]#9.2.3.0+0xf9 stack: 0x202
cpu17:33399)0x439113b9bbb0:[0x41802cce8d41][email protected]#9.2.3.0+0xfd stack: 0x43050f664ac0
cpu17:33399)0x439113b9bbe0:[0x41802cce47fd][email protected]#9.2.3.0+0x71 stack: 0x8
cpu17:33399)0x439113b9bc90:[0x41802cce4a5d][email protected]#9.2.3.0+0xed stack: 0x43050f660940
cpu17:33399)0x439113b9bd00:[0x41802ccdeaf1][email protected]#9.2.3.0+0x7d stack: 0x4305000003e8
cpu17:33399)0x439113b9bd80:[0x41802cce3ad3][email protected]#9.2.3.0+0xe87 stack: 0x0
cpu17:33399)0x439113b9beb0:[0x41802cb66e00][email protected]#9.2+0x158 stack: 0x0
cpu17:33399)0x439113b9bf40:[0x41802cb6450f][email protected]#9.2+0x8f stack: 0x0
cpu17:33399)0x439113b9bf90:[0x41802c49c97b]vmkWorldFunc@vmkernel#nover+0x3b stack: 0x41802c49c976
cpu17:33399)0x439113b9bfd0:[0x41802c617d9e]CpuSched_StartWorld@vmkernel#nover+0xa2 stack: 0x0
cpu17:33399)base fs=0x0 gs=0x418044400000 Kgs=0x0
Cause:- Memory corruption caused by usb devices results in crash on USB disconnect.
Solution:- This USB related PSOD is more likely a Avocent Virtual Hub/Keyboard/Mouse issue. Updating the firmware may resolve the issue.