From owner-freebsd-acpi@FreeBSD.ORG  Thu Nov 18 00:36:50 2004
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 244CA16A4CE; Thu, 18 Nov 2004 00:36:50 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B91F843D31; Thu, 18 Nov 2004 00:36:49 +0000 (GMT)
	(envelope-from imp@harmony.village.org)
Received: from localhost (localhost [IPv6:::1])
	by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAI0Y91v059494;
	Wed, 17 Nov 2004 17:34:10 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Date: Wed, 17 Nov 2004 17:34:09 -0700 (MST)
Message-Id: <20041117.173409.104092741.imp@harmony.village.org>
To: oberman@es.net
From: Warner Losh <imp@harmony.village.org>
In-Reply-To: <20041117211943.E583E5D0A@ptavv.es.net>
References: <419BB117.4070802@root.org>
	<20041117211943.E583E5D0A@ptavv.es.net>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-acpi@FreeBSD.org
cc: freebsd-current@FreeBSD.org
cc: sos@DeepCore.dk
Subject: Re: [PATCH] Please test: new ACPI release (20041105) import 
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Nov 2004 00:36:50 -0000

> I do suspect that this is a PCI power issue and not an ACPI issue, but
> I'd like to know if it shows up on more models. It is most obvious when
> playing a stream as the buffers keep emptying and the sound stops after
> a short time. Music is clearly too fast and high pitched, but at 10%
> overspeed, some may not notice. (Does Dr. Dre sound much different 10%
> faster?)

I've flipped the sense of the PCI power sysctl in current.  Once
that's sanner, we should investigate setting the power states on
resume.  Not sure what to do about suspend, since I think that acpi
has different notions of what D level to put a device in for different
S levels and it would likely have to take care of that after giving
the device a chance to save state.

Warner