mpi3mr_check_rh_fault_ioc(9)
β¨ NAME β¨
mpi3mr_check_rh_fault_ioc β check reset history and fault controller π
Okay bestie, welcome to the mpi3mr_check_rh_fault_ioc(9) page. Itβs giving βsmall function, very specific job,β and honestly? We respect it. π«Ά
π οΈ SYNOPSIS π οΈ
void mpi3mr_check_rh_fault_ioc (struct mpi3mr_ioc *mrioc , u32
reason_code );
π ARGUMENTS π
mriocβ Adapter instance reference. This is your controllerβs wholestruct mpi3mr_ioc *vibe, basically the main character. πreason_codeβ reason code for the fault. This is theu32that tells everyone why weβre faulting. π
π DESCRIPTION π
So this routine saves a snapdump and faults the controller with the given reason_code if itβs not already in the fault state or not already being asynchronously reset. Itβs giving reset-history realness and weβre obsessed. β¨
Itβs used for initialization-time faults/resets/timeout, because in those cases you donβt need to immediately invoke a soft reset. Periodt. π
π RETURN π
None. Itβs a void function, so nothing comes back. Literally no return-value drama. π
π SEE ALSO π
Kernel file: ./drivers/scsi/mpi3mr/mpi3mr_fw.c
The whole friend group pulls up too β no cap:
mpi3mr_get_reply_desc(9),mpi3mr_process_op_reply_q(9),mpi3mr_blk_mq_poll(9),mpi3mr_isr_poll(9)mpi3mr_request_irq(9),mpi3mr_setup_isr(9),mpi3mr_reset_rc_name(9),mpi3mr_reset_type_name(9)mpi3mr_is_fault_recoverable(9),mpi3mr_print_fault_info(9),mpi3mr_save_fault_info(9),mpi3mr_get_iocstate(9)mpi3mr_free_ioctl_dma_memory(9),mpi3mr_alloc_ioctl_dma_memory(9),mpi3mr_fault_uevent_emit(9),mpi3mr_clear_reset_history(9)mpi3mr_issue_and_process_mur(9),mpi3mr_revalidate_factsdata(9),mpi3mr_bring_ioc_ready(9),mpi3mr_soft_reset_success(9)mpi3mr_diagfault_success(9),mpi3mr_set_diagsave(9),mpi3mr_issue_reset(9),mpi3mr_admin_request_post(9)mpi3mr_free_op_req_q_segments(9),mpi3mr_free_op_reply_q_segments(9),mpi3mr_delete_op_reply_q(9),mpi3mr_alloc_op_reply_q_segments(9)mpi3mr_alloc_op_req_q_segments(9),mpi3mr_create_op_reply_q(9),mpi3mr_create_op_req_q(9),mpi3mr_create_op_queues(9)mpi3mr_op_request_post(9),mpi3mr_sync_timestamp(9),mpi3mr_print_pkg_ver(9),mpi3mr_watchdog_work(9)mpi3mr_start_watchdog(9),mpi3mr_stop_watchdog(9),mpi3mr_setup_admin_qpair(9),mpi3mr_issue_iocfacts(9)mpi3mr_check_reset_dma_mask(9),mpi3mr_process_factsdata(9),mpi3mr_alloc_reply_sense_bufs(9),mpimr_initialize_reply_sbuf_queues(9)mpi3mr_issue_iocinit(9),mpi3mr_unmask_events(9),mpi3mr_issue_event_notification(9),mpi3mr_process_event_ack(9)mpi3mr_alloc_chain_bufs(9),mpi3mr_port_enable_complete(9),mpi3mr_issue_port_enable(9),mpi3mr_repost_diag_bufs(9)mpi3mr_read_tsu_interval(9),mpi3mr_print_ioc_info(9),mpi3mr_cleanup_resources(9),mpi3mr_setup_resources(9)mpi3mr_enable_events(9),mpi3mr_init_ioc(9),mpi3mr_reinit_ioc(9),mpi3mr_memset_op_reply_q_buffers(9)mpi3mr_memset_op_req_q_buffers(9),mpi3mr_memset_buffers(9),mpi3mr_free_mem(9),mpi3mr_issue_ioc_shutdown(9)mpi3mr_cleanup_ioc(9),mpi3mr_drv_cmd_comp_reset(9),mpi3mr_flush_drv_cmds(9),mpi3mr_pel_wait_post(9)mpi3mr_pel_get_seqnum_post(9),mpi3mr_pel_wait_complete(9),mpi3mr_pel_get_seqnum_complete(9),mpi3mr_check_op_admin_proc(9)mpi3mr_soft_reset_handler(9),mpi3mr_post_cfg_req(9),mpi3mr_process_cfg_req(9),mpi3mr_cfg_get_dev_pg0(9)mpi3mr_cfg_get_sas_phy_pg0(9),mpi3mr_cfg_get_sas_phy_pg1(9),mpi3mr_cfg_get_sas_exp_pg0(9),mpi3mr_cfg_get_sas_exp_pg1(9)mpi3mr_cfg_get_enclosure_pg0(9),mpi3mr_cfg_get_sas_io_unit_pg0(9),mpi3mr_cfg_get_sas_io_unit_pg1(9),mpi3mr_cfg_set_sas_io_unit_pg1(9)mpi3mr_cfg_get_driver_pg1(9),mpi3mr_cfg_get_driver_pg2(9)
Source/version vibes: ./drivers/scsi/mpi3mr Β· date: October 2026 Β· page tag: mpi3mr_check_rh_fault_ioc(9). Go fault that controller responsibly, bestie πβ¨π¦
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms