From owner-freebsd-stable@FreeBSD.ORG Sun Apr 4 23:23:12 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45F3616A4CE for ; Sun, 4 Apr 2004 23:23:12 -0700 (PDT) Received: from zoot.lafn.org (zoot.lafn.ORG [206.117.18.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A06C43D49 for ; Sun, 4 Apr 2004 23:23:12 -0700 (PDT) (envelope-from bc979@lafn.org) Received: from [10.0.1.90] (host-66-81-192-228.rev.o1.com [66.81.192.228]) (authenticated bits=0) by zoot.lafn.org (8.12.3p3/8.12.3) with ESMTP id i356N78a063842 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Sun, 4 Apr 2004 23:23:10 -0700 (PDT) (envelope-from bc979@lafn.org) Mime-Version: 1.0 (Apple Message framework v613) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Doug Hardie Date: Sun, 4 Apr 2004 23:23:06 -0700 To: freebsd-stable@FreeBSD.ORG X-Mailer: Apple Mail (2.613) X-Virus-Scanned: ClamAV version 'clamd / ClamAV version devel-20040209', clamav-milter version '0.66m' Subject: Reboot Problem with 5.2.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Apr 2004 06:23:12 -0000 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? -- Doug