Data Processing System with Tag-Based Queue Management

2. The system of claim 1, wherein the fault is when (i) the current unique tag value is not found and the controller determines the transaction was executed in an unexpected order.

3. The system of claim 1, wherein the fault is when (i) the current unique tag value is not found and the controller determines the transaction was not deallocated.

4. The system of claim 1, wherein the fault is when (ii) the transactions timeout after a predetermined number of cycles the controller reports a tag timeout.

5. The system of claim 1, wherein the unique tag value comprises a data value.

7. The system of claim 6, wherein the controller comprises the transaction scheduler configured to process transactions, a tag control circuit coupled to the transaction scheduler, a tag generator coupled to the tag control circuit, and a tag checker coupled to the tag control circuit.

8. The system of claim 6, wherein the unique tag value comprises a data value.

9. The system of claim 6, wherein the fault further comprises an improper deallocation of the transaction.

11. The system of claim 10, wherein the fault i) a mismatch in a unique tag value associated with a transaction and a current tag value of a current transaction due to a missing tag value.

12. The system of claim 10, wherein the fault ii) a timed out transaction due to an improper deallocation of a transaction.

13. The system of claim 12, wherein the timed out transaction is after a predetermined number of clock cycles.

14. The system of claim 10, wherein the fault iii) a transaction that is not associated with a unique tag value due to a failure to deallocate the transaction.

16. The method of claim 15, further comprising generating an interrupt signal corresponding to the fault, and responsive to the interrupt signal at a controller, invoking a service routine to analyze the fault.

17. The method of claim 15, further comprising based upon the fault not corresponding to a hard error, resetting a core domain and allowing other portions of the data processing system continue normal operation during reset of the core domain.

18. The method of claim of claim 15, further comprising using an ECC process to check a correctness of a group of data bits in the input data.

19. The method of claim of claim 15, further comprising using a lockstep process to check a correctness of a group of data bits in the input data.