From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Ossman Subject: Re: PCI power state mapping Date: Thu, 29 Jul 2004 13:45:41 +0200 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <4108E365.30204@drzeus.cx> References: <41069C59.5020603@drzeus.cx> <20040729084154.GH21889@openzaurus.ucw.cz> <4108D5BC.8040302@drzeus.cx> <20040729105251.GB9718@elf.ucw.cz> <4108DC59.4050409@drzeus.cx> <20040729112359.GD9718@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20040729112359.GD9718-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Pavel Machek Cc: "Li, Shaohua" , acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org Pavel Machek wrote: >Hi! > >[Please do not use html on the lists.] > > Sorry about that. This account is supposed to only send plain text. Don't know why it decided that HTML would be a good idea :/ >[me:] > > >>Okay, try suspending to disk, first. It tends to work better. Are your >>"hacks into pci_device_suspend() getting it to suspend devices without >>a driver" available somewhere? >> >> > >[you:] > > >> Suspend to disk works fine. It's just the ram-bit that won't work. >> There is an earlier thread about this with more details (search for >> "suspend-to-ram hangs on HP NX7010"). I haven't bothered making a >> patch of my changes since they do not add any functionality. If you >> have a look at pci_device_suspend() it's fairly easy to change it. >> It's a very compact and obvious function. >> >> > >Why do you think it is a driver problem? I have nx5000 here, it fails >to suspend, too, but I suspect some ACPI weirdness. Similar problem is >there on compaq 620c, btw. > Pavel > > That depends on how you define a problem. But as I see it there can only be two reasons that the suspend fails. Either the ACPI implementation or one of the drivers is not up to spec. or the system relies on some "feature" present in Windows. Not being bug-for-bug compatible with Windows might not constitute a problem in the driver per se but can still cause undesired behavior. Suspending all devices, not just those with well behaved drivers, was one thing that seemed reasonable to try. The next step would be manually putting devices into the states specified in the _SxD fields. But I haven't got the "state" files under sysfs to work yet... Rgds Pierre ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click