From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 28 02:59:45 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5E65647F; Thu, 28 Feb 2013 02:59:45 +0000 (UTC) (envelope-from dantavious313@gmail.com) Received: from mail-ye0-f181.google.com (mail-ye0-f181.google.com [209.85.213.181]) by mx1.freebsd.org (Postfix) with ESMTP id 183463C6; Thu, 28 Feb 2013 02:59:44 +0000 (UTC) Received: by mail-ye0-f181.google.com with SMTP id l2so205429yen.40 for ; Wed, 27 Feb 2013 18:59:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding:content-type; bh=xy9BR41Oj9cKpQlMqcfs2qbJhECrDRd3xtmGWAp/uI4=; b=DIarAE0hNQ6lDFUmJdQNRDdHKUfea+zqreYB6Bn2Lcgwhp/vyhkCz1Hkb3K6JNjw+H efvY/hqXn0FTsmwQoy+4yt5wds8ZmEYJiyHVBS/oORcIVkPslX69v8nogRNq1zlzXLhE sYUh9l2NEhkvKNxPCCxIIemICw9U8Hrrx4tEnZvq4pvDRQaMDAVsMemA9erpqXDB6nfk hUbttYQ1V4RfmhAjy684tgcyIb2iMa3h21VrubkYKYEpak0gLA3mPGax92fNLQivJ+74 Ng5jYvJBACjOTVs0fDIVR9JnaVs67fBzG6MTB4GEopSm04WTjTGgZhRkoZ3ANZ/mgaBA lcoQ== X-Received: by 10.236.69.99 with SMTP id m63mr3645799yhd.46.1362020378322; Wed, 27 Feb 2013 18:59:38 -0800 (PST) Received: from zeus.localnet (c-71-226-137-213.hsd1.ga.comcast.net. [71.226.137.213]) by mx.google.com with ESMTPS id x8sm11251765yhn.12.2013.02.27.18.59.37 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 27 Feb 2013 18:59:37 -0800 (PST) From: Derrick Dantavious Edwards To: Adrian Chadd , freebsd-wireless@freebsd.org Subject: Re: ath0 Device Timeout Issues Date: Wed, 27 Feb 2013 21:59:35 -0500 Message-ID: <2287510.yA44TplU79@zeus> User-Agent: KMail/4.9.5 (FreeBSD/10.0-CURRENT; KDE/4.9.5; amd64; ; ) In-Reply-To: References: <1413125.YF2HxR6oBY@zeus> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 02:59:45 -0000 On Wednesday, February 27, 2013 06:45:04 PM you wrote: > These are only during probe requests, right? > > > > > adrian > > > On 27 February 2013 16:30, Derrick Dantavious Edwards > > wrote: > > Hi, > > > > During recent upgrades to Current, I have been experiencing timeouts with > > the ath0 device. These are the errors that I am receiving. Any ideas? > > > > V/r > > > > Derrick > > > > > > > > ath0: ath_tx_tid_drain_print: norm: node 0xffffff802adf3000: > > bf=0xffffff8001d6e000: addbaw=0, dobaw=0, seqno=0, retry=0 > > ath0: ath_tx_tid_drain_print: node 0xffffff802adf3000: > > bf=0xffffff8001d6e000: txq[3] axq_depth=0, axq_aggr_depth=0 > > ath0: ath_tx_tid_drain_print: node 0xffffff802adf3000: > > bf=0xffffff8001d6e000: tid txq_depth=2 hwq_depth=0, bar_wait=0, > > isfiltered=0 > > ath0: ath_tx_tid_drain_print: node 0xffffff802adf3000: tid 16: sched=1, > > paused=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=5 > > NODS 00:22:5f:78:b1:0a->ff:ff:ff:ff:ff:ff(ff:ff:ff:ff:ff:ff) probe_req 0M > > > > 4000 0000 ffff ffff ffff 0022 5f78 b10a ffff ffff ffff 3000 0000 0108 > > 8284 > > > > 8b96 0c12 1824 3014 0100 000f ac04 0100 000f ac04 0100 000f ac02 0000 3204 > > 3048 606c > > ath0: device timeout > > ath0: ath_tx_tid_drain_print: norm: node 0xffffff80270e6000: > > bf=0xffffff8001d6ee10: addbaw=0, dobaw=0, seqno=0, retry=0 > > ath0: ath_tx_tid_drain_print: node 0xffffff80270e6000: > > bf=0xffffff8001d6ee10: txq[3] axq_depth=0, axq_aggr_depth=0 > > ath0: ath_tx_tid_drain_print: node 0xffffff80270e6000: > > bf=0xffffff8001d6ee10: tid txq_depth=2 hwq_depth=0, bar_wait=0, > > isfiltered=0 > > ath0: ath_tx_tid_drain_print: node 0xffffff80270e6000: tid 16: sched=1, > > paused=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=5 > > NODS 00:22:5f:78:b1:0a->ff:ff:ff:ff:ff:ff(ff:ff:ff:ff:ff:ff) probe_req 0M > > > > 4000 0000 ffff ffff ffff 0022 5f78 b10a ffff ffff ffff 3000 0000 0108 > > 8284 > > > > 8b96 0c12 1824 3014 0100 000f ac04 0100 000f ac04 0100 000f ac02 0000 3204 > > 3048 606c > > ath0: device timeout > > > > FreeBSD 10.0-CURRENT #0 r247397: Wed Feb 27 08:53:24 EST 2013 > > > > ath0@pci0:2:0:0: class=0x028000 card=0x3041103c chip=0x002a168c > > rev=0x01 hdr=0x00 > > > > vendor = 'Atheros Communications Inc.' > > device = 'AR928X Wireless Network Adapter (PCI-Express)' > > class = network > > > > _______________________________________________ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to > > "freebsd-wireless-unsubscribe@freebsd.org" Yes. When I start the system, I get those messages. Wireless Link fails to establish thus causing all services requring link to fail....ie NFS . Soon after I am at the command prompt or GUI, I can ping hosts however, I have to /etc/rc.d/mountlate to get remote filesystems connected. Thanks for your assistance. V/r Derrick