Changes between Initial Version and Version 1 of Ticket #344, comment 1
- Timestamp:
- 01/11/2025 04:35:45 PM (19 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #344, comment 1
initial v1 10 10 11 11 The second CPU 1 fault on the third line would only happen if the cam_clear loop timed out and reissued the connects; the lack of CPUs 2 and 3 messages suggests that they did not get a chance to respond in time. 12 13 The source of the connects could only have been cam_clear since the history debugger log showed that all of the processors were involved in cam_clear or wired_fim connect handler.
