public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@mellanox.co.il>
To: Pavel Machek <pavel@suse.cz>
Cc: Andrew Morton <akpm@osdl.org>, Jeff Garzik <jeff@garzik.org>,
	linux-pm@osdl.org,
	Thomas Glanzmann <sithglan@stud.uni-erlangen.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org
Subject: Re: T60 not coming out of suspend to RAM
Date: Wed, 30 Aug 2006 18:05:36 +0300	[thread overview]
Message-ID: <20060830150535.GA30172@mellanox.co.il> (raw)
In-Reply-To: <20060830144646.GC1923@elf.ucw.cz>

Quoting r. Pavel Machek <pavel@suse.cz>:
> Subject: Re: T60 not coming out of suspend to RAM
> 
> Hi!
> 
> > > > > > OK, it turns out the problem was with running SATA drive in AHCI mode.
> > > > > > 
> > > > > > After applying the following patch from Forrest Zhao
> > > > > > http://lkml.org/lkml/2006/7/20/56
> > > > > > both suspend to disk and suspend to ram work fine now.
> > > > > > This patch is going into 2.6.18, isn't it?
> > > > > 
> > > > > Not sure, check latest -rc5, and if it is not there, ask akpm...
> > > > > 
> > > > 
> > > > Andrew, this is going into 2.6.18, isn't it? I don't see it in -rc5.
> > > > 
> > > 
> > > It looks like Forrest's stuff is all queued up in the libata devel tree,
> > > although in a significantly different-looking form.
> > > 
> > > So no, right now it doesn't look good for 2.6.18.
> > > 
> > 
> > Ugh, more's the pity :( How about merging this one patch? T60 is only half
> > as useful without it (no disk after resume), and the rate of changes in
> > libata is high so just using a patch is gonnu be painful in the long run.
> 
> I guess you need to convince SATA maintainer that patch is safe before
> it can go in...

Right.

Jeff, could you please ack whether the following patch from Forrest Zhao
is safe for 2.6.18?
http://lkml.org/lkml/2006/7/20/56

Without it, no disk access is possible after resume from suspend-to-ram
on my T60.

-- 
MST

      reply	other threads:[~2006-08-30 15:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 10:37 T60 not coming out of suspend to RAM Michael S. Tsirkin
2006-08-25 11:04 ` Pavel Machek
2006-08-28 13:53   ` Michael S. Tsirkin
2006-08-28 15:42     ` Pavel Machek
2006-08-28 17:19       ` Michael S. Tsirkin
2006-08-28 19:25         ` Andrew Morton
2006-08-28 20:19           ` Michael S. Tsirkin
2006-08-30 14:46             ` Pavel Machek
2006-08-30 15:05               ` Michael S. Tsirkin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060830150535.GA30172@mellanox.co.il \
    --to=mst@mellanox.co.il \
    --cc=akpm@osdl.org \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@osdl.org \
    --cc=pavel@suse.cz \
    --cc=sithglan@stud.uni-erlangen.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox