From owner-freebsd-usb@FreeBSD.ORG Sun Mar 27 14:13:22 2005 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48C9316A4CE for ; Sun, 27 Mar 2005 14:13:22 +0000 (GMT) Received: from md1.swissinfo.org (md1.swissinfo.org [146.159.4.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FDC943D39 for ; Sun, 27 Mar 2005 14:13:21 +0000 (GMT) (envelope-from sebastien.b@swissinfo.org) Received: from mail.swissinfo.org ([194.6.181.33]) by md1.swissinfo.org (phad1.swissinfo.org [146.159.6.9]) (MDaemon.PRO.v7.2.1.R) with ESMTP id 35-md50000370717.msg for ; Sun, 27 Mar 2005 16:16:39 +0200 Received: from AAmiens-152-1-30-30.w83-192.abo.wanadoo.fr (83.192.205.30) by mail.swissinfo.org (7.0.020) (authenticated as sebastien.b) id 4153942002C9FB81; Sun, 27 Mar 2005 16:13:13 +0200 From: Sebastien B To: ticso@cicely.de Date: Sun, 27 Mar 2005 15:13:18 +0000 User-Agent: KMail/1.8 References: <200503261558.21943.sebastien.b@swissinfo.org> <200503262158.32320.sebastien.b@swissinfo.org> <20050326233214.GM14532@cicely12.cicely.de> In-Reply-To: <20050326233214.GM14532@cicely12.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503271513.18915.sebastien.b@swissinfo.org> X-Spam-Processed: phad1.swissinfo.org, Sun, 27 Mar 2005 16:16:39 +0200 (not processed: message from valid local sender) X-MDRemoteIP: 194.6.181.33 X-Return-Path: sebastien.b@swissinfo.org X-MDaemon-Deliver-To: freebsd-usb@freebsd.org X-MDAV-Processed: phad1.swissinfo.org, Sun, 27 Mar 2005 16:16:45 +0200 cc: freebsd-usb@freebsd.org Subject: Re: What's the right way to wait for an USB transfer to complete ? X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 14:13:22 -0000 > Havn't looked at your code yet, but the panic is by accessing a > memory location near address 0, so it's very likely that you are > accesing a structure member from a NULL pointer. I've just fixed it. It was not that simple, there was in fact a problem with a recursed mutex used with cv_wait(). Regards, Sebastien