2017-12-05 16:12:00

by Alexey Brodkin

[permalink] [raw]
Subject: rsi_91x: Failed to read status register on failed authentication

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?

-Alexey


1. Working scenario
======================================================
# cat /etc/wpa_supplicant.conf 
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1

network={
  ssid="YYY"
  psk="zzz"
}

# iw wlan0 scan
BSS 80:19:34:1f:5e:50(on wlan0) -- associated
        TSF: 248634601 usec (0d, 00:04:08)
        freq: 2412
        beacon interval: 100 TUs
        capability: ESS Privacy ShortSlotTime (0x0411)
        signal: -31.00 dBm
        last seen: 0 ms ago
        Information elements from Probe Response frame:
        SSID: YYY
        Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 
        DS Parameter set: channel 1
        ERP: Barker_Preamble_Mode
        Extended supported rates: 24.0 36.0 48.0 54.0 
        RSN:     * Version: 1
                 * Group cipher: CCMP
                 * Pairwise ciphers: CCMP
                 * Authentication suites: PSK
                 * Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
        HT capabilities:
                Capabilities: 0x1ec
                        HT20
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        No DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 4 usec (0x05)
                HT Max RX data rate: 300 Mbps
                HT TX/RX MCS rate indexes supported: 0-15
        HT operation:
                 * primary channel: 1
                 * secondary channel offset: no secondary
                 * STA channel width: 20 MHz
                 * RIFS: 0
                 * HT protection: no
                 * non-GF present: 1
                 * 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
        Extended capabilities: Extended Channel Switching, 6
        WMM:     * Parameter version 1
                 * BE: CW 15-1023, AIFSN 3
                 * BK: CW 15-1023, AIFSN 7
                 * VI: CW 7-15, AIFSN 2, TXOP 2976 usec
                 * VO: CW 3-7, AIFSN 2, TXOP 1472 usec
        WPS:     * Version: 1.0
                 * Wi-Fi Protected Setup State: 2 (Configured)
                 * Response Type: 3 (AP)
                 * UUID: 97b29264-d9a5-5551-88f9-62fbdacb7162
                 * Manufacturer:  
                 * Model:  
                 * Model Number:  
                 * Serial Number:  
                 * Primary Device Type: 0-00000000-0
                 * Device name:  
                 * Config methods: Display, Keypad
                 * Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20

# 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 80:19:34:1f:5e:50
wlan0: send auth to 80:19:34:1f:5e:50 (try 1/3)
wlan0: authenticated
wlan0: associate with 80:19:34:1f:5e:50 (try 1/3)
wlan0: RX AssocResp from 80:19:34:1f:5e:50 (capab=0x411 status=0 aid=1)
IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: associated
rsi_91x: rsi_hal_key_config: Cipher 0xfac04 key_type: 1 key_len: 16
rsi_91x: rsi_mac80211_set_key: RSI set_key
rsi_91x: rsi_hal_key_config: Cipher 0xfac04 key_type: 2 key_len: 16
rsi_91x: rsi_mac80211_set_key: RSI set_key

# udhcpc -i wlan0
udhcpc: started, v1.27.2
udhcpc: sending discover
udhcpc: sending select for 10.42.1.137
udhcpc: lease of 10.42.1.137 obtained, lease time 3600
deleting routers
adding dns 10.42.1.1
# ifconfig 
lo        Link 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:94  
          inet addr:10.42.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: <no flags>
        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 (0x0000)
        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
======================================================


2017-12-06 07:13:40

by Amitkumar Karwar

[permalink] [raw]
Subject: Re: rsi_91x: Failed to read status register on failed authentication

On Tue, Dec 5, 2017 at 9:41 PM, Alexey Brodkin
<[email protected]> 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 0xffffffff > /sys/kernel/debug/phy0/debug_zone

Regards,
Amitkumar

2017-12-14 18:56:30

by Alexey Brodkin

[permalink] [raw]
Subject: rsi_91x: Low bandwidth: sends ~100 Kbits/sec, receives ~1.5 Mbits/sec

Hi Amitkumar,

Yet another observation with RS-9113 module.
I managed to setup an access point on my board with RS-9113 connected either
via SDIO (this one is soldered on my board) or via USB (this is your RS9113
Evaluation Board Rev 4.0).

But regardless the module I use I still see the same bandwidth figures.
RS-9113 sends data at ~100 Kbits and receives at ~1.5-2 Mbits.
See below results of iperf3 runs (from development host side).

The board with RS-9113 acts as a server:
------------------------------------>8-----------------------------------
# iperf3 -c 192.168.111.1
Connecting to host 192.168.111.1, port 5201
[ 4] local 192.168.111.64 port 43430 connected to 192.168.111.1 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 328 KBytes 2.68 Mbits/sec 0 31.1 KBytes
[ 4] 1.00-2.00 sec 63.6 KBytes 521 Kbits/sec 1 31.1 KBytes
[ 4] 2.00-3.00 sec 191 KBytes 1.57 Mbits/sec 0 31.1 KBytes
[ 4] 3.00-4.00 sec 191 KBytes 1.56 Mbits/sec 0 32.5 KBytes
[ 4] 4.00-5.00 sec 191 KBytes 1.56 Mbits/sec 0 36.8 KBytes
[ 4] 5.00-6.00 sec 63.6 KBytes 521 Kbits/sec 0 38.2 KBytes
[ 4] 6.00-7.00 sec 63.6 KBytes 521 Kbits/sec 0 38.2 KBytes
[ 4] 7.00-8.00 sec 191 KBytes 1.56 Mbits/sec 0 48.1 KBytes
[ 4] 8.00-9.00 sec 255 KBytes 2.09 Mbits/sec 0 48.1 KBytes
[ 4] 9.00-10.00 sec 191 KBytes 1.56 Mbits/sec 0 48.1 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 1.69 MBytes 1.42 Mbits/sec 1 sender
[ 4] 0.00-10.00 sec 1.39 MBytes 1.16 Mbits/sec receiver
------------------------------------>8-----------------------------------

The board with RS-9113 acts as a server (but with "-R" it sends us data now):
------------------------------------>8-----------------------------------
# iperf3 -c 192.168.111.1 -R
Connecting to host 192.168.111.1, port 5201
Reverse mode, remote host 192.168.111.1 is sending
[ 4] local 192.168.111.64 port 45230 connected to 192.168.111.1 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.14 sec 15.6 KBytes 112 Kbits/sec
[ 4] 1.14-2.00 sec 2.83 KBytes 27.0 Kbits/sec
[ 4] 2.00-3.00 sec 12.7 KBytes 104 Kbits/sec
[ 4] 3.00-4.00 sec 14.1 KBytes 116 Kbits/sec
[ 4] 4.00-5.00 sec 12.7 KBytes 104 Kbits/sec
[ 4] 5.00-6.00 sec 14.1 KBytes 116 Kbits/sec
[ 4] 6.00-7.00 sec 14.1 KBytes 116 Kbits/sec
[ 4] 7.00-8.00 sec 12.7 KBytes 104 Kbits/sec
[ 4] 8.00-9.00 sec 14.1 KBytes 116 Kbits/sec
[ 4] 9.00-10.00 sec 12.7 KBytes 104 Kbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 296 KBytes 242 Kbits/sec 2 sender
[ 4] 0.00-10.00 sec 254 KBytes 208 Kbits/sec receiver
------------------------------------>8-----------------------------------

My configurations are as below.
hostapd.conf:
------------------------------------>8-----------------------------------
interface=wlan0
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=AP_NAME
hw_mode=g
channel=1
------------------------------------>8-----------------------------------

wpa_supplicant.conf
------------------------------------>8-----------------------------------
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1

network={
ssid="AP_NAME"
psk="password"
}
------------------------------------>8-----------------------------------

Note I use vanilla Linux v4.14.4.

I'm wondering if you may see different results in your setup and if so
could you please suggest something for me to try.


Thanks in advance,
Alexey

P.S. I do remember about my previous email but so far I was not able to
get with the board to the place with "problematic" Wi-FI AP, once I get
there I'll grab longs for you.

