ENUM IWL_FW_DBG_TRIGGER(9)
β¨ 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
- 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