From owner-freebsd-usb@FreeBSD.ORG Fri Mar 5 09:50:06 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 0C5FC106566C for ; Fri, 5 Mar 2010 09:50:06 +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 F1E778FC0C for ; Fri, 5 Mar 2010 09:50:05 +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 o259o5xB017329 for ; Fri, 5 Mar 2010 09:50:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o259o5pC017328; Fri, 5 Mar 2010 09:50:05 GMT (envelope-from gnats) Date: Fri, 5 Mar 2010 09:50:05 GMT Message-Id: <201003050950.o259o5pC017328@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Hans Petter Selasky 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: Hans Petter Selasky List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Mar 2010 09:50:06 -0000 The following reply was made to PR usb/144423; it has been noted by GNATS. From: Hans Petter Selasky To: PseudoCylon Cc: bug-followup@freebsd.org, jhanna@pangolin-systems.com, freebsd-usb@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: usb/144423: if_run panic with USB-N13 Date: Fri, 5 Mar 2010 10:42:41 +0100 On Friday 05 March 2010 10:31:35 PseudoCylon wrote: > >The files seem a little far from the current I am running, I just used > >the updates to the usbdevs file and the unlock-lock around the firmware > > load in if_run.c. > > Yes, there are some bits added to support RT3572 chipsets. It would be > greately appreciated if you try that file if it's not too mutch trouble. > > >The ASUS-N13 does work when a child wlan device is created with it, > >but if just "ifconfig run0 up" is done there is a page fault. I do > >not know if that is expected. This occurs with or without runfw.ko > >being loaded beforehand. > > Yes, "ifconfig run0 up" will cause page fault. 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 *wlan0* up", it > works, but if you "ifconfig *run0* up", it causes panic. (Of cource > without *. I'm trying to enphasize the point in plain text messeage.) That > is what should happen. (Actually, result of "ifconfig *run0* up" is > undefined.) "run0" should only be used when creating wlan. > > If "ifconfig *wlan0* ..." is causing problem, please let us know. > What is the backtrace of the panic? --HPS