From owner-freebsd-stable@FreeBSD.ORG Wed Nov 17 02:42:21 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 141B4106566B for ; Wed, 17 Nov 2010 02:42:21 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 8A0A08FC12 for ; Wed, 17 Nov 2010 02:42:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id oAH2gGik051633; Wed, 17 Nov 2010 13:42:16 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 17 Nov 2010 13:42:15 +1100 (EST) From: Ian Smith To: Andrew Reilly In-Reply-To: <20101115045549.GB96011@johnny.reilly.home> Message-ID: <20101117133530.H39988@sola.nimnet.asn.au> References: <20101115045549.GB96011@johnny.reilly.home> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: stable@freebsd.org Subject: Re: Console options for legacy-free mini-itx server? 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: Wed, 17 Nov 2010 02:42:21 -0000 On Mon, 15 Nov 2010, Andrew Reilly wrote: > Hi there, [..] > Oh: the other thing about this system: I can't warm-start > it, have to power down and then manually hit the power-on > button. Attempting to reboot leaves the console sitting at > something like "Stopping other CPUs" forever. I assume that > this is a BIOS config problem, but haven't found the right > control knob yet. I've tried turning hyperthreading on and off: > no difference. Reading the kernel code around that message > suggests that rebooting involves getting the keyboard controller > to send an NMI, and I wonder if the legacy-free no-keyboard > state of my system is having an effect on that, too? I really don't know if this may be relevant, but spotted in your dmesg: device_attach: acpi_perf1 attach returned 6 est0: on cpu0 p4tcc0: on cpu0 device_attach: acpi_perf1 attach returned 6 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 16 device_attach: est1 attach returned 6 p4tcc1: on cpu1 I'm used to seeing est either attach to both CPUs, or fail to attach to either CPU. Here it's attached to cpu0, but not to cpu1. Is that odd? cheers, Ian