From: Philip Langdale <philipl@mail.utexas.edu>
To: axboe@suse.de, jgarzik@pobox.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] updated version of Jens' SATA suspend-to-ram patch
Date: Fri, 23 Sep 2005 21:28:17 -0700 [thread overview]
Message-ID: <4334D5E1.5050309@mail.utexas.edu> (raw)
Bad news regarding sata suspend/resume, thought it may not
specifically be a problem with the patch but something more
fundamental.
I have a tecra M3 which uses the i915m and ich6m chips and
as such should be very similar to various dells and ibms which
this patch works great on.
However, for my particular machine, the step of putting the
sata controller pci device into D3 locks the machine up
completely. If I skip this part of the suspend process, it
doesn't lock up. but something is clearly not right with it
as the hd will fail to wake up if I leave it suspended too
long (if it's suspended and then quickly resumed like this,
it seems to work). Putting the PCI device into D1 leads to
problems after resume regardless of the amount of time
suspended.
I disassembled the acpi DSDT and checked it for errors but
didn't find anything of note, so I'm not sure why it does
this. It's obviously not a fundamental problem because windows
can suspend fine on it, but there's clearly a piece of the
puzzle missing. It's all very frustrating because this is
the only part of the machine that can't handle suspending yet.
I tried the reformatted patch with and without Jens' workaround
but the behavour is unchanged.
--phil
next reply other threads:[~2005-09-24 4:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-24 4:28 Philip Langdale [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-23 16:33 [PATCH] updated version of Jens' SATA suspend-to-ram patch Joshua Kwan
2005-09-23 18:07 ` Jens Axboe
2005-09-23 20:23 ` Linus Torvalds
2005-09-23 20:47 ` Jeff Garzik
2005-09-23 21:11 ` Mark Lord
2005-09-23 21:21 ` Joshua Kwan
2005-09-24 7:07 ` Jens Axboe
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=4334D5E1.5050309@mail.utexas.edu \
--to=philipl@mail.utexas.edu \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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