From owner-freebsd-bugs@FreeBSD.ORG Tue May 1 15:30:16 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98F191065673 for ; Tue, 1 May 2012 15:30:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8529F8FC16 for ; Tue, 1 May 2012 15:30:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q41FUGUF084244 for ; Tue, 1 May 2012 15:30:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q41FUGea084241; Tue, 1 May 2012 15:30:16 GMT (envelope-from gnats) Date: Tue, 1 May 2012 15:30:16 GMT Message-Id: <201205011530.q41FUGea084241@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Attilio Rao Cc: Subject: Re: kern/166806: Inability to reboot system X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Attilio Rao List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2012 15:30:16 -0000 The following reply was made to PR kern/166806; it has been noted by GNATS. From: Attilio Rao To: RX Cc: bug-followup@freebsd.org Subject: Re: kern/166806: Inability to reboot system Date: Tue, 1 May 2012 16:29:19 +0100 2012/5/1, RX : > On Apr 20, 2012, at 6:17 PM, Attilio Rao wrote: > >> Are you eventually able to make some tests on that machine if I send >> you some instruction/patches? Is the problem 100% reproducible? >> Can you try by starting with showing "sysctl hw.acpi.handle_reboot" >> and force it to 0 (and see what happens)? > > > Hello Attillio, > > I have hardware dedicated to resolving this problem. > > The problem is 100% reproducible. > > The sysctl you asked for is already set to zero. > > sysctl -a |grep handle_reboot > hw.acpi.handle_reboot: 0 Can you try to update your BIOS to latest available version and see if handle_reboot changes its value? Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein