Date: Mon, 12 Sep 2011 09:01:54 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-current@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: Has ath(4) ever worked one release and not worked another, please poke me.. Message-ID: <Pine.GSO.4.64.1109120857230.29775@sea.ntplx.net> In-Reply-To: <CAJ-Vmo=%2B7tZz1tBLTHLtBZfF=Ef8ZCf1e6pea4KaSo1=3rK%2B9g@mail.gmail.com> References: <CAJ-Vmo=%2B7tZz1tBLTHLtBZfF=Ef8ZCf1e6pea4KaSo1=3rK%2B9g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 12 Sep 2011, Adrian Chadd wrote: > Hi all, > > I've had reports here and there from users who have said ath(4) worked > for them in a previous release, and then suddenly stopped working. > Either it stopped probing at all during boot, or it would probe but > then spit out errors when trying to get allocated resources. > > There's been some recent commits to -HEAD which hopefully have > resolved a class of problems that cardbus users have seen. But I'd > like to know if this has popped up for anyone else. > > So, if you're "anyone else", and you've got an example piece of > equipment and an ath(4) NIC which used to work and now doesn't, please > step forward. Please only do so if you're willing to help diagnose the > problem by downloading/compiling/running older kernel images and > wrangling verbose boot messages from it all. It's likely going to be > time consuming and quite tedious. > > I'd like to try and nail whatever lingering issues can be tracked down > before 9.0-RELEASE if possible. Yes, this even means for older NICs > (ie, the non-11n ones.) As described in previous email to -current, part of r222753 needs to be backed out in order for my cardbus ath to work. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.1109120857230.29775>