From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 19:59:40 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7DAB16A417 for ; Wed, 14 Nov 2007 19:59:40 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from mail.beenic.net (mail.beenic.net [83.246.72.40]) by mx1.freebsd.org (Postfix) with ESMTP id A82C413C442 for ; Wed, 14 Nov 2007 19:59:40 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from [192.168.1.37] (a89-182-174-138.net-htp.de [89.182.174.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.beenic.net (Postfix) with ESMTP id BAC09A44529; Wed, 14 Nov 2007 20:53:35 +0100 (CET) From: "Heiko Wundram (Beenic)" Organization: Beenic Networks GmbH To: Sam Leffler Date: Wed, 14 Nov 2007 21:00:27 +0100 User-Agent: KMail/1.9.7 References: <200711140855.49334.wundram@beenic.net> <473B50F0.5010709@errno.com> In-Reply-To: <473B50F0.5010709@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711142100.27826.wundram@beenic.net> Cc: freebsd-stable@freebsd.org Subject: Re: RT256x PCMCIA card under 7.0-BETA2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2007 19:59:41 -0000 Am Mittwoch, 14. November 2007 20:48:00 schrieb Sam Leffler: > I don't think I can help w/ the interrupt storm but you didn't provide > any logs for wpa_supplicant or wlandebug so it's hard to help w/ that > issue. Sorry for not providing any logs, but I just got the card yesterday, and haven't had an access point in reach during the day (at work) so far. I'll try to get better logging (esp. with net.wlan.debug=-1 and net.wlan.0.debug=-1) this evening, which I'll gladly post the revelant parts of. I just thought that maybe this was a "known" issue with this "newer" chipset I seem to have found with this card "Version 2.0." -- Heiko Wundram Product & Application Development