From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: rsi_91x: Failed to read status register on failed authentication
Date: Fri, 15 Dec 2017 16:09:19 +0000 [thread overview]
Message-ID: <1513354157.29404.72.camel@synopsys.com> (raw)
In-Reply-To: <CAEhWJF=1GU9vOj5+DeJCOjbbh4zh_OMyv2HKH_1XT3XP2auFUg@mail.gmail.com>
Hi Amitkumar,
On Wed, 2017-12-06@12:43 +0530, Amitkumar Karwar wrote:
> On Tue, Dec 5, 2017 at 9:41 PM, Alexey Brodkin
> <Alexey.Brodkin@synopsys.com> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2017.12.15-redpine.log
Type: text/x-log
Size: 96207 bytes
Desc: 2017.12.15-redpine.log
URL: <http://lists.infradead.org/pipermail/linux-snps-arc/attachments/20171215/d7eabb9d/attachment-0001.bin>
prev parent reply other threads:[~2017-12-15 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 16:11 rsi_91x: Failed to read status register on failed authentication Alexey Brodkin
2017-12-06 7:13 ` Amitkumar Karwar
2017-12-14 18:56 ` rsi_91x: Low bandwidth: sends ~100 Kbits/sec, receives ~1.5 Mbits/sec Alexey Brodkin
[not found] ` <b4c2093d-cc2c-cdd3-52a5-73cefd2c189a@redpinesignals.com>
2017-12-15 11:20 ` Alexey Brodkin
[not found] ` <3f553fb0-d1d2-59f1-32f3-53e993c544ca@redpinesignals.com>
2017-12-15 13:21 ` Alexey Brodkin
2017-12-15 16:09 ` Alexey Brodkin [this message]
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=1513354157.29404.72.camel@synopsys.com \
--to=alexey.brodkin@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).