Has ath(4) ever worked one release and not worked another, please poke me..
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.) Thanks, Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Has ath(4) ever worked one release and not worked another, please poke me..
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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Has ath(4) ever worked one release and not worked another, please poke me..
On Sep 12, 2011, at 8:01 AM, Daniel Eischen wrote: 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. 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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
