Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Aug 2013 23:55:07 +0530
From:      Tj <tj@archlinux.us>
To:        Adrian Chadd <adrian@freebsd.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: [ATH] 9.2-PRERELEASE and wlan0 device disconnection
Message-ID:  <CAOz4XF-E68-NoYvL5igKtT-rUNno2RiVDeZaEkuwFpq5nfEbSQ@mail.gmail.com>
In-Reply-To: <CAJ-Vmon5qLPZy=ANDSd4nB41PaNfNR7YB1_d6a7X=h=gm-4zQg@mail.gmail.com>
References:  <CAOz4XF-%2B4dnecDkFTy6FPHqjSYjxmYkM9Ctp0QiXnf%2B7CsueEg@mail.gmail.com> <CAOz4XF9Ne54ohTfF26tFWjc34qeFy2jwk5bKeNDpbwGurgOsFA@mail.gmail.com> <CAOz4XF8_=_ZuoHj0-Xz3dmLOt=AB6Hu64ppqQ9d0WoC-zBeiEw@mail.gmail.com> <CAJ-Vmon-pyc_j4Pj8Sb6VFZfXRXk%2Bra1uRg-hXBhGcO7WPxLYQ@mail.gmail.com> <20130818121916.GA55695@tahoe.tj-h.info> <CAJ-VmokkFTnOs=%2BPZH-xt76sodHVC9KYNkaDE%2BUOcxP7VWnyyQ@mail.gmail.com> <20130819054501.GA92991@tahoe.tj-h.info> <20130819133000.GA1404@tahoe.tj-h.info> <CAJ-Vmon5qLPZy=ANDSd4nB41PaNfNR7YB1_d6a7X=h=gm-4zQg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hmm yea will try that and let you know. Switching to -head though...maybe
that'll make it better.

I have to say though..wow this driver's come a long way in a year. Thanks
for all the work...

-Tj
On Aug 19, 2013 8:58 PM, "Adrian Chadd" <adrian@freebsd.org> wrote:

> Hi,
>
> Please just do it manually for now.
>
> # ifconfig wlan0
> # ifconfig wlan0 create wlandev ath0
> # wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf &
> # dhclient wlan0
>
> .. see what happens.
>
>
>
> -adrian
>
>
>
> On 19 August 2013 06:30, Tj Hariharan <tj@archlinux.us> wrote:
>
>> On Mon, Aug 19, 2013 at 11:15:32AM +0530, Tj Hariharan wrote:
>> > O never mind, it still happens, though obviously more intermittently,
>> > since I didn't notice anything odd for almost an entire day. A few more
>> > things this time though:
>> >
>> > a. It IS intermittent, there seems to be very little pattern to this,
>> > except that it seems to be more likely to happen when/if I am using the
>> > internet more and actively (e.g. youtube etc rather than just let a few
>> > small internet using things run).
>> >
>> > b. There seems to be an extra line in the error logs:
>> >
>> >       "Aug 19 10:53:47 tahoe dhclient[79063]: ioctl(SIOCGIFFLAGS) on
>> >               wlan0: Operation not permitted"
>>
>> > On Sun, Aug 18, 2013 at 09:02:41AM -0700, Adrian Chadd wrote:
>> > > good to know!
>> > >
>> > >
>> > >
>> > >
>> > > -adrian
>> > >
>> > >
>> > > On 18 August 2013 05:19, Tj Hariharan <tj@archlinux.us> wrote:
>> > >
>> > > > Ok so, at the time I was using r254246. Just this afternoon, I
>> realised
>> > > > there were quite a few commits after that. I am now on r254444 and
>> > > > everything seems to be working fine, i.e. no more wlan0 dying
>> randomly.
>> > > > I have no idea what is causing this, though. (the r254246 was from
>> > > > installing from a download of 9.2 dvd).
>> > > > On Sat, Aug 17, 2013 at 09:49:49PM -0700, Adrian Chadd wrote:
>> > > > > Hi!
>> > > > >
>> > > > > I'm not sure what could've caused this! Not much has changed in
>> the
>> > > > > wireless stack and ath driver between 9.1 and 9.2. Would you be
>> able to
>> > > > > work through different svn versions of stable/9 between 9.1 and
>> 9.2 to
>> > > > > narrow down when things broke?
>> > > > >
>> > > > > It may be something other than the wifi driver/stack.
>> > > > >
>> > > > > Thanks!
>> > > > >
>> > > > >
>> > > > > -adrian
>> > > > >
>> > > > >
>> > > > >
>> > > > > On 17 August 2013 05:12, Tj <tj@archlinux.us> wrote:
>> > > > >
>> > > > > > (Sorry emailed from wrong address, re emailing)
>> > > > > >
>> > > > > > Hi, I just upgraded to 9.2-PRERELEASE from 9.1-RELEASE, I have
>> not had
>> > > > this
>> > > > > > problem before with any version of freebsd however. I have an
>> ATHEROS
>> > > > card
>> > > > > > (AR928X according to pciconf), things go fine except every few
>> > > > > > minutes/hours (randomly) I get the following
>> > > > > > http://bpaste.net/show/123755/ type
>> > > > > > of error, and  the network is no longer connected, however,
>> beyond the
>> > > > fact
>> > > > > > that I can't even reach my router there's no obvious other
>> sign, I.e
>> > > > > > ifconfig still shows a valid output with ip address etc as if
>> it were
>> > > > still
>> > > > > > connected. Restarting the netif service fixes it, until it
>> happens
>> > > > again -
>> > > > > > which it does in a short while (though sometimes I have to
>> restart
>> > > > netif
>> > > > > > twice).
>> > > > > >
>> > > > > > As I said, this happened just as I upgraded from 9.1 to 9.2.
>> Anyone
>> > > > have
>> > > > > > any idea what's causing this?
>> > > > > >
>> > > > > > -Tj Hariharan
>> > > > > > _______________________________________________
>> > > > > > freebsd-stable@freebsd.org mailing list
>> > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> > > > > > To unsubscribe, send any mail to "
>> > > > freebsd-stable-unsubscribe@freebsd.org"
>> > > > > >
>> > > >
>> > > > --
>> > > > Tejas (Tj) Hariharan
>> > > > Email: tj@archlinux.us
>> > > >
>> >
>>
>>
>> Okay it's gotten MUCH worse now. netif can no longer be stopped without
>> a reboot when "wlan0" craps out. (As I mentioned a restart usually fixes
>> things). While trying to stop netif attempts to destroy the wlan0
>> interface, which fails - which, as it turns out is where the "ioctl:
>> operation not permitted error" error comes from I think.
>> --
>> Tj Hariharan
>> Email: Tj@archlinux.us
>>
>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOz4XF-E68-NoYvL5igKtT-rUNno2RiVDeZaEkuwFpq5nfEbSQ>