From owner-freebsd-stable@FreeBSD.ORG  Thu Dec  1 14:02:59 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
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 867BA16A41F
	for <freebsd-stable@freebsd.org>; Thu,  1 Dec 2005 14:02:59 +0000 (GMT)
	(envelope-from ducrot@poupinou.org)
Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DC45343D5A
	for <freebsd-stable@freebsd.org>; Thu,  1 Dec 2005 14:02:58 +0000 (GMT)
	(envelope-from ducrot@poupinou.org)
Received: from ducrot by poup.poupinou.org with local (Exim)
	id 1Ehp1Q-0005DE-00; Thu, 01 Dec 2005 15:02:52 +0100
Date: Thu, 1 Dec 2005 15:02:52 +0100
To: Joe Shevland <jshevland@rowantreesoftware.com.au>
Message-ID: <20051201140252.GC17066@poupinou.org>
References: <438EAF47.9010002@rowantreesoftware.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <438EAF47.9010002@rowantreesoftware.com.au>
User-Agent: Mutt/1.5.9i
From: Bruno Ducrot <ducrot@poupinou.org>
Cc: freebsd-stable@freebsd.org
Subject: Re: Lockup with powerd on amd64/tyan k8sd pro
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2005 14:02:59 -0000

On Thu, Dec 01, 2005 at 07:07:35PM +1100, Joe Shevland wrote:
> I've installed 6-stable as of about two weeks ago. I tried out using 
> powerd in 'debug' mode (adaptive by default I guess), more for my own 
> interest's sake, and it locked up the machine solid. Prior to the 
> lock-up the messages reported is was dropping through the various MHz 
> steps, and then the lock-up when it reached what I'm guessing was the 
> lowest level.

Could you post a full sysctl dev.cpu and the same with sysctl
dev.powernow?
Is the lowest frequency the only one which cause that look-up?
If you change manually the frequency via a sysctl

dev.cpu.0.freq=<something other than the lowest one>

will tell us if that's the case.

I think anyway that I found what is wrong.  I think the 2 processors are
doing a transition at the very same time, and it's possible that will
confuse the northbridge.

I don't have time to write a fix right now.  I will post a patch to be
tested latter.

Thanks,

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.