From owner-freebsd-acpi@FreeBSD.ORG  Wed Nov 24 07:26:10 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 37C4F16A4CE
	for <acpi@freebsd.org>; Wed, 24 Nov 2004 07:26:10 +0000 (GMT)
Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C5DAE43D5C
	for <acpi@freebsd.org>; Wed, 24 Nov 2004 07:26:09 +0000 (GMT)
	(envelope-from nate@root.org)
Received: from [10.0.5.50] (adsl-64-171-186-185.dsl.snfc21.pacbell.net
	[64.171.186.185])iAO7Q9p8019372;	Wed, 24 Nov 2004 02:26:11 -0500
Message-ID: <41A43787.7070809@root.org>
Date: Tue, 23 Nov 2004 23:25:59 -0800
From: Nate Lawson <nate@root.org>
User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "M. Warner Losh" <imp@bsdimp.com>
References: <419EF7AD.8050007@root.org>
	<20041121.081521.102766341.imp@bsdimp.com>
In-Reply-To: <20041121.081521.102766341.imp@bsdimp.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: acpi@freebsd.org
Subject: Re: PATCH: power down acpi and pci devices in suspend/resume
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: Wed, 24 Nov 2004 07:26:10 -0000

M. Warner Losh wrote:
> In message: <419EF7AD.8050007@root.org>
>             Nate Lawson <nate@root.org> writes:
> : cbb0: bad Vcc request. ctrl=0xffffff88, status=0xffffffff
> : cbb_power: 0V
> : cbb1: bad Vcc request. ctrl=0xffffff88, status=0xffffffff
> : cbb_power: 0V
> 
> This looks like a problem to me.
> 
> Warner

I did a suspend with dhclient active and an an0 card present and got this:

cbb0: bad Vcc request. ctrl=0xffffff88, status=0xffffffff
cbb_power: 0V
cbb1: bad Vcc request. ctrl=0xffffff88, status=0xffffffff
cbb_power: 0V
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: DMA timeout
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: DMA timeout
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: DMA timeout
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: DMA timeout
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: DMA timeout
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: DMA timeout
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff
fxp0: SCB timeout: 0xff 0xff 0xff 0xffff

Note that the policy is to set all PCI and ACPI devices to D3 when 
suspending unless an _SxD method says to use a different power state. 
fxp0 isn't present in the ACPI namespace but both cardbus ports are and 
both have _S3D methods that say to use D3 for S3!  So this is not an 
error unless it's in cbb needing to do more before I power it down.  I 
don't get any of the above messages on suspend without my patch.

Suggestions?  What does the "bad Vcc request" message mean?

-Nate