From: Lennert Buytenhek <buytenh@wantstofly.org>
To: David Gilman <dgilman@gilslotd.com>
Cc: linux-wireless@vger.kernel.org,
Yogesh Ashok Powar <yogeshp@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>
Subject: Re: Troubleshooting mwl8k driver issue
Date: Mon, 6 Jun 2016 09:51:46 +0300 [thread overview]
Message-ID: <20160606065146.GK8402@wantstofly.org> (raw)
In-Reply-To: <20160604035452.GA5925@dar.local>
On Fri, Jun 03, 2016 at 10:54:52PM -0500, David Gilman wrote:
> Lennert, I am a user of your mwl8k driver through the OpenWRT
> distribution. When working with certain WiFi devices I get errors in
> the kernel logs and network connectivity errors on the wireless device.
> The dmesg logs look like this:
>
> [539374.394607] ieee80211 phy1: Added a new stream for (BSSID MAC) 0
> [539374.394650] ieee80211 phy1: Started stream for (BSSID MAC) 0
> [539374.394732] ieee80211 phy1: tx rings drained
> [539374.401372] ieee80211 phy1: Created a BA stream for (BSSID MAC) : tid 0
These are not (necessarily) errors, just debug messages
> There are a number of other users who are also experiencing the same
> issue on the OpenWRT bug tracker:
>
> https://dev.openwrt.org/ticket/21284
There's a bunch of bad-looking stuff in the posted dmesgs, such as:
[ 10.983657] pci 0000:00:01.0: enabling device (0140 -> 0142)
[ 11.972069] ieee80211 phy0: Command RF_ANTENNA error 0x2
[ 11.977455] ieee80211 phy0: failed to set # of RX antennas
[ 11.993318] ieee80211 phy0: Command RF_ANTENNA error 0x2
[ 11.998713] ieee80211 phy0: failed to set # of TX antennas
[ 12.004243] ieee80211 phy0: 88w8366 v48, c8d719177244, STA firmware 4.1.0.3
And:
[ 22.517451] 0000:02:00.0: unable to load firmware helper image
[ 22.523399] ieee80211 phy1: Cannot start firmware
[ 22.528230] ieee80211 phy1: Trying to reload the firmware again
[ 23.016669] ieee80211 phy1: 88w8366 v7, c8d719177246, AP firmware 5.2.8.17
> As I noted in the bug the driver works with some of my wireless devices
> and not others which suggests that something subtle is up with some
> driver in this picture.
Is the behavior consistent per device across boots? I.e. does device
X always work on every boot while device Y never works at all?
> I don't have a whole lot of experience with kernel development (pretty
> much none actually) and I know absolutely nothing about how these WiFi
> devices work. However I am willing to work with you or anyone else on
> the linux-wireless list (which I have CCd) to help troubleshoot this
> issue. I am using OpenWRT on this router and I can get a build
> environment set up for debug kernel builds with their toolchain. I'm
> running a pretty recent kernel (4.4.7) but git log suggests this driver
> hasn't been touched in a while.
For starters, could you post lspci -n output?
Also, do you see the same behavior with older kernels, or have you
only tried 4.4?
next prev parent reply other threads:[~2016-06-06 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 3:54 Troubleshooting mwl8k driver issue David Gilman
2016-06-06 6:51 ` Lennert Buytenhek [this message]
2016-06-10 4:02 ` David Gilman
2016-06-17 19:43 ` David Gilman
2016-06-18 8:48 ` Lennert Buytenhek
2016-06-21 0:36 ` David Gilman
2016-06-21 8:01 ` Lennert Buytenhek
2016-07-03 6:13 ` David Gilman
-- strict thread matches above, loose matches on Subject: below --
2017-05-06 7:21 Menion
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=20160606065146.GK8402@wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=dgilman@gilslotd.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.com \
--cc=yogeshp@marvell.com \
/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).