ENUM IWL_FW_DBG_TRIGGER(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ enum iwl_fw_dbg_trigger ✨

okay bestie, welcome to the enum iwl_fw_dbg_trigger(9) page from the Kernel API Manual πŸ’– this is literally the master list of triggers available β€” like, all the reasons the iwlwifi firmware-and-driver situation might go "hey, dump the logs, something's happening" πŸŽ€


🌸 SYNOPSIS 🌸

enum iwl_fw_dbg_trigger {
    FW_DBG_TRIGGER_INVALID ,
    FW_DBG_TRIGGER_USER ,
    FW_DBG_TRIGGER_FW_ASSERT ,
    FW_DBG_TRIGGER_MISSED_BEACONS ,
    FW_DBG_TRIGGER_CHANNEL_SWITCH ,
    FW_DBG_TRIGGER_FW_NOTIF ,
    FW_DBG_TRIGGER_MLME ,
    FW_DBG_TRIGGER_STATS ,
    FW_DBG_TRIGGER_RSSI ,
    FW_DBG_TRIGGER_TXQ_TIMERS ,
    FW_DBG_TRIGGER_TIME_EVENT ,
    FW_DBG_TRIGGER_BA ,
    FW_DBG_TRIGGER_TX_LATENCY ,
    FW_DBG_TRIGGER_TDLS ,
    FW_DBG_TRIGGER_TX_STATUS ,
    FW_DBG_TRIGGER_ALIVE_TIMEOUT ,
    FW_DBG_TRIGGER_DRIVER ,
    FW_DBG_TRIGGER_MAX

};

that's the whole lineup, no cap πŸ‘‘


πŸ’… Constants πŸ’…

okay so here's every single one of them, one by one, no skipping fr fr 🫢

  • FW_DBG_TRIGGER_INVALID β€” the invalid trigger value πŸ™ˆ literally the "this means nothing" placeholder.
  • FW_DBG_TRIGGER_USER β€” trigger log collection by user. ⭐ careful bestie, this one's special: it should not be defined as a trigger to the driver, but instead it's a value the driver should set to indicate that the trigger was initiated by the user. iykyk πŸ’–
  • FW_DBG_TRIGGER_FW_ASSERT β€” trigger log collection when the firmware asserts πŸ’€ (yes, the dramatic one).
  • FW_DBG_TRIGGER_MISSED_BEACONS β€” trigger log collection when beacons are missed. πŸ¦‹
  • FW_DBG_TRIGGER_CHANNEL_SWITCH β€” trigger log collection upon channel switch. πŸ”₯
  • FW_DBG_TRIGGER_FW_NOTIF β€” trigger log collection when the firmware sends a command response or a notification. ✨
  • FW_DBG_TRIGGER_MLME β€” trigger log collection upon MLME event. 🌸
  • FW_DBG_TRIGGER_STATS β€” trigger log collection upon statistics threshold. πŸ“
  • FW_DBG_TRIGGER_RSSI β€” trigger log collection when the rssi of the beacon goes below a threshold. 😭 signal said bye.
  • FW_DBG_TRIGGER_TXQ_TIMERS β€” configures the timers for the Tx queue hang detection. ⏱️
  • FW_DBG_TRIGGER_TIME_EVENT β€” trigger log collection upon time events related events. πŸŽ€
  • FW_DBG_TRIGGER_BA β€” trigger log collection upon BlockAck related events. 🌈
  • FW_DBG_TRIGGER_TX_LATENCY β€” trigger log collection when the tx latency goes above a threshold. πŸ”₯ slow is a vibe, just not this one.
  • FW_DBG_TRIGGER_TDLS β€” trigger log collection upon TDLS related events. 🧚
  • FW_DBG_TRIGGER_TX_STATUS β€” trigger log collection upon tx status when the firmware sends a tx reply. πŸ’œ
  • FW_DBG_TRIGGER_ALIVE_TIMEOUT β€” trigger log collection if alive flow timeouts πŸ’€
  • FW_DBG_TRIGGER_DRIVER β€” trigger log collection upon a flow failure in the driver. πŸ™ˆ
  • FW_DBG_TRIGGER_MAX β€” beyond triggers, number for sizing arrays etc. πŸ‘‘ the sentinel, the final boss, the "count how many we got" girlie.
quick note bestie: FW_DBG_TRIGGER_USER is not a real trigger handed to the driver β€” it's the value the driver sets to say "a human did this." don't mix that up πŸ’…

🌟 SEE ALSO 🌟

all the siblings live in Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/error-dump.h, and the whole friend group is:

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_info(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), struct iwl_fw_error_dump_trigger_desc(9)

go read those next, you're gonna slay the whole error-dump situation 🫢✨


πŸ’– that's the page, bestie πŸ’– this cutie came out of ./drivers/net/wireless/intel/i... and it's dated October 2026 β€” the version/date girls said "see you then" πŸŒΈπŸ¦‹ mwah, go trigger some logs responsibly πŸ’…

πŸ“¦ where this page comes from