From owner-freebsd-stable@FreeBSD.ORG Tue May 3 10:08:59 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71B711065674 for ; Tue, 3 May 2011 10:08:59 +0000 (UTC) (envelope-from O.Seibert@cs.ru.nl) Received: from kookpunt.science.ru.nl (kookpunt.science.ru.nl [131.174.30.61]) by mx1.freebsd.org (Postfix) with ESMTP id ECAB18FC1F for ; Tue, 3 May 2011 10:08:58 +0000 (UTC) Received: from twoquid.cs.ru.nl (twoquid.cs.ru.nl [131.174.142.38]) by kookpunt.science.ru.nl (8.13.7/5.31) with ESMTP id p43A8swG021518; Tue, 3 May 2011 12:08:54 +0200 (MEST) Received: by twoquid.cs.ru.nl (Postfix, from userid 4100) id F02132E05D; Tue, 3 May 2011 12:08:54 +0200 (CEST) Date: Tue, 3 May 2011 12:08:54 +0200 From: Olaf Seibert To: Jeremy Chadwick Message-ID: <20110503100854.GY6733@twoquid.cs.ru.nl> References: <20110502143230.GW6733@twoquid.cs.ru.nl> <20110503092113.GA39704@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110503092113.GA39704@icarus.home.lan> User-Agent: Mutt/1.5.19 (2009-01-05) X-Spam-Score: -1.799 () ALL_TRUSTED,BAYES_50 X-Scanned-By: MIMEDefang 2.63 on 131.174.30.61 Cc: freebsd-stable@freebsd.org, Olaf Seibert Subject: Re: Automatic reboot doesn't reboot 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: Tue, 03 May 2011 10:08:59 -0000 On Tue 03 May 2011 at 02:21:13 -0700, Jeremy Chadwick wrote: > There are two things you might try fiddling with. These are sysctls so > you can try them on the fly: > > hw.acpi.disable_on_reboot > hw.acpi.handle_reboot Thanks. For now I've set the second to 1 and we'll see if that affects matters. > Check out the thread Peter Jeremy provided. This is a near-sure > indicator of ZFS ARC exhaustion, and you seem to know of that. What's > very interesting to me is this part of your mail: ... > > Is this box running i386 or amd64? If amd64, I can't explain why your It's amd64. I double-checked just one, you never know what stupid mistakes one might make :-) > /boot/loader.conf settings aren't taking -- they should be for sure. > Maybe provide us a full dmesg and XXX out things you consider > sensitive. If i386, I'm not too surprised that some automatic defaults > get chosen instead of what you ask. Based on one of your mails where setting vm.kmem_size to twice the real RAM size had adverse effects, I've taken the setting out to see if that improves matters. I'll have to wait until the next crash (or opportunity to reboot without too much disturbance) to see the effect. I put dmesg.boot in my other reply. Thanks, > | Jeremy Chadwick jdc@parodius.com | -Olaf. -- Pipe rene = new PipePicture(); assert(Not rene.GetType().Equals(Pipe));