lpfc_kill_board(9)
π NAME π
okay bestie, welcome to the lpfc_kill_board(9) page β yes, that's the manual name, and we're chilling in the Kernel API Manual section. This one is literally about prepping a mailbox command for killing board β¨
lpfc_kill_board β prepare a mailbox command for killing board π«Ά
β¨ SYNOPSIS β¨
void lpfc_kill_board (struct lpfc_hba * phba , LPFC_MBOXQ_t * pmb );
that's the whole signature, no cap π
πΈ ARGUMENTS πΈ
phbaβ pointer to thelpfc_hbadata structure. the hba data situation, iykyk.pmbβ pointer to the driver internal queue element for the mailbox command. that's the queue element the driver keeps internally, specifically for a mailbox command π
π¦ DESCRIPTION π¦
okay so here's the vibe: the kill board mailbox command is used to tell firmware to perform a graceful shutdown of a channel on a specified board to prepare for reset. iconic tidy-up energy, honestly.
when the kill board mailbox command is received, the ER3 bit is set to 1 in the Host Status register, and the ER Attention bit is set to 1 in the Host Attention register of the HBA function that received the kill board command. yes, that exact HBA function β it's giving targeted π
this routine prepares the mailbox command for killing the board in preparation for a graceful shutdown. so lpfc_kill_board is literally doing the pre-game for a graceful shutdown, not chaos π
π₯ SEE ALSO π₯
Kernel file ./drivers/scsi/lpfc/lpfc_mbox.c β and bestie, the cross-ref list is LONG, so here's every single one, no skipping:
lpfc_mbox_rsrc_prep(9)lpfc_mbox_rsrc_cleanup(9)lpfc_dump_static_vport(9)lpfc_down_link(9)lpfc_dump_mem(9)lpfc_dump_wakeup_param(9)lpfc_read_nv(9)lpfc_config_async(9)lpfc_heart_beat(9)lpfc_read_topology(9)lpfc_clear_la(9)lpfc_config_link(9)lpfc_config_msi(9)lpfc_init_link(9)lpfc_read_sparam(9)lpfc_unreg_did(9)lpfc_read_config(9)lpfc_read_lnk_stat(9)lpfc_reg_rpi(9)lpfc_unreg_login(9)lpfc_sli4_unreg_all_rpis(9)lpfc_reg_vpi(9)lpfc_unreg_vpi(9)lpfc_config_pcb_setup(9)lpfc_read_rev(9)lpfc_build_hbq_profile2(9)lpfc_build_hbq_profile3(9)lpfc_build_hbq_profile5(9)lpfc_config_hbq(9)lpfc_config_ring(9)lpfc_config_port(9)lpfc_mbox_put(9)lpfc_mbox_get(9)__lpfc_mbox_cmpl_put(9)lpfc_mbox_cmpl_put(9)lpfc_mbox_cmd_check(9)lpfc_mbox_dev_check(9)lpfc_mbox_tmo_val(9)lpfc_sli4_mbx_sge_set(9)lpfc_sli4_mbx_sge_get(9)lpfc_sli4_mbox_cmd_free(9)lpfc_sli4_config(9)lpfc_sli4_mbox_rsrc_extent(9)lpfc_sli_config_mbox_subsys_get(9)lpfc_sli_config_mbox_opcode_get(9)lpfc_sli4_mbx_read_fcf_rec(9)lpfc_request_features(9)lpfc_init_vfi(9)lpfc_reg_vfi(9)lpfc_init_vpi(9)lpfc_unreg_vfi(9)lpfc_sli4_dump_cfg_rg23(9)lpfc_reg_fcfi(9)lpfc_reg_fcfi_mrq(9)lpfc_unreg_fcfi(9)lpfc_resume_rpi(9)
mwah π this page comes from ./drivers/scsi/lpfc, dated October 2026, and yes it's the lpfc_kill_board(9) page β periodt π
π¦ 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