From owner-freebsd-current@FreeBSD.ORG Tue Nov 6 17:18:25 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A70916A419 for ; Tue, 6 Nov 2007 17:18:25 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 0CE6113C4B7 for ; Tue, 6 Nov 2007 17:18:24 +0000 (UTC) (envelope-from sam@errno.com) 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 lA6HI9if089233 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Nov 2007 09:18:09 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <4730A1D1.8020607@errno.com> Date: Tue, 06 Nov 2007 09:18:09 -0800 From: Sam Leffler User-Agent: Thunderbird 2.0.0.6 (X11/20070814) MIME-Version: 1.0 To: Frank Staals References: <472A6708.9030109@clearchain.com> <472B779B.9060002@gmx.net> <472B9597.2050108@clearchain.com> <473082C5.5080700@gmx.net> In-Reply-To: <473082C5.5080700@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: o.com; whitelist Cc: freebsd-current , Benjamin Close Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 06 Nov 2007 17:18:25 -0000 Frank Staals wrote: > Benjamin Close wrote: >> Frank Staals wrote: > >>> >>> >>> >>> Everything works fine with the connection itself. Allthough >>> sometimes when switching from tty9 to tty0 and back the system locks >>> up. I've had it before when switching from tty1 to tty0. Anyone >>> with the same problems ? >>> >>> Anyway; Great work on the driver so far :D >>> >> I've similar issues and believe it might be due to the amount of >> kernel printfs that are happening. Can you sysctl debug.wpi=0 and >> see if the problem still exists? >> By chance are you using ZFS? I caught a memory modified after free >> panic in zfs the other day pid was from syslogd. I'm trying to work >> out if it's related. >> >> Cheers, >> Benjamin >> > When setting debug.wpi to 0 it seems like the problem is gone. I'm not > using ZFS by the way. I did have a problem connecting to the AP at my > university though; the driver wouldn't assosicate whatever I tried. I > didn't have a chance to do some extensive testing though. It might be > because of the WEP+wpa_supplicant + ca certificate method that is > required to authenticate. Anyway I'll let it know if there is an > actual problem with the driver itself Rule of thumb in debugging wireless issues (and most others for that matter): simplify your config if at all possible. In this case try checking things out w/o wpa_supplicant (i.e. no crypto). When debugging, start at the top and work your way down to rule out problems at each layer. In this case collect a wpa_supplicant debug log first, then check for issues at the net80211 layer (wlandebug, wlanstats, etc.), then finally check at the driver level. Sam