Re: rsi_91x: Failed to read status register on failed authentication
Hi Amitkumar, On Wed, 2017-12-06 at 12:43 +0530, Amitkumar Karwar wrote: > On Tue, Dec 5, 2017 at 9:41 PM, Alexey Brodkin >wrote: > > Hi Amit, > > > > I'm seeing quite a strange behavior of RedPine module. > > It connects perfectly fine to one of access points but fails > > to connect to another. > > > > Moreover after that failure RSI driver starts to flood me with > > messages saying: > > ->8 > > rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register > > ->8 > > > > Below you may find details of my 2 experiments. > > Note I use vanilla Linux kernel v4.14.4 > > > > Any ideas what could be wrong? > > > > Could you enable driver debug zones and share dmesg log for analysis? > > echo 0x > /sys/kernel/debug/phy0/debug_zone Please find attached log. Let me know if you need more details. -Alexey # # mount -t debugfs none /sys/kernel/debug/ # ifco# ifconfig loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:23:A7:65:9B:60 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) # wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf && echo 0x > /s ys/kernel/debug/phy0/debug_zone Successfully initialized wpa_supplicant rfkill: Cannot open RFKILL control device # rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 407, Msg Type:2 rsi_91x: rsi_core_qos_processor: Queue number = 255 rsi_91x: rsi_core_qos_processor: No More Pkt rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 301, Msg Type:2 rsi_91x: rsi_core_qos_processor: Queue number = 255 rsi_91x: rsi_core_qos_processor: No More Pkt rsi_91x: rsi_channel_change: Set channel: 2412 MHz type: 416 channel_no 1 rsi_91x: rsi_set_channel: Sending scan req frame rsi_91x: rsi_core_qos_processor: Queue number = 4 rsi_91x: rsi_sdio_host_intf_write_pkt: Successfully written onto card rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 0, Msg Type:1 rsi_91x: rsi_handle_ta_confirm_type: Invalid TA confirm pkt received rsi_91x: rsi_core_qos_processor: Queue number = 255 rsi_91x: rsi_core_qos_processor: No More Pkt rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_core_xmit: ===> Scheduling TX thead <=== rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 274, Msg Type:2 rsi_91x: rsi_core_qos_processor: Queue number = 4 rsi_91x: rsi_prepare_mgmt_desc: blocking mgmt queue rsi_91x: Mgmt queue blocked rsi_91x: rsi_sdio_host_intf_write_pkt: Successfully written onto card rsi_91x: rsi_core_qos_processor: Queue number = 255 rsi_91x: rsi_channel_change: Set channel: 2417 MHz type: 416 channel_no 2 rsi_91x: rsi_set_channel: Sending scan req frame rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 301, Msg Type:2 rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 16, Msg Type:4 rsi_91x: rsi_mgmt_pkt_recv: Probe confirm received rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 346, Msg Type:2 rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 175, Msg Type:2 rsi_91x: rsi_core_xmit: ===> Scheduling TX thead <=== rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 340, Msg Type:2 rsi_91x: rsi_channel_change: Set channel: 2422 MHz type: 416 channel_no 3 rsi_91x: rsi_set_channel: Sending scan req frame rsi_91x: rsi_core_qos_processor: No More Pkt rsi_91x: rsi_core_qos_processor: Queue number = 4 rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 301, Msg Type:2 rsi_91x: rsi_sdio_host_intf_write_pkt: Successfully written onto card rsi_91x: rsi_core_xmit: ===> Scheduling TX thead <=== rsi_91x: rsi_core_qos_processor: Queue number = 4 rsi_91x: rsi_prepare_mgmt_desc: blocking mgmt queue rsi_91x: Mgmt queue blocked rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt
Re: rsi_91x: Failed to read status register on failed authentication
Hi Amitkumar, On Wed, 2017-12-06 at 12:43 +0530, Amitkumar Karwar wrote: > On Tue, Dec 5, 2017 at 9:41 PM, Alexey Brodkin > wrote: > > Hi Amit, > > > > I'm seeing quite a strange behavior of RedPine module. > > It connects perfectly fine to one of access points but fails > > to connect to another. > > > > Moreover after that failure RSI driver starts to flood me with > > messages saying: > > ->8 > > rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register > > ->8 > > > > Below you may find details of my 2 experiments. > > Note I use vanilla Linux kernel v4.14.4 > > > > Any ideas what could be wrong? > > > > Could you enable driver debug zones and share dmesg log for analysis? > > echo 0x > /sys/kernel/debug/phy0/debug_zone Please find attached log. Let me know if you need more details. -Alexey # # mount -t debugfs none /sys/kernel/debug/ # ifco# ifconfig loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:23:A7:65:9B:60 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) # wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf && echo 0x > /s ys/kernel/debug/phy0/debug_zone Successfully initialized wpa_supplicant rfkill: Cannot open RFKILL control device # rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 407, Msg Type:2 rsi_91x: rsi_core_qos_processor: Queue number = 255 rsi_91x: rsi_core_qos_processor: No More Pkt rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 301, Msg Type:2 rsi_91x: rsi_core_qos_processor: Queue number = 255 rsi_91x: rsi_core_qos_processor: No More Pkt rsi_91x: rsi_channel_change: Set channel: 2412 MHz type: 416 channel_no 1 rsi_91x: rsi_set_channel: Sending scan req frame rsi_91x: rsi_core_qos_processor: Queue number = 4 rsi_91x: rsi_sdio_host_intf_write_pkt: Successfully written onto card rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 0, Msg Type:1 rsi_91x: rsi_handle_ta_confirm_type: Invalid TA confirm pkt received rsi_91x: rsi_core_qos_processor: Queue number = 255 rsi_91x: rsi_core_qos_processor: No More Pkt rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_core_xmit: ===> Scheduling TX thead <=== rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 274, Msg Type:2 rsi_91x: rsi_core_qos_processor: Queue number = 4 rsi_91x: rsi_prepare_mgmt_desc: blocking mgmt queue rsi_91x: Mgmt queue blocked rsi_91x: rsi_sdio_host_intf_write_pkt: Successfully written onto card rsi_91x: rsi_core_qos_processor: Queue number = 255 rsi_91x: rsi_channel_change: Set channel: 2417 MHz type: 416 channel_no 2 rsi_91x: rsi_set_channel: Sending scan req frame rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 301, Msg Type:2 rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 16, Msg Type:4 rsi_91x: rsi_mgmt_pkt_recv: Probe confirm received rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 346, Msg Type:2 rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 175, Msg Type:2 rsi_91x: rsi_core_xmit: ===> Scheduling TX thead <=== rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 340, Msg Type:2 rsi_91x: rsi_channel_change: Set channel: 2422 MHz type: 416 channel_no 3 rsi_91x: rsi_set_channel: Sending scan req frame rsi_91x: rsi_core_qos_processor: No More Pkt rsi_91x: rsi_core_qos_processor: Queue number = 4 rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 301, Msg Type:2 rsi_91x: rsi_sdio_host_intf_write_pkt: Successfully written onto card rsi_91x: rsi_core_xmit: ===> Scheduling TX thead <=== rsi_91x: rsi_core_qos_processor: Queue number = 4 rsi_91x: rsi_prepare_mgmt_desc: blocking mgmt queue rsi_91x: Mgmt queue blocked rsi_91x: rsi_interrupt_handler: Intr_status = 8 8 4 rsi_91x: Pkt pending interrupt rsi_91x:
Re: rsi_91x: Failed to read status register on failed authentication
On Tue, Dec 5, 2017 at 9:41 PM, Alexey Brodkinwrote: > Hi Amit, > > I'm seeing quite a strange behavior of RedPine module. > It connects perfectly fine to one of access points but fails > to connect to another. > > Moreover after that failure RSI driver starts to flood me with > messages saying: > ->8 > rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register > ->8 > > Below you may find details of my 2 experiments. > Note I use vanilla Linux kernel v4.14.4 > > Any ideas what could be wrong? > Could you enable driver debug zones and share dmesg log for analysis? echo 0x > /sys/kernel/debug/phy0/debug_zone Regards, Amitkumar
Re: rsi_91x: Failed to read status register on failed authentication
On Tue, Dec 5, 2017 at 9:41 PM, Alexey Brodkin wrote: > Hi Amit, > > I'm seeing quite a strange behavior of RedPine module. > It connects perfectly fine to one of access points but fails > to connect to another. > > Moreover after that failure RSI driver starts to flood me with > messages saying: > ->8 > rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register > ->8 > > Below you may find details of my 2 experiments. > Note I use vanilla Linux kernel v4.14.4 > > Any ideas what could be wrong? > Could you enable driver debug zones and share dmesg log for analysis? echo 0x > /sys/kernel/debug/phy0/debug_zone Regards, Amitkumar
rsi_91x: Failed to read status register on failed authentication
2.1.137 Bcast:10.42.1.255 Mask:255.255.255.0 inet6 addr: fe80::223:a7ff:fe65:9b94/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5 errors:0 dropped:0 overruns:0 frame:0 TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1028 (1.0 KiB) TX bytes:1738 (1.6 KiB) == 2. Failing scenario: == # cat /etc/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ap_scan=1 network={ ssid="XXX" psk="zzz" } # iw wlan0 scan BSS 6c:3b:6b:7d:a1:46(on wlan0) TSF: 251623213323 usec (2d, 21:53:43) freq: 2427 beacon interval: 100 TUs capability: ESS Privacy ShortSlotTime (0x0411) signal: -65.00 dBm last seen: 0 ms ago Information elements from Probe Response frame: SSID: XXX Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 DS Parameter set: channel 4 ERP: HT capabilities: Capabilities: 0x106e HT20/HT40 SM Power Save disabled RX HT20 SGI RX HT40 SGI No RX STBC Max AMSDU length: 3839 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: No restriction (0x00) HT RX MCS rate indexes supported: 0-15 HT TX MCS rate indexes are undefined RSN: * Version: 1 * Group cipher: CCMP * Pairwise ciphers: CCMP TKIP * Authentication suites: PSK * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x) Extended supported rates: 24.0 36.0 48.0 54.0 HT operation: * primary channel: 4 * secondary channel offset: above * STA channel width: any * RIFS: 0 * HT protection: no * non-GF present: 0 * OBSS non-GF present: 0 * dual beacon: 0 * dual CTS protection: 0 * STBC beacon: 0 * L-SIG TXOP Prot: 0 * PCO active: 0 * PCO phase: 0 WMM: * Parameter version 1 * u-APSD * BE: CW 15-1023, AIFSN 3 * BK: CW 15-1023, AIFSN 7 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec * VO: CW 3-7, AIFSN 2, TXOP 1504 usec # ifconfig wlan0 up rsi_91x: ===> Interface UP <=== rsi_91x: rsi_disable_ps: Cannot accept disable PS in PS_NONE state IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready # wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf Successfully initialized wpa_supplicant rfkill: Cannot open RFKILL control device # wlan0: authenticate with 6c:3b:6b:7d:a1:46 wlan0: send auth to 6c:3b:6b:7d:a1:46 (try 1/3) wlan0: send auth to 6c:3b:6b:7d:a1:46 (try 2/3) wlan0: send auth to 6c:3b:6b:7d:a1:46 (try 3/3) rsi_91x: rsi_sdio_write_register_multiple: Synch Cmd53 write failed -16 rsi_91x: rsi_sdio_host_intf_write_pkt: Unable to write onto the card: -16 rsi_91x: rsi_send_mgmt_pkt: Failed to write the packet wlan0: authentication with 6c:3b:6b:7d:a1:46 timed out wlan0: authenticate with 6c:3b:6b:76:e0:ab wlan0: send auth to 6c:3b:6b:76:e0:ab (try 1/3) wlan0: send auth to 6c:3b:6b:76:e0:ab (try 2/3) wlan0: send auth to 6c:3b:6b:76:e0:ab (try 3/3) rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register wlan0: authentication with 6c:3b:6b:76:e0:ab timed out rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register ==
rsi_91x: Failed to read status register on failed authentication
2.1.137 Bcast:10.42.1.255 Mask:255.255.255.0 inet6 addr: fe80::223:a7ff:fe65:9b94/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5 errors:0 dropped:0 overruns:0 frame:0 TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1028 (1.0 KiB) TX bytes:1738 (1.6 KiB) == 2. Failing scenario: == # cat /etc/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ap_scan=1 network={ ssid="XXX" psk="zzz" } # iw wlan0 scan BSS 6c:3b:6b:7d:a1:46(on wlan0) TSF: 251623213323 usec (2d, 21:53:43) freq: 2427 beacon interval: 100 TUs capability: ESS Privacy ShortSlotTime (0x0411) signal: -65.00 dBm last seen: 0 ms ago Information elements from Probe Response frame: SSID: XXX Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 DS Parameter set: channel 4 ERP: HT capabilities: Capabilities: 0x106e HT20/HT40 SM Power Save disabled RX HT20 SGI RX HT40 SGI No RX STBC Max AMSDU length: 3839 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: No restriction (0x00) HT RX MCS rate indexes supported: 0-15 HT TX MCS rate indexes are undefined RSN: * Version: 1 * Group cipher: CCMP * Pairwise ciphers: CCMP TKIP * Authentication suites: PSK * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x) Extended supported rates: 24.0 36.0 48.0 54.0 HT operation: * primary channel: 4 * secondary channel offset: above * STA channel width: any * RIFS: 0 * HT protection: no * non-GF present: 0 * OBSS non-GF present: 0 * dual beacon: 0 * dual CTS protection: 0 * STBC beacon: 0 * L-SIG TXOP Prot: 0 * PCO active: 0 * PCO phase: 0 WMM: * Parameter version 1 * u-APSD * BE: CW 15-1023, AIFSN 3 * BK: CW 15-1023, AIFSN 7 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec * VO: CW 3-7, AIFSN 2, TXOP 1504 usec # ifconfig wlan0 up rsi_91x: ===> Interface UP <=== rsi_91x: rsi_disable_ps: Cannot accept disable PS in PS_NONE state IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready # wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf Successfully initialized wpa_supplicant rfkill: Cannot open RFKILL control device # wlan0: authenticate with 6c:3b:6b:7d:a1:46 wlan0: send auth to 6c:3b:6b:7d:a1:46 (try 1/3) wlan0: send auth to 6c:3b:6b:7d:a1:46 (try 2/3) wlan0: send auth to 6c:3b:6b:7d:a1:46 (try 3/3) rsi_91x: rsi_sdio_write_register_multiple: Synch Cmd53 write failed -16 rsi_91x: rsi_sdio_host_intf_write_pkt: Unable to write onto the card: -16 rsi_91x: rsi_send_mgmt_pkt: Failed to write the packet wlan0: authentication with 6c:3b:6b:7d:a1:46 timed out wlan0: authenticate with 6c:3b:6b:76:e0:ab wlan0: send auth to 6c:3b:6b:76:e0:ab (try 1/3) wlan0: send auth to 6c:3b:6b:76:e0:ab (try 2/3) wlan0: send auth to 6c:3b:6b:76:e0:ab (try 3/3) rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register wlan0: authentication with 6c:3b:6b:76:e0:ab timed out rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register ==