From owner-freebsd-current@FreeBSD.ORG Wed Nov 12 19:29:14 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 992E81065670 for ; Wed, 12 Nov 2008 19:29:14 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.188]) by mx1.freebsd.org (Postfix) with ESMTP id 165208FC0A for ; Wed, 12 Nov 2008 19:29:13 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by gv-out-0910.google.com with SMTP id n8so149931gve.39 for ; Wed, 12 Nov 2008 11:29:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=3JXkD3QOxtS4Pf5QH8b3qoWfY9ijHJknzxHe1K88MQs=; b=vOMuEj9cxhLuu6AwCZBnPzHtpP18Izm3mq3p9mc8lVo8KG+vWRZOb56CMyAygJQjm+ Y0r13J5UJ1DkJcsPiYYP6A8YO5NlBdkrLVLcBI9FxMXL/2cIrXpZDI2eNqK2jzeI/XQE nkJAJrt4IfCRYgEJXVvizXjOreQD75767AB9A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=dNZ64gtYxMvdgAVcvSxkshjT7wx7gT6NngLx1KBdSRD3ZtCYKgrCbnhKt5LySvmZYe qWf7vay/erGI0FUNbEhk67z/+skry82U1tWMApDdbA8LLEwItNdcAm7cxd5+ah4qn0Eq Ym/dWWMQQa+12K2RMJhl/tI1+8FolZhF5yI88= Received: by 10.86.72.15 with SMTP id u15mr9386832fga.45.1226517675842; Wed, 12 Nov 2008 11:21:15 -0800 (PST) Received: by 10.86.2.18 with HTTP; Wed, 12 Nov 2008 11:21:15 -0800 (PST) Message-ID: <3bbf2fe10811121121q29b60f19va9be4808b962259a@mail.gmail.com> Date: Wed, 12 Nov 2008 20:21:15 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Jeremy Chadwick" In-Reply-To: <20081112182148.GA1308@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <491AEBB5.8010001@zedat.fu-berlin.de> <20081112154240.GA28818@icarus.home.lan> <3bbf2fe10811120744hd740388s25e7413e84bbb8c1@mail.gmail.com> <20081112154744.GA28943@icarus.home.lan> <3bbf2fe10811120752k5e42b912nd0933771696519e0@mail.gmail.com> <20081112161644.GA98426@icarus.home.lan> <3bbf2fe10811120820xeb54b4fj4f4c5e285670c29a@mail.gmail.com> <20081112182148.GA1308@icarus.home.lan> X-Google-Sender-Auth: 90c3ca91ce81cf3c Cc: freebsd-current@freebsd.org, "O. Hartmann" Subject: Re: fsck_ufs after every reboot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2008 19:29:14 -0000 2008/11/12, Jeremy Chadwick : > On Wed, Nov 12, 2008 at 05:20:56PM +0100, Attilio Rao wrote: > > 2008/11/12, Jeremy Chadwick : > > > On Wed, Nov 12, 2008 at 04:52:59PM +0100, Attilio Rao wrote: > > > > 2008/11/12, Jeremy Chadwick : > > > > > On Wed, Nov 12, 2008 at 04:44:52PM +0100, Attilio Rao wrote: > > > > > > 2008/11/12, Jeremy Chadwick : > > > > > > > On Wed, Nov 12, 2008 at 02:44:05PM +0000, O. Hartmann wrote: > > > > > > > > I run FreeBSD 8.0/AMD64 on two boxes (one is a UP older AMD64 Athlon64 > > > > > > > > 3500, other an 8-Core Dell Poweredge 1950). > > > > > > > > > > > > > > > > After nearly every reboot the box does fsck on all UFS2 filesystems. In > > > > > > > > most cases, while shuting down, the box reports about not willing to die > > > > > > > > processes and after a reboot, the filesystems are unclean. > > > > > > > > > > > > > > > > Is this a common problem at the moment or special? > > > > > > > > > > > > > > > > > > > > > I've seen this happen on my CURRENT box at home when using "shutdown -p > > > > > > > now". Instead of the box powering off, it would lock up near the very > > > > > > > end of the shutdown process (before marking the filesystems clean). > > > > > > > > > > > > > > Oddly, this works fine in RELENG_7, so I'm guessing there's some ACPI > > > > > > > development going on (I can't complain, it *is* CURRENT). > > > > > > > > > > > > This could cames after my VFS works. > > > > > > Could you spend some time on this? > > > > > > I will tell you what to look at. > > > > > > > > > > > > > > > Sure thing! > > > > > > > > > > Let me know what I need to do to help, what information you need, or if > > > > > I should revert some commits to see if the behaviour changes. Build > > > > > date of the box (src-all csup'd about 45 minutes prior to the build > > > > > date): > > > > > > > > > > FreeBSD icarus.home.lan 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri Nov 7 14:19:03 PST 2008 root@icarus.home.lan:/usr/obj/usr/src/sys/X7SBA_CURRENT_amd64 amd64 > > > > > > > > Is this reproducible? > > > > > > > > > I don't have an answer at this time. I've only performed "shutdown -p > > > now" on this box twice since running CURRENT, and both times the problem > > > described occurred. > > > > > > > > > > I need you build a kernel with following options: > > > > INVARIANT_SUPPORT > > > > INVARIANTS > > > > DEBUG_VFS_LOCKS > > > > WITNESS > > > > and without WITNESS_SKIPSPIN > > > > > > > > > Will do. Relevant options I use: > > > > > > makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols > > > options SCHED_ULE # ULE scheduler > > > options PREEMPTION # Enable kernel thread preemption > > > options BREAK_TO_DEBUGGER # Sending a serial BREAK drops to DDB > > > options KDB # Enable kernel debugger support > > > options KDB_TRACE # Print stack trace automatically on panic > > > options DDB # Support DDB > > > options GDB # Support remote GDB > > > options INVARIANTS # Enable calls of extra sanity checking > > > options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS > > > options WITNESS # Enable checks to detect deadlocks and cycles > > > options DEBUG_VFS_LOCKS # vfs lock debugging > > > > > > I have physical access to the console of this machine on a regular > > > basis. > > > > It's fine, great. > > > And as luck would have it, I can't reproduce the problem any more. I've > shutdown -p now'd literally 6 times in a row without any sort of lock > up, and this is running on the old kernel. The same behaviour is now > seen with the new kernel. > > So, the 2-3 times I've seen "shutdown -p now" not fully power off the > machine were either flukes, or who knows what/why. > > I simply can't reproduce the problem any longer. I'm sorry. Can you recompile your kernel with the old option (read: not use the old kernel, but recompile it with the old options) and see if it hangs? Did you update the sources in the while? Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein