en:users:drivers:iwlwifi:debugging
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
en:users:drivers:iwlwifi:debugging [2019/02/06 12:38] Emmanuel Grumbach |
en:users:drivers:iwlwifi:debugging [2019/10/10 05:44] Luca Coelho [Prints] updated line number of debug bitmap |
||
|---|---|---|---|
| Line 25: | Line 25: | ||
| ==== Prints ==== | ==== Prints ==== | ||
| - | The simplest way to provide minimal output is to dump your kernel log: dmesg. Sometimes we will ask for logs from the supplicant too - they typically land in syslog. iwlwifi can print more data to the kernel log if asked to: this is controlled by the debug module parameter. This is a [[https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/wireless/intel/iwlwifi/iwl-debug.h#n143|bitmap]]. To see more debug prints, [[https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/wireless/intel/iwlwifi/Kconfig#n105|CONFIG_IWLWIFI_DEBUG]] must be enabled. | + | The simplest way to provide minimal output is to dump your kernel log: dmesg. Sometimes we will ask for logs from the supplicant too - they typically land in syslog. iwlwifi can print more data to the kernel log if asked to: this is controlled by the debug module parameter. This is a [[https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/wireless/intel/iwlwifi/iwl-debug.h#n129|bitmap]]. To see more debug prints, [[https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/wireless/intel/iwlwifi/Kconfig#n105|CONFIG_IWLWIFI_DEBUG]] must be enabled. |
| Please don't add debug level unless instructed to do so. Adding more prints typically adds useless information. | Please don't add debug level unless instructed to do so. Adding more prints typically adds useless information. | ||
| Line 101: | Line 101: | ||
| This way, each time a dump is created it will automatically land on your file system. Remember to make the /sbin/iwlfwdump.sh file executable (i.e. ''chmod a+x /sbin/iwlfwdump.sh''), so that the udev rule can execute it, otherwise it won't work. | This way, each time a dump is created it will automatically land on your file system. Remember to make the /sbin/iwlfwdump.sh file executable (i.e. ''chmod a+x /sbin/iwlfwdump.sh''), so that the udev rule can execute it, otherwise it won't work. | ||
| - | To debug the firmware you'll typically need a customized version of it. This customization depends on the bug you are facing. | ||
| Starting from 4.1, we can trigger firmware dumps when issues occur (e.g. when the association fails) this again requires a customized firmware. In that case, the developer working with you will let you know and you won't have to trigger the dump yourself using fw_dbg_collect debugfs hook. | Starting from 4.1, we can trigger firmware dumps when issues occur (e.g. when the association fails) this again requires a customized firmware. In that case, the developer working with you will let you know and you won't have to trigger the dump yourself using fw_dbg_collect debugfs hook. | ||
| Line 114: | Line 113: | ||
| In this case, please copy the full dmesg output since there may be data before and after this message that can be helpful. | In this case, please copy the full dmesg output since there may be data before and after this message that can be helpful. | ||
| - | In case of a firmware crash or queues being stuck, a dump will be automatically created. If you have the udev rule in place, you'll see the dump on your file system. No customization needed in that case, the dump from a regular firmware will already include valuable data, but the firmware team is likely to ask reproduction with a customized version. | + | In case of a firmware crash or queues being stuck, a dump will be automatically created. If you have the udev rule in place, you'll see the dump on your file system. No customization needed in that case, the dump from a regular firmware will already include valuable data, but we usually need more information than the data provided by a release version of the firmware. When you report a bug, please use a debug firmware |
| + | from the list below. This will allow to include more data in the dump at the cost of extra PCI transactions: | ||
| + | |||
| + | {{en:users:drivers:iwlwifi:iwlwifi-3160-17.ucode.gz|debug firmware version for 3160}} | ||
| + | |||
| + | {{en:users:drivers:iwlwifi:iwlwifi-7260-17.ucode.gz|debug firmware version for 7260}} | ||
| + | |||
| + | {{en:users:drivers:iwlwifi:iwlwifi-7265-17.ucode.gz|debug firmware version for 7265}} | ||
| + | |||
| + | {{en:users:drivers:iwlwifi:iwlwifi-7265d-29.ucode.gz|debug firmware version for 7265D}} | ||
| + | |||
| + | {{en:users:drivers:iwlwifi:iwlwifi-3168-29.ucode.gz|debug firmware version for 3168}} | ||
| + | |||
| + | {{en:users:drivers:iwlwifi:iwlwifi-8000C-36.ucode.gz|debug firmware version for 8260}} | ||
| + | |||
| + | {{en:users:drivers:iwlwifi:iwlwifi-8265-36.ucode.gz|debug firmware version for 8265}} | ||
| + | |||
| + | {{en:users:drivers:iwlwifi:iwlwifi-9000-pu-b0-jf-b0-43.ucode.gz|debug firmware version for 9000}} | ||
| + | |||
| + | {{en:users:drivers:iwlwifi:iwlwifi-9260-th-b0-jf-b0-43.ucode.gz|debug firmware version for 9260}} | ||
| ==== Privacy aspects ==== | ==== Privacy aspects ==== | ||
en/users/drivers/iwlwifi/debugging.txt · Last modified: 2022/05/30 08:07 by Johannes Berg
Page Tools
