Hi,
No errors and the file with mode 4511 exists.
On Thu, Oct 24, 2013 at 12:49 PM, J.R. Oldroyd wrote:
> On Wed, 23 Oct 2013 13:12:05 -0700 Adrian Chadd
> wrote:
> >
> > On 23 October 2013 13:10, claudiu vasadi
> wrote:
> >
> > > Hi,
> > >
> > > Still getting the "Cannot reset interface wla
On Wed, 23 Oct 2013 13:12:05 -0700 Adrian Chadd wrote:
>
> On 23 October 2013 13:10, claudiu vasadi wrote:
>
> > Hi,
> >
> > Still getting the "Cannot reset interface wlan0 - exit status 1" in
> > wifimgr but no crash yet. Will keep trying :D
> >
>
> I have no idea about that. It's likely there
Understood. Will do so.
On Wed, Oct 23, 2013 at 10:12 PM, Adrian Chadd wrote:
>
>
>
> On 23 October 2013 13:10, claudiu vasadi wrote:
>
>> Hi,
>>
>> Still getting the "Cannot reset interface wlan0 - exit status 1" in
>> wifimgr but no crash yet. Will keep trying :D
>>
>
> I have no idea about
On 23 October 2013 13:10, claudiu vasadi wrote:
> Hi,
>
> Still getting the "Cannot reset interface wlan0 - exit status 1" in
> wifimgr but no crash yet. Will keep trying :D
>
I have no idea about that. It's likely there's some net80211/iwn bug(s) but
I don't use wifimgr so I don't know what it'
Hi,
Still getting the "Cannot reset interface wlan0 - exit status 1" in wifimgr
but no crash yet. Will keep trying :D
On Wed, Oct 23, 2013 at 9:51 PM, Adrian Chadd wrote:
> Hi,
>
> Please try this:
>
>
> http://people.freebsd.org/~adrian/ath/20131023-net80211-txmgt-locking-2.diff
>
> It implem
Hi,
Please try this:
http://people.freebsd.org/~adrian/ath/20131023-net80211-txmgt-locking-2.diff
It implements what I think is the mostly-right fix:
* remove the node reference in the callout, it's actually not freaking
needed!
* grab the ic lock when doing the timeout callout, ensuring consis
Grr, it's slightly more complicated than that.
That whole timer mess is actually used for two things:
* if the management transmit succeeds - it acts as a short-interval (a few
seconds) timer to ensure that the probe request ends up providing some
response that transitions to auth; otherwise it a
For when the time comes, I'm all in for any tests (if needed).
On Tue, Oct 22, 2013 at 6:07 PM, Adrian Chadd wrote:
> I know what's causing this!
>
> It's because when the management frame completes, there's a callback mbuf
> tag (M_TXCB) that causes the driver to call the net80211 TX completio
I know what's causing this!
It's because when the management frame completes, there's a callback mbuf
tag (M_TXCB) that causes the driver to call the net80211 TX completion
callback.
Now, because some drivers call the net80211 tx completion callback from
within their driver locks, it causes locki
