From owner-freebsd-i386@FreeBSD.ORG Sat May 10 10:43:24 2008 Return-Path: Delivered-To: freebsd-i386@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A80111065676; Sat, 10 May 2008 10:43:24 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.freebsd.org (Postfix) with ESMTP id 2BE088FC19; Sat, 10 May 2008 10:43:24 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from besplex.bde.org (c220-239-252-11.carlnfd3.nsw.optusnet.com.au [220.239.252.11]) by mail14.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m4AAhJm6008636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 May 2008 20:43:22 +1000 Date: Sat, 10 May 2008 20:43:19 +1000 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Volker Werth In-Reply-To: <4824D8C2.6060501@freebsd.org> Message-ID: <20080510203757.W2931@besplex.bde.org> References: <200805082255.m48MtN8B072787@freefall.freebsd.org> <20080509151006.U20170@delplex.bde.org> <4824D8C2.6060501@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: kbyrdPM@yahoo.com, freebsd-i386@freebsd.org Subject: Re: i386/74650: System Reboot with umount command X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2008 10:43:24 -0000 On Sat, 10 May 2008, Volker Werth wrote: > On 05/09/08 07:28, Bruce Evans wrote: >> This might be the bug unsetting the dirty flag which I submitted a fix >> last year, combined with user error (attempting to write to an unwriteable >> disk). ... > thanks for your answer (and for checking my GNATS cleanup). I really > enjoy your explanations. > > If I got you right, you think this PR should be re-opened until an > errata is being released? I think other PRs are enough if we know that this is the same bug. The PR didn't seem to give enough details to be sure of this. If the bug is what I think it is (probably just a write-protected disk), then the driver would write a lot (too many) printfs about write errors. These messages might not be obvious on the console due to being in X mode, but they should be recorded in logs. Bruce