linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gilman <dgilman@gilslotd.com>
To: buytenh@wantstofly.org
Cc: linux-wireless@vger.kernel.org
Subject: Troubleshooting mwl8k driver issue
Date: Fri, 3 Jun 2016 22:54:52 -0500	[thread overview]
Message-ID: <20160604035452.GA5925@dar.local> (raw)

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

`iw event -t' logs (it looks like OpenWRT is patching the heck out of this
tool):

1465008930.594531: wlan1 (phy #1): unknown event 60
1465008930.652119: wlan1 (phy #1): unknown event 60
1465008930.653494: wlan1 (phy #1): unknown event 60
1465008930.655582: wlan1: new station (BSSID MAC)

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

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.

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.

-- 
David Gilman  :DG<
http://gilslotd.com

             reply	other threads:[~2016-06-04  3:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-04  3:54 David Gilman [this message]
2016-06-06  6:51 ` Troubleshooting mwl8k driver issue Lennert Buytenhek
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=20160604035452.GA5925@dar.local \
    --to=dgilman@gilslotd.com \
    --cc=buytenh@wantstofly.org \
    --cc=linux-wireless@vger.kernel.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).