en:users:drivers:ath10k:debug
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:users:drivers:ath10k:debug [2015/04/24 14:15] Kalle Valo bitrates: move the description before the example |
en:users:drivers:ath10k:debug [2017/03/29 14:32] (current) Kalle Valo [Firmware crash dump file] useless use of cat and add a log message |
||
|---|---|---|---|
| Line 26: | Line 26: | ||
| ATH10K_DBG_BMI = 0x00000400, | ATH10K_DBG_BMI = 0x00000400, | ||
| ATH10K_DBG_REGULATORY = 0x00000800, | ATH10K_DBG_REGULATORY = 0x00000800, | ||
| + | ATH10K_DBG_TESTMODE = 0x00001000, | ||
| + | ATH10K_DBG_WMI_PRINT = 0x00002000, | ||
| + | ATH10K_DBG_PCI_PS = 0x00004000, | ||
| + | ATH10K_DBG_AHB = 0x00008000, | ||
| ATH10K_DBG_ANY = 0xffffffff, | ATH10K_DBG_ANY = 0xffffffff, | ||
| };</code> | };</code> | ||
| Line 182: | Line 186: | ||
| <code>iw wlan0 set bitrates legacy-5 ht-mcs-5 vht-mcs-5 2:9 force-sgi</code> | <code>iw wlan0 set bitrates legacy-5 ht-mcs-5 vht-mcs-5 2:9 force-sgi</code> | ||
| + | |||
| + | Few more complicated examples, only supported since 4.2 kernel: | ||
| + | |||
| + | <code> | ||
| + | iw wlan0 set bitrates legacy-5 6 12 ht-mcs-5 1 2 3 | ||
| + | iw wlan0 set bitrates legacy-5 ht-mcs-5 7 8 9 | ||
| + | iw wlan0 set bitrates legacy-5 24 ht-mcs-5 vht-mcs-5 1:0-9 | ||
| + | </code> | ||
| ==== Simulating firmware crashes ==== | ==== Simulating firmware crashes ==== | ||
| Line 198: | Line 210: | ||
| `assert` - this will send special illegal parameter to firmware to cause assert failure and crash. | `assert` - this will send special illegal parameter to firmware to cause assert failure and crash. | ||
| `hw-restart` - this will simply queue hw restart without fw/hw actually crashing.</code> | `hw-restart` - this will simply queue hw restart without fw/hw actually crashing.</code> | ||
| + | |||
| + | ==== Firmware crash dump file ==== | ||
| + | |||
| + | When the firmware crashes ath10k collects various information which helps to debug the crash and creates a crash dump file. This is available via dev_coredump facility from /sys/class/devcoredump. | ||
| + | |||
| + | To automatically collect devcoredump files add script /usr/local/sbin/devcoredump-collect.sh: | ||
| + | |||
| + | <code> | ||
| + | #!/bin/sh | ||
| + | |||
| + | timestamp=$(date +%Y%m%d%H%M%S) | ||
| + | filename="/var/spool/devcoredump/devcoredump-${timestamp}.dump" | ||
| + | cp /sys/${DEVPATH}/data ${filename} | ||
| + | echo 1 > /sys/${DEVPATH}/data | ||
| + | logger "created ${filename}"</code> | ||
| + | |||
| + | Create a directory for the dump files: | ||
| + | |||
| + | <code> | ||
| + | sudo mkdir /var/spool/devcoredump</code> | ||
| + | |||
| + | And add a udev rules script /etc/udev/rules.d/50-devcoredump.rules: | ||
| + | |||
| + | <code> | ||
| + | SUBSYSTEM=="devcoredump", ACTION=="add", RUN+="/usr/local/sbin/devcoredump-collect.sh"</code> | ||
| + | |||
| + | |||
en/users/drivers/ath10k/debug.1429884906.txt.gz ยท Last modified: 2015/04/24 14:15 by Kalle Valo
Page Tools
