From owner-freebsd-current@FreeBSD.ORG Tue Jun 24 04:39:29 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5809E7D0 for ; Tue, 24 Jun 2014 04:39:29 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 193752AD9 for ; Tue, 24 Jun 2014 04:39:29 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 7B31C1FE028; Tue, 24 Jun 2014 06:39:25 +0200 (CEST) Message-ID: <53A90116.7040306@selasky.org> Date: Tue, 24 Jun 2014 06:39:50 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: "Lundberg, Johannes" Subject: Re: ucom_free Fatal trap on shutdown / module unload References: <53A3E81B.5050805@selasky.org> <53A79732.6060705@selasky.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Tue, 24 Jun 2014 04:39:29 -0000 On 06/23/14 07:34, Lundberg, Johannes wrote: > I added some logging to see what is going on and this is what I got (none > of the proposed solution solved the problem) > > uhso_detach gets called 7 times (for oid 0-6). It crashes the 2nd time on > the call usbd_transfer_unsetup(sc->sc_xfer, 3); > Hi, You are running -stable presumably? Can you set hw.usb.debug=16 and collects the 10 last prints before the panic, and backtrace would be nice too. This does not happen when you unplug the device, correct? --HPS