[Bug 197187] New: ToF range request through debugfs generates FW error (IO)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=197187

            Bug ID: 197187
           Summary: ToF range request through debugfs generates FW error
                    (IO)
           Product: Backports project
           Version: unspecified
    Kernel Version: 3.19.0-61-lowlatency
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Backports
          Assignee: backports@xxxxxxxxxxxxxxx
          Reporter: mibrahim.ahmed@xxxxxxxxxxx
        Regression: No

Hi,

I have been experimenting the FTM protocol using IWLWIFI on Intel 8260 (also
tried using Intel 8265) through debugfs. Configured two nodes one as AP and the
other one as STA.

Downloaded the Core30 release from this link
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/
And managed to build and install it successfully following the instructions
here:
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release
Load the latest firmware (version 31) from here:
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/
And used the hostapd (to configure the AP) v2.6 from here:
https://w1.fi/cgit/hostap/

Also, I followed the post here for ToF usage:
https://www.spinics.net/lists/linux-wireless/msg166565.html

There are two issues:
1. In the final step for sending request using $ echo 'send_range_request=1' >
tof_range_request: it generates the following error:

[  202.367326] Loading modules backported from iwlwifi
[  202.367328] iwlwifi-stack-public:release/LinuxCore30:6399:0b6afc5b
[  202.376502] iwlwifi 0000:01:00.0: Direct firmware load for iwl-dbg-cfg.ini
failed with error -2
[  202.376517] iwlwifi 0000:01:00.0: Direct firmware load for
iwlwifi-8000C-33.ucode failed with error -2
[  202.376525] iwlwifi 0000:01:00.0: Direct firmware load for
iwlwifi-8000C-32.ucode failed with error -2
[  202.376918] iwlwifi 0000:01:00.0: capa flags index 3 larger than supported
by driver
[  202.377688] iwlwifi 0000:01:00.0: loaded firmware version 31.532993.0
op_mode iwlmvm
[  202.384634] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC
8260, REV=0x208
[  202.456899] iwlwifi 0000:01:00.0: base HW address: 00:c2:c6:f5:9b:46
[  513.119382] iwlwifi 0000:01:00.0: Microcode SW error detected.  Restarting
0x2000000.
[  513.120033] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[  513.120339] iwlwifi 0000:01:00.0: Status: 0x00000100, count: 6
[  513.120661] iwlwifi 0000:01:00.0: Loaded firmware version: 31.532993.0
[  513.121023] iwlwifi 0000:01:00.0: 0x00000071 | ADVANCED_SYSASSERT          
[  513.121407] iwlwifi 0000:01:00.0: 0x000006F7 | trm_hw_status0
[  513.121727] iwlwifi 0000:01:00.0: 0x00000000 | trm_hw_status1
[  513.122045] iwlwifi 0000:01:00.0: 0x00010040 | branchlink2
[  513.122348] iwlwifi 0000:01:00.0: 0x00028DA6 | interruptlink1
[  513.122665] iwlwifi 0000:01:00.0: 0x00010F16 | interruptlink2
[  513.122985] iwlwifi 0000:01:00.0: 0x00000000 | data1
[  513.123263] iwlwifi 0000:01:00.0: 0x00001000 | data2
[  513.123540] iwlwifi 0000:01:00.0: 0x02039842 | data3
[  513.123818] iwlwifi 0000:01:00.0: 0x234013CC | beacon time
[  513.124124] iwlwifi 0000:01:00.0: 0x112E5C04 | tsf low
[  513.124410] iwlwifi 0000:01:00.0: 0x00000000 | tsf hi
[  513.124692] iwlwifi 0000:01:00.0: 0x00000000 | time gp1
[  513.124983] iwlwifi 0000:01:00.0: 0x108BDD5A | time gp2
[  513.125274] iwlwifi 0000:01:00.0: 0x00000001 | uCode revision type
[  513.125616] iwlwifi 0000:01:00.0: 0x0000001F | uCode version major
[  513.125959] iwlwifi 0000:01:00.0: 0x00082201 | uCode version minor
[  513.126300] iwlwifi 0000:01:00.0: 0x00000201 | hw version
[  513.126599] iwlwifi 0000:01:00.0: 0x00C89008 | board version
[  513.126914] iwlwifi 0000:01:00.0: 0x0000001C | hcmd
[  513.127186] iwlwifi 0000:01:00.0: 0xA2F22080 | isr0
[  513.127459] iwlwifi 0000:01:00.0: 0x00804000 | isr1
[  513.127733] iwlwifi 0000:01:00.0: 0x18001802 | isr2
[  513.128005] iwlwifi 0000:01:00.0: 0x40400084 | isr3
[  513.128277] iwlwifi 0000:01:00.0: 0x00000000 | isr4
[  513.128550] iwlwifi 0000:01:00.0: 0x0407001C | last cmd Id
[  513.128857] iwlwifi 0000:01:00.0: 0x00000000 | wait_event
[  513.129157] iwlwifi 0000:01:00.0: 0x0000EF7E | l2p_control
[  513.129462] iwlwifi 0000:01:00.0: 0x00002820 | l2p_duration
[  513.129774] iwlwifi 0000:01:00.0: 0x00000000 | l2p_mhvalid
[  513.130078] iwlwifi 0000:01:00.0: 0x00000030 | l2p_addr_match
[  513.130397] iwlwifi 0000:01:00.0: 0x0000000F | lmpm_pmg_sel
[  513.130708] iwlwifi 0000:01:00.0: 0x15062149 | timestamp
[  513.131003] iwlwifi 0000:01:00.0: 0x00005870 | flow_handler
[  513.131459] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[  513.132092] iwlwifi 0000:01:00.0: Status: 0x00000100, count: 7
[  513.132742] iwlwifi 0000:01:00.0: 0x00100327 | ADVANCED_SYSASSERT
[  513.133403] iwlwifi 0000:01:00.0: 0x00000000 | umac branchlink1
[  513.134046] iwlwifi 0000:01:00.0: 0xC0086B70 | umac branchlink2
[  513.134673] iwlwifi 0000:01:00.0: 0xC00818AC | umac interruptlink1
[  513.135302] iwlwifi 0000:01:00.0: 0x00000000 | umac interruptlink2
[  513.135925] iwlwifi 0000:01:00.0: 0xDEADBEEF | umac data1
[  513.136494] iwlwifi 0000:01:00.0: 0xDEADBEEF | umac data2
[  513.137050] iwlwifi 0000:01:00.0: 0xDEADBEEF | umac data3
[  513.137588] iwlwifi 0000:01:00.0: 0x0000001F | umac major
[  513.138120] iwlwifi 0000:01:00.0: 0x00082201 | umac minor
[  513.138647] iwlwifi 0000:01:00.0: 0xC0886E58 | frame pointer
[  513.139187] iwlwifi 0000:01:00.0: 0xC0886E58 | stack pointer
[  513.139720] iwlwifi 0000:01:00.0: 0x00490800 | last host cmd
[  513.140251] iwlwifi 0000:01:00.0: 0x00000000 | isr status reg
[  513.140806] iwlwifi 0000:01:00.0: FW error in SYNC CMD TOF_RANGE_REQ_CMD
[  513.141429]  [<ffffffffc0741ba1>] iwl_trans_pcie_send_hcmd+0x5b1/0x5e0
[iwlwifi]
[  513.141437]  [<ffffffffc0736c78>] iwl_trans_send_cmd+0x68/0x130 [iwlwifi]
[  513.141475] iwlwifi 0000:01:00.0: Failed to send ToF cmd! err: -5


2. How to configure the AP as responder? just setting ftm_responder=1 in the
hostapd.conf? And call tof_responder_config? or I have to call
tof_responder_params? 
the tof_responder_params file is not generated automatically in the debugfs
directory. The only way that I know to generate it is by setting
IWL_MVM_TOF_IS_RESPONDER in the constants.h file.


Thanks,
Mohamed

-- 
You are receiving this mail because:
You are the assignee for the bug.--
To unsubscribe from this list: send the line "unsubscribe backports" in



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux