From owner-freebsd-stable@FreeBSD.ORG Mon May 24 01:40:33 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AA3316A4CE for ; Mon, 24 May 2004 01:40:33 -0700 (PDT) Received: from auk2.snu.ac.kr (auk2.snu.ac.kr [147.46.100.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22F6E43D2F for ; Mon, 24 May 2004 01:40:33 -0700 (PDT) (envelope-from stopspam@users.sourceforge.net) Received: from [147.46.44.181] (stopspam@users.sourceforge.net) by auk2.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2004052417:22:45:930801.13435.2716855216 for ; Mon, 24 May 2004 17:22:45 +0900 (KST) Message-ID: <40B1B4F2.6050605@users.sourceforge.net> Date: Mon, 24 May 2004 17:40:18 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Cyril Guibourg , freebsd-stable@freebsd.org References: <40ABFB4A.9060508@users.sourceforge.net> <87ad037d5j.fsf@blackbox.babasse.net> In-Reply-To: <87ad037d5j.fsf@blackbox.babasse.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:11.82) (by Terrace) Subject: Re: USB/umass detach freezes system X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 May 2004 08:40:33 -0000 Cyril Guibourg wrote: > Rob writes: > > >>Mounting this device with "mount_msdos /dev/da0s1 /mnt" is okay. >>The umass filesystem is there. Problems start when unmounting it. >>The umount command will hang and eventually the whole system will hang. >>Power off/on is only what helps then. > > > Welcome on board. I have the same issue and sometimes the system reboots. > It seems it worked better with 4.10-RC1 and starting with RC2 I am back > to 4.9 behaviour. > > >>Any ideas how to deal with this? > > > I would be glad to have the answer to that question. I compiled a kernel > with debug code and tried to figure out what is wrong without any success. > I asked for some help here but got no answer, good luck. Today someone has posted a patch for USB on the CURRENT mailing list, which seems to address this problem. Only bad-luck: the patch applies to CURRENT. Rob.