From owner-freebsd-stable@FreeBSD.ORG Mon Aug 19 15:28:45 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E29EFEC for ; Mon, 19 Aug 2013 15:28:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 63B4425A8 for ; Mon, 19 Aug 2013 15:28:44 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id hq12so3175754wib.4 for ; Mon, 19 Aug 2013 08:28:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=fOfW+vBhUhTlYzxrN2WwyOMclib1UeROTOqqaGTdmAY=; b=Ouo4QDlTBPx8K4r6LIUGx3p+A9YtuLZq0SfVaiNJSGQDX4PBpkAV80RX3qweJB0EKj aW6oc03eLTj7dhUJvWVxl/C0MBOpn/GzaoxK+Jr3yWtSbWsz5abifTYRTdo0QFTeL/xw CeVrWF427hpBd09VyusVGHjQLORL1mBsD2sC3tU0KNi177uxtX1aNzQTv6UVcuVy17Sr 0QXTqbhVBp0ckGMxxlQGUvDuNkag9B9DA+bOCbQ4PaaUk513fubEU5MgocVQ82mpYUAL 5Gc+YQlhKEh/kVlSJ7QFCFZ+xFk63rKzLxsVNBTbxamjvvlT41UfghadLQSNZPQyOKL4 xsBg== MIME-Version: 1.0 X-Received: by 10.194.234.100 with SMTP id ud4mr2101082wjc.44.1376926122556; Mon, 19 Aug 2013 08:28:42 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.116.136 with HTTP; Mon, 19 Aug 2013 08:28:42 -0700 (PDT) In-Reply-To: <20130819133000.GA1404@tahoe.tj-h.info> References: <20130818121916.GA55695@tahoe.tj-h.info> <20130819054501.GA92991@tahoe.tj-h.info> <20130819133000.GA1404@tahoe.tj-h.info> Date: Mon, 19 Aug 2013 08:28:42 -0700 X-Google-Sender-Auth: m7IugxO9chiMVsv7lai_Uan4JKk Message-ID: Subject: Re: [ATH] 9.2-PRERELEASE and wlan0 device disconnection From: Adrian Chadd To: Tj Hariharan Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Aug 2013 15:28:45 -0000 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 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 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 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 >