Date: Mon, 12 Sep 2011 10:15:04 -0500 From: Warner Losh <imp@bsdimp.com> To: Daniel Eischen <deischen@freebsd.org> Cc: Adrian Chadd <adrian@freebsd.org>, 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: <802BD398-6F6B-4584-B1AD-36FDFB23D0D2@bsdimp.com> In-Reply-To: <Pine.GSO.4.64.1109120857230.29775@sea.ntplx.net> References: <CAJ-Vmo=%2B7tZz1tBLTHLtBZfF=Ef8ZCf1e6pea4KaSo1=3rK%2B9g@mail.gmail.com> <Pine.GSO.4.64.1109120857230.29775@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 12, 2011, at 8:01 AM, Daniel Eischen wrote: > On Mon, 12 Sep 2011, Adrian Chadd wrote: >=20 >> Hi all, >>=20 >> 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. >>=20 >> 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. >>=20 >> 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. >>=20 >> 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.) >=20 > As described in previous email to -current, part of r222753 > needs to be backed out in order for my cardbus ath to work. That's not an ath(4) issue, but a cardbus(4) issue. I'll take care of = it after the funeral when I return home, likely next week. Of course, = John can take care of it sooner if he wants. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?802BD398-6F6B-4584-B1AD-36FDFB23D0D2>