From: David Gilman <dgilman@gilslotd.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
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, 20 Jun 2016 19:36:30 -0500 [thread overview]
Message-ID: <20160621003630.GA39401@dar.local> (raw)
In-Reply-To: <20160618084828.GN20238@wantstofly.org>
On Sat, Jun 18, 2016 at 11:48:28AM +0300, Lennert Buytenhek wrote:
> Nothing in here seems particularly bad. So whatever the problem is,
> I don't think it can be diagnosed from these messages alone.
>
> I went back to the email thread, and it seems that the problem is that
> you're trying to run the card in AP mode but no traffic is making it
> through? Is AP association working at all, or is that failing too?
The mwl8k is in AP mode and it gets associated just fine. It'll work
for five or so minutes and then you'll get the disconnect and the log
messages in the earlier emails. And it only happens with one of my
wireless devices - the other one will browse all day with a stable
connection to the mwl8k router.
Back in the OpenWRT issue a few more people have stuck their heads in
to say they're also seeing the same issue.
https://dev.openwrt.org/ticket/21284
--
David Gilman :DG<
http://gilslotd.com
next prev parent reply other threads:[~2016-06-21 1:05 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
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 [this message]
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=20160621003630.GA39401@dar.local \
--to=dgilman@gilslotd.com \
--cc=buytenh@wantstofly.org \
--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).