From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 06:10:13 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D35631065675 for ; Tue, 31 May 2011 06:10:13 +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 C28328FC25 for ; Tue, 31 May 2011 06:10:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4V6ADQe005641 for ; Tue, 31 May 2011 06:10:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4V6AD0J005640; Tue, 31 May 2011 06:10:13 GMT (envelope-from gnats) Date: Tue, 31 May 2011 06:10:13 GMT Message-Id: <201105310610.p4V6AD0J005640@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Andriy Gapon X-Mailman-Approved-At: Tue, 31 May 2011 11:34:02 +0000 Cc: Subject: Re: amd64/157386: [powerd] Enabling powerd(8) with default settings on Intel Xeon-E3 results in system freeze X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 06:10:13 -0000 The following reply was made to PR amd64/157386; it has been noted by GNATS. From: Andriy Gapon To: David Graham , bug-followup@FreeBSD.org Cc: Subject: Re: amd64/157386: [powerd] Enabling powerd(8) with default settings on Intel Xeon-E3 results in system freeze Date: Tue, 31 May 2011 09:08:48 +0300 on 29/05/2011 17:19 David Graham said the following: > On 05/29/11 01:59, Andriy Gapon wrote: >> >> Can you provide output of the dev.cpu sysctl and a snippet of devinfo command >> output that shows devices under cpu0? >> > Hi Andriy, > > ev.cpu.0.%desc: ACPI CPU > dev.cpu.0.%driver: cpu > dev.cpu.0.%location: handle=\_SB_.CP00 > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > dev.cpu.0.%parent: acpi0 > dev.cpu.0.freq: 2654 > dev.cpu.0.freq_levels: 2654/-1 2322/-1 1990/-1 1658/-1 1327/-1 995/-1 663/-1 331/-1 > dev.cpu.0.cx_supported: C1/0 > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_usage: 100.00% last 2224us > [snip] > cpu0 > acpi_throttle0 > cpufreq0 > acpi_timer0 I'd say that the problem is because of acpi_throttle driver, which is kind of dangerous and useless driver because of how it regulates frequency. I usually disable it on my Intel machines via: hint.acpi_throttle.0.disabled=1 I am a bit surprised that acpi_perf and (dependent on it) est drivers haven't attached. -- Andriy Gapon