From owner-freebsd-current@FreeBSD.ORG Tue Apr 13 04:01:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2805E16A4CE for ; Tue, 13 Apr 2004 04:01:18 -0700 (PDT) Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74B7143D5F for ; Tue, 13 Apr 2004 04:01:17 -0700 (PDT) (envelope-from philip@nixsys.be) Received: from loge.nixsys.be (loge.nixsys.be [195.144.77.45]) by gateway.nixsys.be (Postfix) with ESMTP id BF61C63 for ; Tue, 13 Apr 2004 13:01:15 +0200 (CEST) Received: from loge.nixsys.be (philip@localhost [IPv6:::1]) by loge.nixsys.be (8.12.11/8.12.11) with ESMTP id i3DB1F4g045818 for ; Tue, 13 Apr 2004 13:01:15 +0200 (CEST) (envelope-from philip@loge.nixsys.be) Received: (from philip@localhost) by loge.nixsys.be (8.12.11/8.12.11/Submit) id i3DB1E1F045817 for current@freebsd.org; Tue, 13 Apr 2004 13:01:14 +0200 (CEST) (envelope-from philip) Date: Tue, 13 Apr 2004 13:01:14 +0200 From: Philip Paeps To: current@freebsd.org Message-ID: <20040413110114.GK711@loge.nixsys.be> Mail-Followup-To: current@freebsd.org References: <20040409.095635.32718566.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040409.095635.32718566.imp@bsdimp.com> X-Date-in-Rome: Idibus Aprilibus MMDCCLVII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 User-Agent: Mutt/1.5.6i Subject: Re: HEADS UP: PCI Chnages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2004 11:01:18 -0000 On 2004-04-09 09:56:35 (-0600), M. Warner Losh wrote: > I just committed some rather extensive changes to the pci bus layer. These > changes should help people that need better suspend/resume support, better > resource allocation and resource collision avoidance. I just noticed that I seem to be having a problem with my cardbus which I think might be related to your pci changes. I haven't completely dug through the cvs logs though, so I might have missed something :-) | pci0:3:3: setting power state D3 | pci0: Failed to set ACPI power state D3 on (null): AE_BAD_PARAMETER This shows up on a number of devices and is probably related to whatever the author of my bios was smoking when he was writing it. I'll read through my acpi tables and see what I can come up with. | cbb0: irq 5 at device 10.0 on pci0 | cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xf8000000 | cardbus0: on cbb0 | pccard0: <16-bit PCCard bus> on cbb0 | cbb0: bad Vcc request. ctrl=0xffffff88, status=0xffffffff | cbb_power: 0V | cbb1: irq 11 at device 10.1 on pci0 | cbb1: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xf8001000 | cardbus1: on cbb1 | pccard1: <16-bit PCCard bus> on cbb1 | cbb1: bad Vcc request. ctrl=0xffffff88, status=0xffffffff | cbb_power: 0V I have no idea what all this is supposed to mean :-) Anything I can do to help sort it out? > Let me know how well/poorly this works. Thanks Works well here. My laptop suspends/resumes almost completely happily now. Yay :-) - Philip -- Philip Paeps Please don't CC me, I am subscribed to the list. Zounds! I was never so bethumped with words since I first called my brother's father dad. -- William Shakespeare, "Kind John"