mpi3mr_soft_reset_handler(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

okay so bestie, this is a page from the Kernel API Manual for mpi3mr_soft_reset_handler(9), and the function is literally mpi3mr_soft_reset_handler β€” Reset the controller ✨. That's the whole main-character job, no cap.

πŸŽ€ SYNOPSIS πŸŽ€

int mpi3mr_soft_reset_handler (struct mpi3mr_ioc *mrioc , u16
       reset_reason , u8 snapdump );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • mrioc β€” Adapter instance reference, aka the controller's contact card πŸ’–
  • reset_reason β€” Reset reason code, the why-are-we-resetting receipts πŸ‘€
  • snapdump β€” Flag to generate snapdump in firmware or not 🫢

🌸 DESCRIPTION 🌸

This is the handler for recovering the controller by issuing a soft reset or diag fault reset. The way that this is a blocking function is lowkey important: when one reset is executed, if any other resets come through, they will be blocked. All BSG requests will be blocked during the reset too. If controller reset is successful, then the controller will be reinitialized; otherwise the controller will be marked as not recoverable 😭. Periodt.

If the snapdump bit is set, the controller is issued with a diag fault reset so that the firmware can create a snap dump, and after that the firmware will result in an F000 fault, and the driver will issue a soft reset to recover from that 🫢.

πŸ”₯ RETURN πŸ”₯

0 on success, non-zero on failure. That's it, bestie πŸ’….

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/scsi/mpi3mr/mpi3mr_fw.c is the home base, and here's the whole friend group of refs β€” every single one, fr fr:


Catch you later, bestie β€” this page is signed off from the ./drivers/scsi/mpi3mr source and dated October 2026 πŸ’–βœ¨πŸ«Ά

πŸ“¦ where this page comes from