From owner-freebsd-current@FreeBSD.ORG Fri Sep 14 15:01:38 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8430716A417; Fri, 14 Sep 2007 15:01:38 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id 0691D13C442; Fri, 14 Sep 2007 15:01:37 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [192.38.9.151] (account mc467741@c2i.net HELO laptop) by mailfe03.swip.net (CommuniGate Pro SMTP 5.1.10) with ESMTPA id 619618122; Fri, 14 Sep 2007 17:01:35 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org, freebsd-usb@freebsd.org Date: Fri, 14 Sep 2007 17:01:50 +0200 User-Agent: KMail/1.9.7 References: <20070908164003.06ffa0dc@Picasso.Zahemszky.HU> In-Reply-To: <20070908164003.06ffa0dc@Picasso.Zahemszky.HU> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200709141701.51507.hselasky@c2i.net> Cc: Zahemszky =?iso-8859-2?q?G=E1bor?= Subject: Re: crash (and the backtrace) in the new if_zyd driver 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: Fri, 14 Sep 2007 15:01:38 -0000 Hi, Maybe there is a race condition in the ZYD driver because Giant is not lock= ed=20 when calling the start routine? =2D-HPS On Saturday 08 September 2007, Zahemszky G=E1bor wrote: > Hi! > > I tried the new if_zyd driver with my new Lutec WLA-54L USB-stick on a > today-based CURRENT. My machine recognised it correctly when I plugged > in it: > > zyd0: on uhub2 > zyd0: HMAC ZD1211B, FW 47.25, RF AL2230, PA 0, address 00:02:72:65:66:00 > zyd0: Ethernet address: 00:02:72:65:66:00 > > But when I "ifconfig zyd0 up" -ed it, the machine crashed. Here > is the backtrace of it: >