From owner-freebsd-current@FreeBSD.ORG  Sat Aug  4 06:42:16 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B006C16A41A;
	Sat,  4 Aug 2007 06:42:16 +0000 (UTC)
	(envelope-from kris@obsecurity.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.freebsd.org (Postfix) with ESMTP id B9FA613C461;
	Sat,  4 Aug 2007 06:42:16 +0000 (UTC)
	(envelope-from kris@obsecurity.org)
Received: from rot26.obsecurity.org (elvis.mu.org [192.203.228.196])
	by elvis.mu.org (Postfix) with ESMTP id 5FFA31A4D7E;
	Fri,  3 Aug 2007 23:41:38 -0700 (PDT)
Received: by rot26.obsecurity.org (Postfix, from userid 1001)
	id DA662C0F6; Sat,  4 Aug 2007 02:42:15 -0400 (EDT)
Date: Sat, 4 Aug 2007 02:42:15 -0400
From: Kris Kennaway <kris@obsecurity.org>
To: Bruno Damour <freebsd.ruomad@free.fr>
Message-ID: <20070804064215.GA2787@rot26.obsecurity.org>
References: <20070803210113.GA68807@rot26.obsecurity.org>
	<46B40D98.4020304@free.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46B40D98.4020304@free.fr>
User-Agent: Mutt/1.4.2.3i
Cc: re@FreeBSD.org, current@FreeBSD.org, Kris Kennaway <kris@obsecurity.org>
Subject: Re: reboot hanging
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2007 06:42:16 -0000

On Sat, Aug 04, 2007 at 07:24:40AM +0200, Bruno Damour wrote:
> I see this also quite frequently (and have seen it for a period of time, 
> running current amd64 updated almost each week).
> each time i have to hard reboot, and restart in single mode to fsck my 
> small boot partition (the rest is zfs, no problem there).
> My proc is a core2 6400. I'm using :
> 
> nooptions     SCHED_4BSD        # 4BSD scheduler
> options     SCHED_ULE        # Newer scheduler
> options     PREEMPTION        # Enable kernel thread preemption
> 
> But I was using SCHED_4BSD before and it did happen as well.
> 
> Sorry no debugging available.

It doesn't sound like the same problem.  In my case buffers are
synched so the filesystems are clean.

Kris