2017-12-15 11:20:49

by Alexey Brodkin

[permalink] [raw]
Subject: Re: rsi_91x: Low bandwidth: sends ~100 Kbits/sec, receives ~1.5 Mbits/sec

Hi Prameela,

On Fri, 2017-12-15 at 11:13 +0530, Prameela Rani Garnepudi wrote:
> Hi Alexey,
>
> Please use the attached patch to improve TX throughput. We will be
> submitting this patch along with few others soon.

Could you please specify which branch this patch is based on?
I tried to apply on 4.14.5 (whatever is latests in "linux-4.14.y")
but first 3 hunks failed to apply.

Maybe there're other dependencies?

Also a couple of questions about this patch.
Even though I'm not a networking/Wi-Fi expert of any kind but just
looking at your changes:

1. I assume for upstreaming that patch will be split in 5 seperate patches
each addressing its own item instead of doing all at once, right?

2. The only obvious change that might help me with bandwidth is increase
of a number of aggregated Tx frames. But bumping from 6 to 8 doesn't look
as a significant improvement. How that might bring Tx bandwidth at least to
what I see on Rx, i.e. make things 10 times faster?

Also while at it I'm wondering why 5GHz mode didn't work for me even though
"iw list" reports 5 GHz mode supported:
----------------------->8------------------
# iw list
Wiphy phy0
...
Frequencies:
* 5180 MHz [36] (20.0 dBm) (no IR)

# cat /etc/hostapd.conf
interface=wlan0
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=HSDK-AP
hw_mode=a
channel=36

# hostapd -B /etc/hostapd.conf
Starting hostapd: Configuration file: /etc/hostapd.conf
rsi_91x: ===> Interface UP <===
rfkill: Cannot open RFKILL contrIPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
ol device
wlan0: IEEE 802.11 Configured channel (36) not found from the channel list of current mode (2) IEEE 802.11a
wlan0: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-3)
wlan0: interface state UNINITIALIZED->DISABLED
wlan0: AP-DISABLED
wlan0: Unable to setup interface.
wlan0: interface state DISABLED->DISABLED
wlan0: AP-DISABLED
hostapd_free_hapd_data: Interface wlan0 wasn't started
----------------------->8------------------

Has it something to do with your another fix in that patch?

-Alexey

2017-12-15 13:24:35

by Alexey Brodkin

[permalink] [raw]
Subject: Re: rsi_91x: Low bandwidth: sends ~100 Kbits/sec, receives ~1.5 Mbits/sec

Hi Prameela,

On Fri, 2017-12-15 at 18:14 +0530, Prameela Rani Garnepudi wrote:
> Hi Alexey,
>
>
> On Friday 15 December 2017 04:50 PM, Alexey Brodkin wrote:
> > Hi Prameela,
> >
> > On Fri, 2017-12-15 at 11:13 +0530, Prameela Rani Garnepudi wrote:
> >> Hi Alexey,
> >>
> >> Please use the attached patch to improve TX throughput. We will be
> >> submitting this patch along with few others soon.
> > Could you please specify which branch this patch is based on?
> > I tried to apply on 4.14.5 (whatever is latests in "linux-4.14.y")
> > but first 3 hunks failed to apply.
> It is based on 4.14.0-rc7+
> >
> > Maybe there're other dependencies?
> >
> > Also a couple of questions about this patch.
> > Even though I'm not a networking/Wi-Fi expert of any kind but just
> > looking at your changes:
> >
> > 1. I assume for upstreaming that patch will be split in 5 seperate patches
> > each addressing its own item instead of doing all at once, right?
> >
> > 2. The only obvious change that might help me with bandwidth is increase
> > of a number of aggregated Tx frames. But bumping from 6 to 8 doesn't look
> > as a significant improvement. How that might bring Tx bandwidth at least to
> > what I see on Rx, i.e. make things 10 times faster?
>
> The significant change to improve performance is bootup parameters
> update as below:
>
> diff --git a/drivers/net/wireless/rsi/rsi_boot_params.h
> b/drivers/net/wireless/rsi/rsi_boot_params.h
> index 238ee96..ad903b22 100644
> --- a/drivers/net/wireless/rsi/rsi_boot_params.h
> +++ b/drivers/net/wireless/rsi/rsi_boot_params.h
> @@ -46,7 +46,8 @@
> (((TA_PLL_M_VAL_20 + 1) * 40) / \
> ((TA_PLL_N_VAL_20 + 1) * (TA_PLL_P_VAL_20 + 1)))
> #define VALID_20 \
> - (WIFI_PLL960_CONFIGS | WIFI_AFEPLL_CONFIGS |
> WIFI_SWITCH_CLK_CONFIGS)
> + (WIFI_TAPLL_CONFIGS | WIFI_PLL960_CONFIGS | WIFI_AFEPLL_CONFIGS | \
> + WIFI_SWITCH_CLK_CONFIGS | BOOTUP_MODE_INFO | CRYSTAL_GOOD_TIME)
> #define UMAC_CLK_40BW \
> (((TA_PLL_M_VAL_40 + 1) * 40) / \
> ((TA_PLL_N_VAL_40 + 1) * (TA_PLL_P_VAL_40 + 1)))
>

