From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 26 16:03:42 2008 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24B33106567D for ; Wed, 26 Mar 2008 16:03:42 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id D83458FC12 for ; Wed, 26 Mar 2008 16:03:41 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m2QG3bom058303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Mar 2008 09:03:38 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <47EA73D9.6050302@freebsd.org> Date: Wed, 26 Mar 2008 09:03:37 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: "Alphons \"Fonz\" van Werven" References: <20080326124324.GA1756@rebelion.Sisis.de> <47EA53D5.4070106@student.utwente.nl> In-Reply-To: <47EA53D5.4070106@student.utwente.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: Matthias Apitz , freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: 7.0-RELEASE && panic after ~4 hours 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: Wed, 26 Mar 2008 16:03:42 -0000 Alphons "Fonz" van Werven wrote: > Matthias Apitz wrote: > >> the main difference between home and work is: WEP at home and WPA2 at >> work; > > Which WiFi board are you using? Several drivers are known to cause > panics when > used with WPA. I am aware only of issues with USB adapters being removed while wpa_supplicant is running. This is a race in the usb code that I have worked around in the forthcoming vap code (not sure if the technique I used can be ported to RELENG_7). Regardless, for any issue to be pursued the usual info is required; the device identity, a stack trace, and if possible, debug msgs from the kernel prior to a problem (wlandebug enables net80211 msgs and every driver has a debug msg knob that may or may not require building a kernel w/ msgs enabled). iwi has most recently been tended by Andrew Thompson who is traveling so may not follow up for a bit (if sufficient info is provided). Sam