From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Piggin Subject: Re: [PM][ACPI] No ACPI interrupts after resume from S1 Date: Fri, 24 Oct 2003 20:24:31 +1000 Sender: linux-kernel-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Message-ID: <3F98FDDF.1040905@cyberone.com.au> References: <20031020141512.GA30157@hell.org.pl> <20031020184750.GA26154@hell.org.pl> <20031023082534.GD643@openzaurus.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: To: =?ISO-8859-1?Q?M=E5ns_Rullg=E5rd?= Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org M=E5ns Rullg=E5rd wrote: >Pavel Machek writes: > > >>>>>suspend, the extra buttons (I use them to fire up programs) stop >>>>>working. Normally, they will generate an ACPI event, that is >>>>>processed by acpid etc. After a suspend, each button will work on= ce. >>>>>If I then close and open the lid, they will work one more time, an= d so >>>>>on. Any way I can help? >>>>> >>>>Please specify the type of suspend. The situation I described >>>>only occurs for S1 (or, echo -n standby, more specifically), and >>>>only in certain kernel versions. >>>> >>>standby, at least. >>> >>>After echo -n mem > /sys/power/state, the display light won't turn o= n, >>>so I don't know what's going on. I've never managed to resume from = a >>>suspend to disk. It just boots normally and makes a fuss about the >>>filesystems. >>> >>Are you passing resume=3D option? >> > >I've been trying the new suspend to disk implementation (pmdisk, I >think) lately. I get these lines in the kernel log when starting >after a suspend: > >PM: Reading pmdisk image. >PM: Resume from disk failed. >ACPI: (supports S0 S1 S3 S4 S5) > >Last time I tried swsusp, I did pass the resume=3D option, but it didn= 't >work. > >Could it be that some disk cache is never flushed properly? >Occasionally, some random filesystem is reported as not being cleanly >unmounted when booting normally, which seems to point in the same >direction. > Try turning your disk cache off, or set it to write through caching (even so I heard some IDE drives don't turn it off anyway!). See if it helps.