From owner-freebsd-current@FreeBSD.ORG Sun Dec 21 11:20:02 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C82A416A4CE for ; Sun, 21 Dec 2003 11:20:02 -0800 (PST) Received: from priv-edtnes42.telusplanet.net (outbound05.telus.net [199.185.220.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AD1B43D50 for ; Sun, 21 Dec 2003 11:20:01 -0800 (PST) (envelope-from james@icionline.ca) Received: from localhost ([199.185.220.240]) by priv-edtnes42.telusplanet.net (InterMail vM.6.00.05.02 201-2115-109-103-20031105) with ESMTP id <20031221192001.NOC3871.priv-edtnes42.telusplanet.net@localhost> for ; Sun, 21 Dec 2003 12:20:01 -0700 Received: from 24.64.142.120 ( [24.64.142.120]) as user urbanex2@192.168.200.1 by webmail.telus.net with HTTP; Sun, 21 Dec 2003 11:20:00 -0800 Message-ID: <1072034400.3fe5f260ca848@webmail.telus.net> Date: Sun, 21 Dec 2003 11:20:00 -0800 From: James Earl To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1-cvs X-Originating-IP: 24.64.142.120 Subject: Continued problems with Aironet device and 5.2-RC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Dec 2003 19:20:02 -0000 Hi, I was able to get rid of "an0: failed to read RID ff50 7f21 21 0 2eab, 3" messages, but my connection still eventually drops when transmitting data. I tried many different IRQ combinations in the BIOS setup. Some combinations go t rid of the error message above, and some combinations had more stable results that would NOT partially freeze my system. Another strange thing I noticed... After the connection would drop, I wasn't able to reconnect to my Access Point - even after a reboot, until I powered down, and powered back up the AP! I don't think there's any problem with the AP as it works without problems under 5.1-RELEASE. I also tried booting with ACPI disabled but there was no difference. I monitored system activity using 'systat 1 -vmstat' on both 5.1-RELEASE and 5.2 -RC, but nothing really stood out as being the problem. There is also an fxp0: Intel Pro/100 VE NIC on my machine and it hasn't shown any problems. My Cisco Aironet 350 card has a downgraded firmware - version 5.00.01. I have also tried newer firmware versions just in case, without any luck. Making the transition from 5.1-RELEASE to 5.2-RC I didn't change any BIOS settings, and I built the kernel identical to what I had setup under 5.1-RELEASE. Has anyone else had similar problems with 'an', and 5.2-RC? Is there anything obvious I'm missing?