Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Apr 2014 07:34:52 -0700
From:      Adrian Chadd <adrian@freebsd.org>
To:        Da Rock <freebsd-questions@herveybayaustralia.com.au>,  "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: FBSD10 Atheros wifi not working
Message-ID:  <CAJ-VmomhTy%2B%2B9hjKyTu4j1sTuG9sxF6C8zVH9e91EKYoZqTkjg@mail.gmail.com>
In-Reply-To: <53511DC2.6070501@herveybayaustralia.com.au>
References:  <534B32FA.30500@herveybayaustralia.com.au> <CAJ-Vmok9Y2Dkgh=x2kP8su7LjrVo==ijSJ5GYrc=wzZv0uwNgQ@mail.gmail.com> <534BC380.90608@herveybayaustralia.com.au> <CAJ-Vmomb2d7jdPRmruaYK1LJ6gZ62_=4N3Ko9Z2eANLJ02c6Rw@mail.gmail.com> <534E80AB.4000007@herveybayaustralia.com.au> <CAJ-Vmoksxv3skF21fhJkYUKpitcadfd9d-L2WAXBDaQvFawo3g@mail.gmail.com> <CAJ-VmokfbMn9GnUdGEE-2XssO1TuoZ0%2Bs04J1oU1qs5cGrb3rQ@mail.gmail.com> <5350780F.2070806@herveybayaustralia.com.au> <CAJ-Vmo=RNHumJNAZmz28jbNk2_ntYSTz2iCdrfF%2BUAO0kxSPCQ@mail.gmail.com> <535116CA.9060009@herveybayaustralia.com.au> <53511DC2.6070501@herveybayaustralia.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On 18 April 2014 05:42, Da Rock
<freebsd-questions@herveybayaustralia.com.au> 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

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. :-)


-a



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomhTy%2B%2B9hjKyTu4j1sTuG9sxF6C8zVH9e91EKYoZqTkjg>