Searched refs:diagnose (Results 1 – 10 of 10) sorted by relevance
61 * The maximum number of pages we will diagnose as faulty on any one108 * | (CSPATH) for the same chip number, diagnose to an fault event |113 * | continuing to diagnose endless page faults from a dimm with |
38 * we diagnose for page faults, to record the physical address of the faulting105 * trips we diagnose a fault.memory.page so that the response agent can108 * diagnose a fault.memory.dimm_sb against the containing dimm.129 * SERD engines which diagnose fault.memory.page_sb if they trip.132 * into additional per-rank SERD engines which diagnose fault.memory.page_ck169 * Once we have faulted the rank we will continue to diagnose any further page213 * The maximum number of single-correctable-unit page faults we will diagnose241 * ereport which we diagnose to a fault if the threshold has been reached.
141 * Instead we will diagnose a distinct fault for each possible cache level,208 * Discards - not enough info to diagnose.
51 * we diagnose it to an upset and decalre a fault when the SERD engine129 * Instead we will diagnose a distinct fault for each possible cache level,208 * we diagnose for page faults, to record the physical address of the faulting
56 * trigger fault.io.n2.niu-xfp. Based on the following rules, the diagnose
37 msgstr "illumos will attempt to save and diagnose the error telemetry"
6608 diagnose
6606 diagnose
1589 07-11-05 A bug in which printf %d "'AB" did not diagnose unconverted characters
13668 diagnose scoping issues. The old scope name as well as the new