From owner-freebsd-bugs@FreeBSD.ORG Mon Apr 16 21:09:00 2007 Return-Path: X-Original-To: freebsd-bugs@freebsd.org Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3B89816A401 for ; Mon, 16 Apr 2007 21:09:00 +0000 (UTC) (envelope-from bobf@mrp3.com) Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by mx1.freebsd.org (Postfix) with ESMTP id 1518313C458 for ; Mon, 16 Apr 2007 21:09:00 +0000 (UTC) (envelope-from bobf@mrp3.com) Received: from [70.167.171.130] (helo=[192.168.0.79]) by elasmtp-kukur.atl.sa.earthlink.net with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1HdYDk-0007ta-0R for freebsd-bugs@freebsd.org; Mon, 16 Apr 2007 16:54:44 -0400 Message-ID: <4623E2ED.5040807@mrp3.com> Date: Mon, 16 Apr 2007 13:56:13 -0700 From: Bob Frazier User-Agent: Thunderbird 1.5.0.7 (X11/20061022) MIME-Version: 1.0 To: freebsd-bugs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 549015f0ad0344773aad58b8ed06a5f90a9da525759e2654945f39e705d383759d3b3947dca09c00a7ce0e8f8d31aa3f350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 70.167.171.130 Subject: if_ath driver bug, causes hang with certain access points X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Apr 2007 21:09:00 -0000 [I attempted to submit this using the problem report form but it was not responding after I submitted it] FreeBSD version (uname -a) FreeBSD BSDLaptop 6.2-STABLE FreeBSD 6.2-STABLE #0: Fri Mar 9 20:19:08 PST 2007 bobf@BSDLaptop:/usr/obj/usr/src/sys/GENERIC i386 Problem description: When running access points that use broadcom chipsets (such as the Linksys 300N or WRT54GS), the if_ath driver will occasionally hang when using an Airlink 101 cardbus device (Atheros 5212). The problem typically occurs when a MIMO capable AP (Linksys 300N) or speedboost capable AP (WRT54GS) is being used at close range and the Atheros-based card is NOT associated (only scanning or packet-sniffing via WireShark). I have speculated that it may be due to speedboost or the MIMO packets having a negative effect on the if_ath driver, since this problem does not occur with any other access points to my knowledge. Anecdotally it may also happen if the access point is malfunctioning, sending bad or partial packets, or when there is a LOT of interference (aircraft radar, other access points), but I have only observed this happening with the speedboost-capable or MIMO access points running at close range. Steps to reproduce problem: a) activate a Linksys 300N (configured for MIMO g operation) or WRT54GS access point (with speedboost enabled), but do not associate with the AP. b) enable the 'ath' device via ifconfig, choose a non-existent ssid (so it does not associate) and do a scan, similar to the following command ifconfig ath0 up ssid x scan repeat this several times, as needed FYI - the probability of 'malformed packets' due to 'work in progress' code is very high, so that could be part of the problem. However, even with a malformed packet, the if_ath driver shouldn't hang.