Page MenuHomeFreeBSD

mpi3mr: Consider Diagnostic Fault Reset Success Beyond 0xF000 fault Code
ClosedPublic

Authored by chandrakanth.patil_broadcom.com on Mar 19 2024, 11:36 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sep 30 2024, 1:36 PM
Unknown Object (File)
Sep 30 2024, 1:35 PM
Unknown Object (File)
Sep 30 2024, 11:41 AM
Unknown Object (File)
Sep 28 2024, 2:37 AM
Unknown Object (File)
Sep 22 2024, 7:32 PM
Unknown Object (File)
Sep 22 2024, 4:06 PM
Unknown Object (File)
Aug 29 2024, 5:41 PM
Unknown Object (File)
Aug 21 2024, 11:36 PM
Subscribers
None

Details

Summary

Accept any fault as successful for diagnostic fault reset, not just the 0xF000
code. print fault information and return.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Mar 21 2024, 8:16 AM

I don't have any chip documentation to know what is right here, so just wonder if unconditional printing a bunch of raw hex numbers is expected here. It feels mpi3mr_print_fault_info() is another candidate for mpi3mr_dprint().

In D44426#1013880, @mav wrote:

I don't have any chip documentation to know what is right here, so just wonder if unconditional printing a bunch of raw hex numbers is expected here. It feels mpi3mr_print_fault_info() is another candidate for mpi3mr_dprint().

Agreed. There are so many other places where we need to take care of this kind of printing so we are preparing the debug improvement patch and will submit it soon which will cover this as well.