Lines Matching refs:errors
1176 * potential syndrome 71 generating errors.
1182 * errors.
1249 * Check the logout areas of all other cpus for unlogged errors.
1463 * or disrupting errors have happened. We do this because if a
1483 * Panic here if aflt->flt_panic has been set. Enqueued errors will
1556 * are no valid errors in the AFSR, we'll assume they've
1607 * Disrupting errors controlled by NCEEN: EDU:ST, WDU, CPU, IVU
1608 * Disrupting errors controlled by CEEN: CE, EMC, EDC, WDC, CPC, IVC
1686 * If this trap is a result of one of the errors not masked
1702 * We re-enable CEEN (if required) and check if any disrupting errors
1717 * Panic here if aflt->flt_panic has been set. Enqueued errors will
1727 * Deferred errors controlled by NCEEN: UE, EMU, EDU:BLD, L3_EDU:BLD, TO, BERR
1729 * Cheetah+: No additional errors handled.
1854 * for peeks and caut_gets errors are expected
1912 * Log any errors that occurred
1935 * IO errors that may have resulted in this trap.
1944 * fatal errors. Attempts to do diagnostic read on caches may
1945 * introduce more errors (especially when the module is bad).
1949 * Ask our bus nexus friends if they have any fatal errors. If
1958 * can check for copyback errors.
1973 * IO errors that may have resulted in this trap.
1982 * fatal errors. Attempts to do diagnostic read on caches may
1983 * introduce more errors (especially when the module is bad).
1988 * errors. If so, they will log appropriate error messages.
1996 * for copyback errors.
2013 * or disrupting errors have happened. We do this because if a
2026 * Check for secondary errors, and avoid panicking if we
2039 * Panic here if aflt->flt_panic has been set. Enqueued errors will
2072 * Handling of data and instruction parity errors (traps 0x71, 0x72).
2074 * For Panther, P$ data parity errors during floating point load hits
2078 * AFSR/AFAR are not set for parity errors, only TPC (a virtual address)
2100 * For icache parity errors the fault address is the trap PC.
2101 * For dcache/pcache parity errors the instruction would have to
2185 * For panther we also need to check the P$ for parity errors.
2233 * As far as clearing P$ parity errors, it is enough to
2261 * Panic here if aflt->flt_panic has been set. Enqueued errors will
2339 * since P$ data parity errors are reported in Panther using
2383 uint64_t errors;
2427 * scrubber. However, none of those errors should occur
2472 if (page_retire_check(aflt->flt_addr, &errors) == EINVAL) {
2476 if (errors != PR_OK) {
2597 * E$, and MTag errors. Historically this entry point was used to log bits of
2805 * Scrub memory, then check AFSR for errors. The AFAR we scrub may
3178 * any errors and return null disposition info. If the original detecting
3347 * We route all errors through a single switch statement.
3694 * Historical function only called for SBus errors in debugging.
3703 * any of the AFSR's sticky errors are detected. If a non-null pointer to
3736 * has already filled flt_synd. For errors trapped by CPU we only fill
3754 * Snapshot the AFSR and AFAR and clear any errors
3777 * logout areas for any unlogged errors.
3791 * Enable errors.
4248 * examine the entire Pcache to check for any parity errors.
4679 * Memory errors, do unum lookup
4790 * errors, so return 0.
5045 * Queue expected errors, error bit and fault type must match
5054 * For FRC/FRU errors on Serrano the afar2 captures
5081 * Queue unexpected errors, error bit only match.
5088 * For FRC/FRU errors on Serrano the afar2 captures
5206 * "Possible persistent" errors to which we have applied a valid
6082 * When the CPU gets a disrupting trap for any of the errors
6095 * spend all its time logging CE errors.
6173 * The memscrubber will also use this routine to clear any errors
6209 * If no CEEN errors have occurred during the timeout
6341 * check if we caused any errors during cleanup
6351 * Log/clear CEEN-controlled disrupting errors
6402 * The trap handler does it for CEEN enabled errors
6494 * If we got multiple errors, no point in trying
6505 * is not set when multiple correctable errors of the same
6506 * type occur, so we might have multiple CPC or EDC errors,
7123 * Return 1 if the errors in ch_flt's AFSR are secondary errors caused by
7124 * the errors in the original AFSR, 0 otherwise.
7135 * When clear_errors() is called, it will determine that secondary errors have
7141 * errors occur, we return 0.
7159 * (multiple errors are also OK)
7164 * (multiple errors are also OK)
7184 * Check the secondary errors were exclusively an EDU and/or WDU.
7190 * Check the AFAR of the original error and secondary errors
7205 * is checked for any valid errors. If found, the error type is
7206 * returned. If not found, the flt_type is checked for L1$ parity errors.
7214 * Currently, logging errors to the SC is not supported on Jalapeno