DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=KW6+VpYbiHQ6Ydw8gwLde7yLWThRHCmKt92TSM99tZ8KQlgppChCFBMMxD0RHFeUzyu9sef8AGCLFDt/Mxo30eqkMgefS152OS1bMrVEuYILzpRzRHnF3MNTeeheMo8q/T85CUakrARakLc1PC4b/jqrFvyBpY/5VvfCGjBFtco=
Message-ID: <8f53421d0802251436vd98a97h5db6b8af3dc39d0@mail.gmail.com>
Date: Tue, 26 Feb 2008 00:36:54 +0200
From: "Michael S. Tsirkin" <m.s.tsirkin@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>
Subject: Re: broken suspend in .2.6.25-rc3 on T61p (was Re: new regression in 2.6.25-rc3: no keyboard/lid acpi events on thinkpad T61p)
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
       "Andrew Morton" <akpm@linux-foundation.org>,
       LKML <linux-kernel@vger.kernel.org>,
       "Alexey Starikovskiy" <astarikovskiy@suse.de>,
       "Len Brown" <len.brown@intel.com>, linux-acpi@vger.kernel.org,
       "Jeff Garzik" <jeff@garzik.org>
In-Reply-To: <20080225222023.GK2659@elf.ucw.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <8f53421d0802251119q470a79c1p31048ef136271f84@mail.gmail.com>
	 <20080225114611.d91791f6.akpm@linux-foundation.org>
	 <8f53421d0802251245j5439b37die840e34bb293f995@mail.gmail.com>
	 <200802252157.10412.rjw@sisk.pl> <20080225212615.GA2659@elf.ucw.cz>
	 <8f53421d0802251331n31b37db8gb644dc9aa2d553d4@mail.gmail.com>
	 <20080225215049.GD2659@elf.ucw.cz>
	 <8f53421d0802251415g2033ca6bqd4e6ea9e2d93f097@mail.gmail.com>
	 <20080225222023.GK2659@elf.ucw.cz>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2323
Lines: 73

On Tue, Feb 26, 2008 at 12:20 AM, Pavel Machek <pavel@ucw.cz> wrote:
>
> Hi!
>
>  > >  > >  > commit 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2
>  > >  > >  > Author: Pavel Machek <pavel@ucw.cz>
>  > >  > >  > Date:   Thu Feb 21 13:56:55 2008 +0100
>  > >  > >  >
>  > >  > >  >     power_state: get rid of write-only variable in SATA
>  > >  > >
>  > >  > >  This is pretty unlikely to be it. Can you double check that this patch
>  > >  > >  really breaks something?
>  > >  >
>  > >  > I did and it seems to: just reverting
>  > >  > 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2 fixes resume for me.
>  > >  > 635adc28087ced0c843d2ecb6d4ae474d0e611cd which is
>  > >  > 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2~1
>  > >  > also resumes fine.
>  > >
>  > >  Hmm, I guess that should teach me about "simple cleanups".
>  > >
>  > >  Do you use any of:
>  > >
>  > >  ata/sata_inic162x.c
>  > >  ata/sata_nv.c
>  > >  ata/sata_sil24.c
>  > >
>  > >  by chance?
>  >
>  > I don't think so.
>  > Here are the only 3 ata modules I have built:
>  > drivers/ata/ahci.ko
>  > drivers/ata/ata_piix.ko
>  > drivers/ata/libata.ko
>  >
>  >
>  > ahci.c seems to look at power_state.
>  >
>  > static int ahci_pci_device_resume(struct pci_dev *pdev)
>  > {
>  >         struct ata_host *host = dev_get_drvdata(&pdev->dev);
>  >         int rc;
>  >
>  >         rc = ata_pci_device_do_resume(pdev);
>  >         if (rc)
>  >                 return rc;
>  >
>  >         if (pdev->dev.power.power_state.event == PM_EVENT_SUSPEND) {
>  >                 rc = ahci_reset_controller(host);
>  >                 if (rc)
>  >                         return rc;
>  >
>  >                 ahci_init_controller(host);
>  >         }
>
>  > Right?
>
>  Hmm, mystery partly solved... as you guessed it, this piece of code
>  was not in my tree.
>
>  (still, how can this cause autoresume after 5 seconds is a mystery to
>  me).
>
>
>                                                                 Pavel

Maybe it doesn't. Andrew saw the autoresume on -rc[2,3], I didn't.
For me, it causes resume to fail.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/