On 2025年8月18日 14:57:41 +0200, Niklas Neronin wrote: > One of the reasons for a Set TR Deq Context State Error, is that the Slot > state is not Default, Configured, or Addressed. This leaves it 2 options; > Enabled and Disabled. If the slot state was Disabled, HW would have > returned a Slot Not Enabled Error, which only leaves Enabled Slot state. > > Devices with a slot state of Enabled must have previously been in a > Disabled slot state. Both Enabled and Disabled slot states have the > Doorbell register disabled, meaning they do not receive or handle TDs. > Consequently, all cancelled TDs are released. Is there any realistic chance that the virtual endpoint to which those TDs belonged still exists after a slot disable/enable cycle? Disabling a slot normally frees the virtual device with all virt eps. This is true even in exotic cases like using a disable/enable cycle on Etron HCs as a substitute for Reset Device command. In more typical cases, the newly enabled slot is a different device.