From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 19 09:19:11 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A99E16A420 for ; Sun, 19 Feb 2006 09:19:11 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DCBF43D45 for ; Sun, 19 Feb 2006 09:19:09 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail27.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k1J9J8t2019124 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 19 Feb 2006 20:19:08 +1100 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k1J9J7Xp000794 for ; Sun, 19 Feb 2006 20:19:08 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k1J9J74F000793 for freebsd-amd64@freebsd.org; Sun, 19 Feb 2006 20:19:07 +1100 (EST) (envelope-from peter) Date: Sun, 19 Feb 2006 20:19:07 +1100 From: Peter Jeremy To: freebsd-amd64@freebsd.org Message-ID: <20060219091907.GA738@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Subject: Hard hang using powerd X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Feb 2006 09:19:11 -0000 I have an HP nx6125, running about a two week old 6-stable/amd64 and I've found that powerd causes random hard hangs (no response to anything except holding the power-switch down for an extended period). This occurs with both cpufreq and raw acpi frequency control. I wrote a perl script to pseudo-randomly change CPU frequency much as powerd does (but ignoring the load impact) and could trigger the problem after about 12 minutes with a buildworld happening. Has anyone else seen this problem? -- Peter Jeremy