From owner-freebsd-questions@FreeBSD.ORG Thu Apr 8 18:08:19 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C45CB16A4CE for ; Thu, 8 Apr 2004 18:08:19 -0700 (PDT) Received: from zoot.lafn.org (zoot.lafn.ORG [206.117.18.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8172743D45 for ; Thu, 8 Apr 2004 18:08:19 -0700 (PDT) (envelope-from bc979@lafn.org) Received: from [10.0.1.90] (host-66-81-25-159.rev.o1.com [66.81.25.159]) (authenticated bits=0) by zoot.lafn.org (8.12.3p3/8.12.3) with ESMTP id i3918ES5005926 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Thu, 8 Apr 2004 18:08:17 -0700 (PDT) (envelope-from bc979@lafn.org) Mime-Version: 1.0 (Apple Message framework v613) Content-Transfer-Encoding: 7bit Message-Id: <603563EE-89C2-11D8-9DA3-000393681B06@lafn.org> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-questions@freebsd.org From: Doug Hardie Date: Thu, 8 Apr 2004 18:08:13 -0700 X-Mailer: Apple Mail (2.613) X-Virus-Scanned: ClamAV version 'clamd / ClamAV version devel-20040209', clamav-milter version '0.66m' Subject: Re: Reboot Problem with 5.2.1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Apr 2004 01:08:19 -0000 > On Sun, 4 Apr 2004 23:23:06 -0700 > Doug Hardie wrote: > >> I am testing 5.2.1 in preperation for moving production servers >> eventually from 4.6 to 5.x. Most of the issues I have figured out, >> but >> there is one that I cannot get to work - shutdown -r now. Rebooting >> dies consistently. With the GENERIC kernel I get the message: >> >> Rebooting... >> Keyboard reset did not work, attempting CPU shutdown >> >> In NOTES is a dexcription of BROKEN_KEYBOARD_RESET so I added that and >> rebuilt the kernel. Now all I get is the Rebooting... line and >> nothing >> more. Granted the system I am using for testing is not at all like >> the >> production hardware, but rebooting worked fine on 4.6 with this >> system. >> I am very reluctant to convert any production systems unless I can >> be >> sure they can successfully be rebooted without having a person >> on-site. >> These machines are all unattended and quite far away. Is there a >> workaround for this issue? > Try toggeling hw.acpi.disable_on_poweroff with sysctl. > > Regards, > > Stephen Hilton > Setting both the BROKEN_KEYBOARD_RESET and hw.acpi.disable_on_powerff to 0 fixed my problem. Now the systems reboot properly.