From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 13:15:01 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 ACF1A16A41C for ; Thu, 9 Jun 2005 13:15:01 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55A2D43D4C for ; Thu, 9 Jun 2005 13:15:01 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from [192.168.2.10] (p54AAE1C5.dip.t-dialin.net [84.170.225.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 97A42311B2; Thu, 9 Jun 2005 15:17:51 +0200 (CEST) Message-ID: <42A8416B.4090501@incubus.de> Date: Thu, 09 Jun 2005 15:17:31 +0200 From: Matthias Buelow User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050526) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vulpes Velox References: <20050608001306.3FB1F43D5C@mx1.FreeBSD.org> <42A6C7CE.9000002@incubus.de> <200506080908.02478.fcash@ocis.net> <42A71AE1.8020300@incubus.de> <6.2.1.2.0.20050608134054.06b8ccb0@64.7.153.2> <42A73293.5000105@incubus.de> <20050608224802.78f4e6a4@vixen42.local.lan> In-Reply-To: <20050608224802.78f4e6a4@vixen42.local.lan> X-Enigmail-Version: 0.91.0.0 OpenPGP: id=6FF22C9F; url=http://www.mkbuelow.net/mkbkeys Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 5.4: Is it generally unstable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 13:15:01 -0000 Vulpes Velox wrote: > I just had to try the USB part... other than having to unmount it and > remount it, I had no problems. What did you do? I just tried it again, and get: # umount /dev/da0s1 umount: unmount of /ipod failed: Resource temporarily unavailable And that stays that way, until reboot, rendering the da0s1 device unavailable. umount -f produces an instant reset. No panic, nothing, just *zapp* and the machine resets itself. halt gives up on synching buffers after a while (or produces a panic, like I got in earlier "attempts"), rendering the filesystems unclean on the next boot. That's on 5.4-STABLE of perhaps 1-2 weeks ago. mkb.