From owner-freebsd-usb@FreeBSD.ORG Wed Jul 14 19:46:13 2010 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 756741065677; Wed, 14 Jul 2010 19:46:13 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 5E8CB8FC16; Wed, 14 Jul 2010 19:46:13 +0000 (UTC) Received: from eagle.syrec.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id o6EJKhN2009974; Wed, 14 Jul 2010 12:20:43 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <4C3E0E0B.8050908@rawbw.com> Date: Wed, 14 Jul 2010 12:20:43 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.10) Gecko/20100708 Thunderbird/3.0.5 MIME-Version: 1.0 To: remko@FreeBSD.org References: <201007141612.o6EGCcMW076016@freefall.freebsd.org> In-Reply-To: <201007141612.o6EGCcMW076016@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-usb@FreeBSD.org Subject: Re: usb/77184: [umass] [panic] kernel panic on USB device disconnect, even if not detected X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jul 2010 19:46:13 -0000 Crash is gone. But there is something wrong. I did the following steps: 1. plug the camera into USB and mount it 2. unplug the camera without unmounting it -- no crash, looks good. 3. mount still exists. that's ok. 4. umount /mnt/camera -- command says: "Device Busy", this looks reasonable. 5. umount -f /mnt/camera -- mount is gone. 6. repeated steps 1...4 on step 4 umount command without -f flag doesn't complain about device busy any more. This is really strange and this means that device disconnect or unmount hasn't been done cleanly and something is different now. So this issue has to be cleared -- outcome of steps 1..5 should always be the same. Yuri