From owner-freebsd-questions@FreeBSD.ORG Sun Apr 20 07:36:51 2014 Return-Path: Delivered-To: freebsd-questions@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 ESMTPS id 814FE2ED for ; Sun, 20 Apr 2014 07:36:51 +0000 (UTC) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2BEB61432 for ; Sun, 20 Apr 2014 07:36:50 +0000 (UTC) Received: from laptop2.herveybayaustralia.com.au (laptop2.herveybayaustralia.com.au [192.168.0.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id C501227322 for ; Sun, 20 Apr 2014 17:36:41 +1000 (EST) Message-ID: <53537909.3080407@herveybayaustralia.com.au> Date: Sun, 20 Apr 2014 17:36:41 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130516 Thunderbird/17.0.6 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: FBSD10 Atheros wifi not working References: <534B32FA.30500@herveybayaustralia.com.au> <534BC380.90608@herveybayaustralia.com.au> <534E80AB.4000007@herveybayaustralia.com.au> <5350780F.2070806@herveybayaustralia.com.au> <535116CA.9060009@herveybayaustralia.com.au> <53511DC2.6070501@herveybayaustralia.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2014 07:36:51 -0000 On 04/20/14 00:34, Adrian Chadd wrote: > On 18 April 2014 05:42, Da Rock > wrote: >> Skipped another thought - I wouldn't have thought the laptop I have was too >> badly built, and how would the noise cause the error messages? I didn't have >> that many messages for the iwn in the m/c's prior, is it just the atheros >> chipsets? I kind of expect some reconnection issues, but the hardware reset >> messages (from 9.x) were disconcerting - these current ones are obviously >> worse. >> >> And I meant to add: where do I go now? Should I send you the logs or other >> errors? > > Well, I highly recommend rebuilding with debugging in your kernel config: > > * ATH_DEBUG > * AH_DEBUG > * ATH_DIAGAPI Thats already been done, as per last (second to last?) post. All it really managed to do was crash the system. > > And then figure out why you can't build the ath tools. > > The output from athstats will likely be helpful. > > The reset stuff is interesting - it means the NIC is taking way too > long to finish some task. Normally grabbing that lock doesn't take too > long, but something has your NIC angry. > > Yes, please compile up athstats at least. :-) It'd have to be athstats, wouldn't it? Right where it stops compiling with an error (why would it be using gcc still?). I'll give it a shot... Thanks Adrian. And let me know if you want that mini pcie. > > > -a > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"