STRUCT IWL_FW_ERROR_DUMP_INFO(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

struct iwl_fw_error_dump_info β€” the lil' info packet about your device and firmware, bestie. it's from the Kernel API Manual, and it's giving "who am I, what am I running, and what went wrong" energy ✨


🌸 SYNOPSIS 🌸

okay so here's the shape of it, no cap:

struct iwl_fw_error_dump_info {
    __le32 hw_type;
    __le32 hw_step;
    u8 fw_human_readable[FW_VER_HUMAN_READABLE_SZ];
    u8 dev_human_readable[64];
    u8 bus_human_readable[8];
    u8 num_of_lmacs;
    __le32 umac_err_id;
    __le32 lmac_err_id[MAX_NUM_LMAC];
};

πŸŽ€ Members πŸŽ€

each field is a whole vibe, let me introduce you 🫢

  • hw_type β€” the type of the device. literally just: what hardware is this πŸ’…
  • hw_step β€” the step of the device. the lil' revision detail, iykyk
  • fw_human_readable β€” human readable FW version. the firmware version but make it readable πŸŽ€
  • dev_human_readable β€” name of the device. so it can introduce itself
  • bus_human_readable β€” name of the bus used. yes the bus, not the vehicle 🚌
  • num_of_lmacs β€” the number of lmacs. that's the count, periodt
  • umac_err_id β€” the umac error_id/rt_status that triggered the latest dump. careful bestie: if the dump collection was not initiated by an assert, the value is 0 πŸ’€
  • lmac_err_id β€” the lmac 0/1 error_id/rt_status that triggered the latest dump. same deal fr fr: if the dump collection was not initiated by an assert, the value is 0 πŸ’€
lowkey the whole point is: these two err ids are only ~spicy~ when an assert kicked off the dump. otherwise they're just chillin' at 0. πŸ™ˆ

🌈 SEE ALSO 🌈

the whole friend group 🫢 everything below lives in the kernel file ./drivers/net/wireless/intel/iwlwifi/fw/error-dump.h, and honestly the lore is deep:

  • enum iwl_fw_error_dump_type(9)
  • struct iwl_fw_error_dump_data(9)
  • struct iwl_dump_file_name_info(9)
  • struct iwl_fw_error_dump_file(9)
  • struct iwl_fw_error_dump_txcmd(9)
  • struct iwl_fw_error_dump_fifo(9)
  • struct iwl_fw_error_dump_fw_mon(9)
  • struct iwl_fw_error_dump_smem_cfg(9)
  • struct iwl_fw_error_dump_prph(9)
  • struct iwl_fw_error_dump_mem(9)
  • struct iwl_fw_ini_error_dump_data(9)
  • struct iwl_fw_ini_dump_file_hdr(9)
  • struct iwl_fw_ini_fifo_hdr(9)
  • struct iwl_fw_ini_error_dump_range(9)
  • struct iwl_fw_ini_error_dump_header(9)
  • struct iwl_fw_ini_error_dump(9)
  • struct iwl_fw_ini_error_dump_register(9)
  • struct iwl_fw_ini_dump_cfg_name(9)
  • struct iwl_fw_ini_err_table_dump(9)
  • struct iwl_fw_error_dump_rb(9)
  • struct iwl_fw_ini_monitor_dump(9)
  • struct iwl_fw_ini_special_device_memory(9)
  • struct iwl_fw_error_dump_paging(9)
  • iwl_fw_error_next_data(9)
  • enum iwl_fw_dbg_trigger(9)
  • struct iwl_fw_error_dump_trigger_desc(9)

and that's the tea πŸ“ this page came from the Kernel API Manual, pulled out of ./drivers/net/wireless/intel/i... and dated October 2026 β€” so if you see struct iwl_...or_dump_info(9) at the bottom, that's just the footer being iconic and mysterious πŸ’…βœ¨

πŸ“¦ where this page comes from