From owner-freebsd-mobile@FreeBSD.ORG Sun Jul 30 18:53:57 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA7DF16A4DA for ; Sun, 30 Jul 2006 18:53:57 +0000 (UTC) (envelope-from lists@swaggi.com) Received: from swaggi.com (c-24-91-61-171.hsd1.ma.comcast.net [24.91.61.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DDBE43D46 for ; Sun, 30 Jul 2006 18:53:57 +0000 (GMT) (envelope-from lists@swaggi.com) Received: from localhost ([127.0.0.1] helo=swaggi.com) by swaggi.com with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1G7HN8-0001Xx-Vg for freebsd-mobile@freebsd.org; Sun, 30 Jul 2006 14:54:47 -0500 Received: (from lists@localhost) by swaggi.com (8.13.6/8.13.6/Submit) id k6UJskcC005948; Sun, 30 Jul 2006 14:54:46 -0500 (EST) (envelope-from lists@swaggi.com) From: "Yuri Lukin" To: freebsd-mobile@freebsd.org Cc: X-Originating-IP: 192.168.1.57 X-Mailer: Usermin 1.220 Message-Id: <1154289286.5944@swaggi.com> Date: Sun, 30 Jul 2006 14:54:46 -0500 (EST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1154289286" Subject: Re: Ongoing problems with the "ath" interface - is any relief in sight?? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jul 2006 18:53:58 -0000 This is a multi-part message in MIME format. --bound1154289286 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Ross Finlayson wrote .. > > Interesting... I'm having the reverse problem: With the 6.1-STABLE > CVS as of July 27th, I'm getting many of these ath interface errors. > Because of this, I reverted to the June 21st version, in which the > errors occur less frequently (but still occasionally). > You could always look at the diffs on cvsweb.freebsd.org to see the changes in code since previous commit. IMO, Sam has been doing a great job on the ath driver so maybe your problem is hardware related. --bound1154289286--