From owner-freebsd-usb@FreeBSD.ORG Fri Mar 5 10:00:19 2010 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EFD21065675 for ; Fri, 5 Mar 2010 10:00:18 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AE83C8FC1C for ; Fri, 5 Mar 2010 10:00:18 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id o25A0IKb017525 for ; Fri, 5 Mar 2010 10:00:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o25A0I4l017524; Fri, 5 Mar 2010 10:00:18 GMT (envelope-from gnats) Date: Fri, 5 Mar 2010 10:00:18 GMT Message-Id: <201003051000.o25A0I4l017524@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: PseudoCylon Cc: Subject: Re: usb/144423: if_run panic with USB-N13 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: PseudoCylon List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Mar 2010 10:00:19 -0000 The following reply was made to PR usb/144423; it has been noted by GNATS. From: PseudoCylon To: bug-followup@FreeBSD.org, jhanna@pangolin-systems.com Cc: freebsd-usb@freebsd.org, freebsd-gnats-submit@freebsd.org, Hans Petter Selasky Subject: Re: usb/144423: if_run panic with USB-N13 Date: Fri, 5 Mar 2010 01:31:35 -0800 (PST) >The files seem a little far from the current I am running, I just used=0A>= the updates to the usbdevs file and the unlock-lock around the firmware loa= d=0A>in if_run.c.=0AYes, there are some bits added to support RT3572 chipse= ts. It would be greately appreciated if you try that file if it's not too m= utch trouble.=0A=0A>The ASUS-N13 does work when a child wlan device is crea= ted with it,=0A>but if just "ifconfig run0 up" is done there is a page faul= t. I do=0A>not know if that is expected. This occurs with or without runfw.= ko=0A>being loaded beforehand.=0AYes, "ifconfig run0 up" will cause page fa= ult. The wlanN interface is should be created as an instance of the parent = interface and used for actual communication. This is new feature to 8.0 and= 9-current. My understanding is that if you create wlan and "ifconfig *wlan= 0* up", it works, but if you "ifconfig *run0* up", it causes panic. (Of cou= rce without *. I'm trying to enphasize the point in plain text messeage.) T= hat is what should happen. (Actually, result of "ifconfig *run0* up" is und= efined.) "run0" should only be used when creating wlan.=0A=0AIf "ifconfig *= wlan0* ..." is causing problem, please let us know.=0A=0A=0A _________= _________________________________________________________=0AThe new Interne= t Explorer=AE 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now = for Free! at http://downloads.yahoo.com/ca/internetexplorer/