From owner-freebsd-bugs@FreeBSD.ORG Mon Apr 16 20:50:03 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9009416A404 for ; Mon, 16 Apr 2007 20:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 70AD213C45A for ; Mon, 16 Apr 2007 20:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l3GKo3LQ095745 for ; Mon, 16 Apr 2007 20:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3GKo3Kx095744; Mon, 16 Apr 2007 20:50:03 GMT (envelope-from gnats) Resent-Date: Mon, 16 Apr 2007 20:50:03 GMT Resent-Message-Id: <200704162050.l3GKo3Kx095744@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, bob frazier Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 85DD416A402 for ; Mon, 16 Apr 2007 20:46:30 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.freebsd.org (Postfix) with ESMTP id 763E013C45E for ; Mon, 16 Apr 2007 20:46:30 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id l3GKkUKh063667 for ; Mon, 16 Apr 2007 20:46:30 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id l3GKfStq062892; Mon, 16 Apr 2007 20:41:28 GMT (envelope-from nobody) Message-Id: <200704162041.l3GKfStq062892@www.freebsd.org> Date: Mon, 16 Apr 2007 20:41:28 GMT From: bob frazier To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: kern/111744: if_ath occasionally hangs system with certain broadcom AP chipsets 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 20:50:03 -0000 >Number: 111744 >Category: kern >Synopsis: if_ath occasionally hangs system with certain broadcom AP chipsets >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 16 20:50:03 GMT 2007 >Closed-Date: >Last-Modified: >Originator: bob frazier >Release: 6.2 STABLE >Organization: SFT Inc. >Environment: 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 >Description: When testing 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. >How-To-Repeat: 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 >Fix: >Release-Note: >Audit-Trail: >Unformatted: