From owner-freebsd-net@FreeBSD.ORG Mon May 28 14:53:31 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ECC3516A46E for ; Mon, 28 May 2007 14:53:30 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id A967C13C480 for ; Mon, 28 May 2007 14:53:30 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: (qmail 48999 invoked from network); 28 May 2007 14:51:02 -0000 Received: from unknown (HELO ?192.168.0.2?) (spawk@69.123.42.176) by acm.poly.edu with AES256-SHA encrypted SMTP; 28 May 2007 14:51:02 -0000 Message-ID: <465AECDD.6060008@acm.poly.edu> Date: Mon, 28 May 2007 10:53:17 -0400 From: Boris Kochergin User-Agent: Thunderbird 1.5.0.7 (X11/20061009) MIME-Version: 1.0 To: Sepherosa Ziehau References: <465959FF.4040401@acm.poly.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: System hang with Ralink RT2661 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2007 14:53:32 -0000 Sepherosa Ziehau wrote: > On 5/27/07, Boris Kochergin wrote: >> Hi. I got an "SMC SMCWPCI-GM" card the other day, which is one of these: >> >> May 27 01:16:55 router kernel: ral0: mem >> 0xf4000000-0xf4007fff irq 10 at device 13.0 on pci0 >> May 27 01:16:55 router kernel: ral0: MAC/BBP RT2661D, RF RT2529 (MIMO >> XR) >> >> I put it into a Pentium III machine (which has PCI 2.2, per the ral(4) >> man page) running a 7-CURRENT build from earlier today with a GENERIC >> kernel, and attempted to connect to my wireless network, the access >> point of which is an Atheros 5212 card, which has been serving Prism and >> other Atheros cards for months. The RT2661 card associated fine and was >> able to carry out lightweight operations like pinging and HTTP requests, >> but when I attempted to use it to send or receive any heavy traffic (a >> few dozen KiB/second), the system froze. I was able to toggle the caps >> lock/num lock lights, and if I did something to make the system beep >> (i.e. by pressing ALT+F10 when there was no virtual terminal running >> there), the beep would ring out endlessly. It may also be worth >> mentioning that the system was unresponsive to ACPI (via the power >> button) and that the same RT2661 card in the same machine has no trouble >> sniffing over 2 MiB/second of traffic via tcpdump. I'll be happy to >> provide any other information that may be deemed useful. Thanks. > > Try changing ~line160 of dev/ral/rt2661reg.h > From > #define RT2661_SHORT_PREAMBLE (1 << 19) > #define RT2661_MRR_ENABLED (1 << 20) > #define RT2661_MRR_CCK_FALLBACK (1 << 23) > to > #define RT2661_SHORT_PREAMBLE (1 << 18) > #define RT2661_MRR_ENABLED (1 << 19) > #define RT2661_MRR_CCK_FALLBACK (1 << 22) > > This will make the situation better. > > Except the above wrongly configured MMR register values, rt2661 parts' > TX intr processing is completely wrong; The channel TX power is > incorrect too, for 11bg the difference between the correct one and the > value that driver is using is small, but for 11a, the channel TX power > will be completely wrong. > > Best Regards, > sephe > Doesn't seem to have any effect. Thanks, though. I guess I'll wait for SAM_WIFI to become available in -CURRENT. -Boris