From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 24 15:03:49 2004 Return-Path: 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 E21A616A4CE for ; Wed, 24 Nov 2004 15:03:49 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08C1D43D49 for ; Wed, 24 Nov 2004 15:03:49 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAOF206G053739; Wed, 24 Nov 2004 08:02:00 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 24 Nov 2004 08:02:40 -0700 (MST) Message-Id: <20041124.080240.60195009.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <41A43787.7070809@root.org> References: <419EF7AD.8050007@root.org> <20041121.081521.102766341.imp@bsdimp.com> <41A43787.7070809@root.org> 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 15:03:50 -0000 In message: <41A43787.7070809@root.org> Nate Lawson writes: : M. Warner Losh wrote: : > In message: <419EF7AD.8050007@root.org> : > Nate Lawson 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? At a guess, I'd say that we're accessing the hardware after the power state has been set to d3, likely via an interrupt. 'bad Vcc request' is just a bit that's set in the pccbb hardware. It is almost never right, especially with the status of 0xffffffff. Warner