With this change alone I don't see any improvement, see iperf3 results before this change:
--------------------------->8-------------------------
Accepted connection from 10.42.1.85, port 33814
[ 5] local 10.42.1.1 port 5201 connected to 10.42.1.85 port 33816
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 1.00-2.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 2.00-3.00 sec 14.1 KBytes 116 Kbits/sec
[ 5] 3.00-4.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 4.00-5.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 5.00-6.00 sec 11.3 KBytes 92.7 Kbits/sec
[ 5] 6.00-7.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 7.00-8.00 sec 11.3 KBytes 92.7 Kbits/sec
[ 5] 8.00-9.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 9.00-10.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 10.00-11.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 11.00-12.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 12.00-12.44 sec 5.66 KBytes 107 Kbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-12.44 sec 157 KBytes 103 Kbits/sec receiver

Accepted connection from 10.42.1.85, port 33818
[ 5] local 10.42.1.1 port 5201 connected to 10.42.1.85 port 33820
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 296 KBytes 2.42 Mbits/sec 0 41.0 KBytes
[ 5] 1.00-2.00 sec 137 KBytes 1.12 Mbits/sec 0 46.7 KBytes
[ 5] 2.00-3.00 sec 127 KBytes 1.04 Mbits/sec 0 53.7 KBytes
[ 5] 3.00-4.00 sec 127 KBytes 1.04 Mbits/sec 0 62.2 KBytes
[ 5] 4.00-5.00 sec 191 KBytes 1.56 Mbits/sec 0 82.0 KBytes
[ 5] 5.00-6.00 sec 191 KBytes 1.56 Mbits/sec 0 113 KBytes
[ 5] 6.00-7.00 sec 573 KBytes 4.69 Mbits/sec 0 158 KBytes
[ 5] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec 0 187 KBytes
[ 5] 8.00-9.00 sec 445 KBytes 3.65 Mbits/sec 0 243 KBytes
[ 5] 9.00-10.00 sec 636 KBytes 5.22 Mbits/sec 0 298 KBytes
[ 5] 10.00-11.00 sec 0.00 Bytes 0.00 bits/sec 0 362 KBytes
[ 5] 11.00-12.00 sec 0.00 Bytes 0.00 bits/sec 0 399 KBytes
[ 5] 12.00-12.87 sec 827 KBytes 7.80 Mbits/sec 0 455 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-12.87 sec 3.47 MBytes 2.26 Mbits/sec 0 sender
--------------------------->8-------------------------

and right after:
--------------------------->8-------------------------
Accepted connection from 10.42.1.85, port 60582
[ 5] local 10.42.1.1 port 5201 connected to 10.42.1.85 port 60584
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 1.00-2.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 2.00-3.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 3.00-4.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 4.00-5.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 5.00-6.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 6.00-7.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 7.00-8.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 8.00-9.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 9.00-10.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 10.00-11.00 sec 12.7 KBytes 104 Kbits/sec
[ 5] 11.00-12.00 sec 14.1 KBytes 116 Kbits/sec
[ 5] 12.00-12.51 sec 5.66 KBytes 90.5 Kbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-12.51 sec 160 KBytes 105 Kbits/sec receiver
-----------------------------------------------------------

