From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Jeff Chua <jchua@fedex.com>
Cc: lkml@rtr.ca, jeff.chua.linux@gmail.com, hugh@veritas.com,
cjb@mrao.cam.ac.uk, pavel@suse.cz, arekm@maven.pl,
jeff@garzik.org, mpm@selenic.com, axboe@suse.de,
randy_d_dunlap@linux.intel.com, linux-kernel@vger.kernel.org,
ncunningham@linuxmail.org
Subject: Re: sata suspend resume ... (fwd)
Date: Tue, 25 Apr 2006 21:38:41 -0700 [thread overview]
Message-ID: <20060425213841.63f0641e.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0604250810370.5533@boston.corp.fedex.com>
On Tue, 25 Apr 2006 08:54:21 +0800 (SGT) Jeff Chua wrote:
>
> On Sun, 23 Apr 2006, Mark Lord wrote:
>
> > Try Randy Dunlop's libata-acpi patches -- I've been using variants of them
> > for a *very long time* here now, as they're the only thing that works for me.
>
> This the one that makes does it!!! I've tried just about all patches
> including the famous "mdelay(2000);" but none worked. ... perhaps it's
> just something to do with IBM X60s which is dual-core.
>
> Here's what I did to make it work...
>
> Linux is vanilla linux-2.6.17-rc2.
>
> Pavel suggested the right step as I was going no where with SMP suspend.
> Switching to UP and using "suspend2" (CONFIG_SUSPEND2) didn't work either
> with PIIX or AHCI. Patch is suspend2-2.2.5-for-2.6.17-rc2.tar.bz2
>
> Then I tried "suspend" (CONFIG_SOFTWARE_SUSPEND) with both PIIX and
> AHIC in UP mode ... still didn't work.
>
> Next, I applied libata-acpi.patch with a little modification. No sure
> what the implication is but the original patch seems to use "i" outside
> the loop. Here's what I added to libata-acpi.patch ... can someone verify
> this or do we need this at all?
>
> +
> + for (i = 0; i < ATA_MAX_DEVICES; i++)
> + ata_acpi_push_id(ap, i);
Yes, that looks appropriate. The function that code lives in
has changed quite a bit since this patch was written.
> Tried both PIIX and AHCI in UP mode. Failed with AHCI, but worked in
> "suspend to disk" in PIIX mode (configured in BIOS under SATA ->
> "COMPATIBILITY").
---
~Randy
next prev parent reply other threads:[~2006-04-26 4:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 13:54 Jeff Chua
2006-04-24 1:21 ` Mark Lord
2006-04-24 7:41 ` Jeff Chua
2006-04-25 0:54 ` Jeff Chua
2006-04-25 8:29 ` Pavel Machek
2006-04-26 4:38 ` Randy.Dunlap [this message]
2006-04-24 7:55 ` Pavel Machek
2006-04-24 8:55 ` Jens Axboe
2006-04-25 0:07 ` Jeff Chua
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=20060425213841.63f0641e.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=arekm@maven.pl \
--cc=axboe@suse.de \
--cc=cjb@mrao.cam.ac.uk \
--cc=hugh@veritas.com \
--cc=jchua@fedex.com \
--cc=jeff.chua.linux@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=mpm@selenic.com \
--cc=ncunningham@linuxmail.org \
--cc=pavel@suse.cz \
--cc=randy_d_dunlap@linux.intel.com \
/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
all inboxes | Powered by JetHome®