From owner-freebsd-stable@FreeBSD.ORG Mon Aug 19 05:45:36 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 6F9729D8 for ; Mon, 19 Aug 2013 05:45:36 +0000 (UTC) (envelope-from tj@archlinux.us) Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 41824236F for ; Mon, 19 Aug 2013 05:45:35 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id bg4so4173489pad.4 for ; Sun, 18 Aug 2013 22:45:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=GPxLwvEfO0ItbjXjJl1ZDFKEZ/PNbHBJmiXxcIL0q/w=; b=QgITX6E8KeuMvVIsW5G+tCCBbpZGbqA/LCcN+bJK/F2sIIoS1Nx6RGjIxrj0cpNGEh LQanIw3k9qXyfqpTACFe7zwY4UXsVAyh1h5je3P0K9k74Er7Kmb1hiyMV3syufc6cm4J Tm4TEkToY9M2oamlwkF21ifrrxI0HDEu1FNo0j5JqODeuPQhF/horOZF4h+/YFx4B+cJ jLjdUertCy6hDK+ZPna8LgbCFDET7AfpNpj+QtXQKiLIqGbuqJSyH9bqRUZMQgekhe2n JFGaq+T8o4MhU9oAooyJIFJAqaA+12+LWiCC/gVV8IZB0hWVbwTy/2dDeGi6/ZXqwPAZ m2wA== X-Gm-Message-State: ALoCoQkZOGY1rldoFPdZYz22x3+lZDm72Q8whCF13ydBlvfoeaDZ0hfYdyxAL0xBmJGVi4w33KZy X-Received: by 10.68.164.1 with SMTP id ym1mr11591888pbb.33.1376891135289; Sun, 18 Aug 2013 22:45:35 -0700 (PDT) Received: from tahoe.tj-h.info ([117.192.21.27]) by mx.google.com with ESMTPSA id ut7sm12805921pbc.31.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 18 Aug 2013 22:45:34 -0700 (PDT) Date: Mon, 19 Aug 2013 11:15:32 +0530 From: Tj Hariharan To: Adrian Chadd Subject: Re: [ATH] 9.2-PRERELEASE and wlan0 device disconnection Message-ID: <20130819054501.GA92991@tahoe.tj-h.info> References: <20130818121916.GA55695@tahoe.tj-h.info> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QTprm0S8XgL7H0Dt" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 05:45:36 -0000 --QTprm0S8XgL7H0Dt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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).=20 b. There seems to be an extra line in the error logs: =09 "Aug 19 10:53:47 tahoe dhclient[79063]: ioctl(SIOCGIFFLAGS) on wlan0: Operation not permitted" c. Speaking of error logs; I think this was the case before as well, but now it has become more obvious as I try to diagnose the exact issue: the breakage does not ALWAYS produce any output in any logs. i.e.: there are many times that wlan0 craps out and no logs show anything out of the ordinary.=20 d. The above is in addition to the intermittent-ish nature of the issue (that was mentioned) as well as the fact that restarting netif once d= oes not always fix it, sometimes netif needs to be restarted 2 or 3 times in a row. (Before any restarts ping just doesn't show any output. After 1 restart it just immediately gets back to me with "network unreachable" type error).=20 I will try to submit a pr in the next few days, studying for an exam right now.=20 Additionally, once I figure out how to use SVN, I can try to work through the different svn versions to see where it goes awry, though this will take a lot longer as compiling world takes about a full day on this machine.=20 Thanks,=20 -Tj --=20 Tj Hariharan Email: Tj@archlinux.us=20 On Sun, Aug 18, 2013 at 09:02:41AM -0700, Adrian Chadd wrote: > good to know! >=20 >=20 >=20 >=20 > -adrian >=20 >=20 > On 18 August 2013 05:19, Tj Hariharan wrote: >=20 > > 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 ATHER= OS > > 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 we= re > > 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 > > --QTprm0S8XgL7H0Dt Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iJwEAQECAAYFAlIRsPwACgkQzgFEBQLF5IwxDAQAmuCgGq2iGIXrckmuYCAoP29L 4WjIHAwoouj4cS8DL8Cx4LyGSmyaS7bq7PUaPzZ0VMg4/nQu9AAKoIWKfOXmWtUo Yxuwz5SH3g+DKK4MeFHPFN/FW7qmica63BB2aKXuP2pin6rXH9QtDNXlEE2+9ws1 5K7NQvgRJm7XiVwBjmY= =Vfj7 -----END PGP SIGNATURE----- --QTprm0S8XgL7H0Dt--