Accepted connection from 10.42.1.85, port 60586
[ 5] local 10.42.1.1 port 5201 connected to 10.42.1.85 port 60588
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 296 KBytes 2.42 Mbits/sec 0 42.4 KBytes
[ 5] 1.00-2.00 sec 137 KBytes 1.12 Mbits/sec 0 48.1 KBytes
[ 5] 2.00-3.00 sec 127 KBytes 1.04 Mbits/sec 0 53.7 KBytes
[ 5] 3.00-4.00 sec 127 KBytes 1.04 Mbits/sec 0 62.2 KBytes
[ 5] 4.00-5.00 sec 318 KBytes 2.61 Mbits/sec 0 80.6 KBytes
[ 5] 5.00-6.00 sec 255 KBytes 2.08 Mbits/sec 0 112 KBytes
[ 5] 6.00-7.00 sec 318 KBytes 2.61 Mbits/sec 0 153 KBytes
[ 5] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec 0 188 KBytes
[ 5] 8.00-9.00 sec 509 KBytes 4.17 Mbits/sec 0 233 KBytes
[ 5] 9.00-10.00 sec 0.00 Bytes 0.00 bits/sec 0 270 KBytes
[ 5] 10.00-11.00 sec 573 KBytes 4.69 Mbits/sec 0 345 KBytes
[ 5] 11.00-12.00 sec 0.00 Bytes 0.00 bits/sec 0 387 KBytes
[ 5] 12.00-12.66 sec 954 KBytes 11.8 Mbits/sec 0 414 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-12.66 sec 3.53 MBytes 2.34 Mbits/sec 0 sender
--------------------------->8-------------------------

Any ideas?
Does it really work for you (again I'm trying on top of linux-4.14.y)?

> >
> > Also while at it I'm wondering why 5GHz mode didn't work for me even though
> > "iw list" reports 5 GHz mode supported:
> > ----------------------->8------------------
> > # iw list
> > Wiphy phy0
> > ...
> > Frequencies:
> > * 5180 MHz [36] (20.0 dBm) (no IR)
> >
> > # cat /etc/hostapd.conf
> > interface=wlan0
> > ctrl_interface=/var/run/hostapd
> > ctrl_interface_group=0
> > ssid=HSDK-AP
> > hw_mode=a
> > channel=36
> >
> > # hostapd -B /etc/hostapd.conf
> > Starting hostapd: Configuration file: /etc/hostapd.conf
> > rsi_91x: ===> Interface UP <===
> > rfkill: Cannot open RFKILL contrIPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> > ol device
> > wlan0: IEEE 802.11 Configured channel (36) not found from the channel list of current mode (2) IEEE 802.11a
> > wlan0: IEEE 802.11 Hardware does not support configured channel
> > Could not select hw_mode and channel. (-3)
> > wlan0: interface state UNINITIALIZED->DISABLED
> > wlan0: AP-DISABLED
> > wlan0: Unable to setup interface.
> > wlan0: interface state DISABLED->DISABLED
> > wlan0: AP-DISABLED
> > hostapd_free_hapd_data: Interface wlan0 wasn't started
> > ----------------------->8------------------
> It should work without any issues. I hope you have dual band module with
> you. Please confirm once.

1. How may I tell the module supports 5GHz?
2. If it doesn't support 5GHz why iw reports this support?

-Alexey

2017-12-15 16:09:30

by Alexey Brodkin

[permalink] [raw]
Subject: 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
> <[email protected]> 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 0xffffffff > /sys/kernel/debug/phy0/debug_zone

Please find attached log.
Let me know if you need more details.

-Alexey


Attachments:
2017.12.15-redpine.log (93.95 kB)
2017.12.15-redpine.log