From owner-freebsd-current@FreeBSD.ORG Wed Nov 12 16:20:58 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 0D3EC1065672 for ; Wed, 12 Nov 2008 16:20:58 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.189]) by mx1.freebsd.org (Postfix) with ESMTP id 953078FC1D for ; Wed, 12 Nov 2008 16:20:57 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by gv-out-0910.google.com with SMTP id n8so101978gve.39 for ; Wed, 12 Nov 2008 08:20:56 -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=DsZCQXBlAKFt1eQQGvoU1m4cYCnmVT2NvVFhrmteGoM=; b=EVYINe9UGUX7ZyEfzfGhNIBflbvyJWo0/19+Nf7QR8a2TJEXh+jfluTRGfKmEtDE1n udCMS/WtjtXMe0N+rtwd36SK2zUkv5ym6D78AwnnkJrCp3WI4X5Vqu8li2yz3LViS4sL UsD8DF+k7aVXRdLcy3E3olL9ovI34kjHXLBCo= 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=M29cQInefAkLZauZiEUnOmrJY+zc0EexvQC4jo/2Ov9BSBmEGQ0hOity2by0VVFbcQ ogliJcHgbSwz6344UCl9btesZ7KbrC/kIEYO+Czb1UEiHEnxyuayF6+Wu84YIHdNedQa cNX+H8+iiZOsa9ivIP2lJNj11eNq0NeYaEAx4= Received: by 10.86.79.19 with SMTP id c19mr9288719fgb.26.1226506856441; Wed, 12 Nov 2008 08:20:56 -0800 (PST) Received: by 10.86.2.18 with HTTP; Wed, 12 Nov 2008 08:20:56 -0800 (PST) Message-ID: <3bbf2fe10811120820xeb54b4fj4f4c5e285670c29a@mail.gmail.com> Date: Wed, 12 Nov 2008 17:20:56 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Jeremy Chadwick" In-Reply-To: <20081112161644.GA98426@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> X-Google-Sender-Auth: 96e30de618848b8f 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 16:20:58 -0000 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. > Got it. Just need to wait a little while for world/kernel to build and > then I'll be able to perform the necessary testing. > > I do have one question (and it's a general one): I assume without serial > console (I'm excluding firewire because that's not an option here) or > taking photos of the monitor, there's no way to effectively log all > output from db> to disk for review/access later? (The obvious answer > here is "yes that's correct", being as the kernel itself is more or less > suspended at that point, but I thought I'd ask) You can save the log with log capture for later lookups, but without a serial line or physical access to the machine there is few you can do. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein