linux-snps-arc.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)
To: linux-snps-arc@lists.infradead.org
Subject: rsi_91x: Failed to read status register / FIRMWARE Assert issues
Date: Tue, 24 Apr 2018 17:37:35 +0000	[thread overview]
Message-ID: <1524591454.11868.7.camel@synopsys.com> (raw)

Hi Amitkumar,

I'm seeing quite a strange behavior of RedPine RS9113SB module.
I tried to use it as wifi hotspot, and sometimes I fail to connect to it.
Moreover after that failure RSI driver starts to flood me with following messages:
Issue 1:
--------------------->8--------------------
rsi_91x: rsi_handle_card_ready: card ready indication in invalid state 9.
rsi_91x: rsi_interrupt_handler: ==> FIRMWARE Assert <==
rsi_91x: rsi_interrupt_handler: Firmware Status is 0x79
rsi_91x: rsi_core_xmit: FSM state not open
rsi_91x: rsi_core_xmit: Failed to queue packet
rsi_91x: rsi_core_xmit: FSM state not open
rsi_91x: rsi_core_xmit: Failed to queue packet
--------------------->8--------------------

Sometimes messages in same situation can be different (Issue 2):
--------------------->8--------------------
rsi_91x: rsi_read_pkt: pkt from invalid queue: 2
rsi_91x: Failed to read the packet
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_data_pkt: Failed to write pkt
rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register
rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register
--------------------->8--------------------

NOTE:
I use vanilla Linux kernel v4.17-rc2
  rsi_91x: FW Version     : 1.6.1
  rsi_91x: Firmware file  : rsi/rs9113_wlan_bt_dual_mode.rps
Also these issues reproduce on vanilla v4.16 Linux kernel
  rsi_91x: FW Version     : 1.5.3
  rsi_91x: Firmware file  : rsi/rs9113_wlan_qspi.rps


Wifi hotspot is started with next commands:
--------------------->8--------------------
# echo 1 > /proc/sys/net/ipv4/ip_forward
# iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
# iptables -A FORWARD -i eth0 -o wlan0 -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
# iptables -A FORWARD -i wlan0 -o eth0 -j ACCEPT
# hostapd -B /etc/hostapd.conf

# cat /etc/hostapd.conf
interface=wlan0
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=HSDK_wifi
hw_mode=g
channel=1
beacon_int=100
dtim_period=2
max_num_sta=255
rts_threshold=-1
fragm_threshold=-1
macaddr_acl=0
auth_algs=3
ignore_broadcast_ssid=0
wmm_enabled=1
wmm_ac_bk_cwmin=4
wmm_ac_bk_cwmax=10
wmm_ac_bk_aifs=7
wmm_ac_bk_txop_limit=0
wmm_ac_bk_acm=0
wmm_ac_be_aifs=3
wmm_ac_be_cwmin=4
wmm_ac_be_cwmax=10
wmm_ac_be_txop_limit=0
wmm_ac_be_acm=0
wmm_ac_vi_aifs=2
wmm_ac_vi_cwmin=3
wmm_ac_vi_cwmax=4
wmm_ac_vi_txop_limit=94
wmm_ac_vi_acm=0
wmm_ac_vo_aifs=2
wmm_ac_vo_cwmin=2
wmm_ac_vo_cwmax=3
wmm_ac_vo_txop_limit=47
wmm_ac_vo_acm=0
eapol_key_index_workaround=0
own_ip_addr=127.0.0.1
--------------------->8--------------------


I tried to reproduce this issues with extended RSI log enabled, this is log tail
for "Issue 2":
--------------------->8--------------------
rsi_91x: Pkt pending interrupt
rsi_91x: rsi_mgmt_pkt_recv: Msg Len: 0, Msg Type:    8
rsi_91x: rsi_sdio_host_intf_write_pkt: Successfully written onto card
rsi_91x: Beacon event
rsi_91x: rsi_core_qos_processor: Queue number = 4
rsi_91x: rsi_send_beacon: Added to beacon queue
rsi_91x: rsi_sdio_host_intf_write_pkt: Successfully written onto card
rsi_91x: rsi_core_qos_processor: Queue number = 5
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_sdio_host_intf_write_pkt: Successfully written onto card
rsi_91x: rsi_core_qos_processor: Queue number = 4
rsi_91x: rsi_sdio_host_intf_write_pkt: Successfully written onto card
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_read_pkt: pkt from invalid queue: 2
rsi_91x: rsi_sdio_host_intf_write_pkt: Successfully written onto card
rsi_91x: Failed to read the packet
rsi_91x: rsi_core_qos_processor: Queue number = 255
rsi_91x: rsi_core_qos_processor: No More Pkt
rsi_91x: rsi_core_qos_processor: Queue number = 255
rsi_91x: rsi_core_qos_processor: No More Pkt
rsi_91x: rsi_core_xmit: ===> Scheduling TX thead <===
rsi_91x: rsi_core_qos_processor: Queue number = 1
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_sdio_host_intf_write_pkt: Successfully written onto card
rsi_91x: rsi_send_data_pkt: Failed to write pkt
rsi_91x: rsi_core_xmit: ===> Scheduling TX thead <===
rsi_91x: rsi_core_qos_processor: Queue number = 1
rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register
rsi_91x: rsi_core_xmit: ===> Scheduling TX thead <===
rsi_91x: rsi_core_qos_processor: Queue number = 1
rsi_91x: rsi_sdio_check_buffer_status: Failed to read status register
--------------------->8--------------------

Any ideas what could be wrong?

-- 
 Eugeniy Paltsev

                 reply	other threads:[~2018-04-24 17:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1524591454.11868.7.camel@synopsys.com \
    --to=eugeniy.paltsev@synopsys.com \
    --cc=linux-snps-arc@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).