From owner-freebsd-current@FreeBSD.ORG Thu Jul 5 03:18:36 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9819616A46B for ; Thu, 5 Jul 2007 03:18:36 +0000 (UTC) (envelope-from nslay@comcast.net) Received: from alnrmhc14.comcast.net (alnrmhc14.comcast.net [206.18.177.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7360D13C468 for ; Thu, 5 Jul 2007 03:18:36 +0000 (UTC) (envelope-from nslay@comcast.net) Received: from lightbulb.local (c-68-35-224-189.hsd1.fl.comcast.net[68.35.224.189]) by comcast.net (alnrmhc14) with ESMTP id <20070705030541b14004mju2e>; Thu, 5 Jul 2007 03:05:41 +0000 Message-ID: <468C5FAF.8060702@comcast.net> Date: Wed, 04 Jul 2007 23:04:15 -0400 From: Nathan Lay User-Agent: Thunderbird 2.0.0.4 (X11/20070620) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: -pureg doesn't stick 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: Thu, 05 Jul 2007 03:18:36 -0000 Hi list, I have a recent build (July 1st) and running it as a wireless AP (with hostapd WPA-PSK TKIP) using an atheros card (Netgear WG311T). I've been trying to get an 802.11b client on and I noticed the -pureg option doesn't seem to stick at bootup. e.g. this rc.conf line ifconfig_ath0="ssid Lamp channel 9 mediaopt hostap -pureg up" Maybe -pureg should be specified somewhere else in that line (I also tried "-pureg ssid Lamp channel 9 mediaopt hostap up")? Anyways, I have to login and manually set ath0 to -pureg in order for the 802.11b client to associate. On the side, this same 802.11b client, which runs Windows XP SP2 on a Thinkpad T41 with an Intel Pro Wireless 2100 card will crash both 6.2-RELEASE and 7.0-CURRENT with medium traffic (e.g. streaming radio). On the 6.2 system, the backtrace indicated that the crash occurred in the atheros driver itself ... though I don't have that core handy. I have no way to get the debugging information off of the 7.0 machine until I get a serial cable, but the crash is fairly simple to reproduce (The 6.2 system would crash 2-3 times a day due to this one client). Best Regards, Nathan Lay