From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: PCI power state mapping Date: Thu, 29 Jul 2004 14:26:00 +0200 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20040729122600.GI9718@elf.ucw.cz> 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> <4108E365.30204@drzeus.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4108E365.30204-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Pierre Ossman Cc: "Li, Shaohua" , acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org Hi! > >> 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. > > > 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... Aha, okay, I see now. I believe it is "ACPI implementation is not up to spec or or the system relies on some "feature" present in Windows.". It might make sense to try noapic (but it does not help here). Hmm, strange. My nx5k has "interesting" bios feature when it enters some kind of bios-based-suspend-to-RAM upon pressing fn-F3... But it only works as long as you keep accessing disk (yes, strange!). It works at grub prompt, too (even without disk accessing). If disk is not accessed, normally nothing will happen, but with "noapic nolapic" it will freeze machine in similar way "echo 3 > /proc/acpi/sleep" will. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! ------------------------------------------------------- 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