From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: Re: [Swsusp-devel] swsusp and ac status Date: Mon, 28 Jun 2004 22:25:49 +0200 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20040628202549.GI698@openzaurus.ucw.cz> References: <200406241513.i5OFDpKC003189@fermat.unipv.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <200406241513.i5OFDpKC003189-xzhXYMPkGmXoPXhRcRtihA@public.gmane.org> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Daniele Boffi Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org Hi! > > For now, in practice all ACPI modules should be unloaded prior to > > suspend and loaded on resume. > > > > I use the AC module and kernel 2.4.24 with swsusp 2.0 and it works > > fine as long as it is removed prior to suspend. > > Unloading acpi modules, suspending, resuming and loading modules > again does not help for me (2.6.7 and swsusp 2.0.0.88). > Even after resuming, if I This is known, and can be properly fixed by entering S4 (not S5; during swsusp. Some more hacky solutions are available, too. Get 2.6.7-vanilla and ask me for testing patch... -- 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com