From: Avery Pennarun <apenwarr@gmail.com>
To: Janusz Dziedzic <janusz.dziedzic@gmail.com>
Cc: Ben Greear <greearb@candelatech.com>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: ath10k driver crashes whenever firmware crashes on ARM SoC
Date: Tue, 28 Jan 2014 15:51:06 -0500 [thread overview]
Message-ID: <CAHqTa-3mnugb8SZU434bsNbhP1xqHrKoEVou72k95iyZLC6hyw@mail.gmail.com> (raw)
In-Reply-To: <CAFED-j=c6i+LMY8gqiWeKehka7Z85b4h8xZNV9grAxkwLY1_yg@mail.gmail.com>
On Tue, Jan 28, 2014 at 3:10 PM, Janusz Dziedzic
<janusz.dziedzic@gmail.com> wrote:
> FW636 have problems with monitor iface:
> iw wlan0 set type monitor
> ifconfig wlan0 up
> tcpdump -i wlan0
> Will always crash firmware after "entered promiscuous mode"
>
> Generally in case you will have/left only one monitor interface and
> active tcpdump (in your case after hostapd kill), you will always get
> this crash. So using monitor interface with FW636 is not good idea.
>
> BTW monitor works fine with 10.x FW.
Well, in this case it gives a mostly-reproducible test case for the
driver's failure to recover from firmware crashes. So it's useful in
that respect. I was using the 10.x firmware until I wanted an easier
way to reproduce the problem :)
Avery
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-01-28 20:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 17:18 ath10k driver crashes whenever firmware crashes on ARM SoC Avery Pennarun
2014-01-28 18:20 ` Ben Greear
2014-01-28 18:34 ` Avery Pennarun
2014-01-28 19:01 ` Ben Greear
2014-01-28 19:11 ` Avery Pennarun
2014-01-28 20:10 ` Janusz Dziedzic
2014-01-28 20:51 ` Avery Pennarun [this message]
2014-01-29 16:44 ` Kalle Valo
[not found] ` <CAJ-VmokorbJ2iU4rGNYdRj+A22NR9cV-5h-tDN0pD2FCurZDpA@mail.gmail.com>
2014-01-28 20:55 ` Avery Pennarun
2014-01-29 16:41 ` Kalle Valo
2014-01-29 18:44 ` Adrian Chadd
2014-01-30 2:41 ` Avery Pennarun
2014-02-09 8:00 ` Avery Pennarun
2014-02-27 15:48 ` Missing memory barriers Kalle Valo
2014-02-28 6:10 ` Avery Pennarun
2014-03-06 13:34 ` Kalle Valo
2014-03-11 7:33 ` ath10k driver crashes whenever firmware crashes on ARM SoC Kalle Valo
2014-03-11 7:40 ` Avery Pennarun
2014-03-11 7:52 ` Adrian Chadd
2014-03-11 7:59 ` Avery Pennarun
2014-03-11 8:13 ` Kalle Valo
2014-03-11 8:37 ` Michal Kazior
2014-03-11 8:10 ` Kalle Valo
2014-03-11 19:01 ` Ben Greear
2014-03-12 8:22 ` Kalle Valo
2014-03-12 16:01 ` Ben Greear
2014-03-12 23:28 ` Avery Pennarun
2014-03-13 5:09 ` Kalle Valo
2014-03-13 17:34 ` Adrian Chadd
2014-03-13 17:39 ` Kalle Valo
2014-03-13 17:42 ` Ben Greear
2014-03-14 6:26 ` Kalle Valo
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=CAHqTa-3mnugb8SZU434bsNbhP1xqHrKoEVou72k95iyZLC6hyw@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=janusz.dziedzic@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.