From: Tejun Heo <htejun@gmail.com>
To: Brian Keck <bwkeck@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: slow resume from s2ram
Date: Wed, 06 Feb 2008 15:49:24 +0900 [thread overview]
Message-ID: <47A95874.60601@gmail.com> (raw)
In-Reply-To: <20080205130931.56F31E2B10@vilya.x>
Brian Keck wrote:
> Hello,
>
> I can't get my otherwise lovely debian/sid Vaio TX17 to resume promptly
> from suspend-to-ram.
>
> Until recently it resumed at all maybe 1 in 4 times from
> 's2ram -f -p' in X, always taking several minutes, apparently
> due to the hard disk (1.8" Toshiba HDD1544/MK6006GAH).
>
> Last week I tried 2 things:
>
> * added /etc/modprobe.d/libata with
> options libata noacpi=0
>
> * built a kernel + initrd from debian linux-source-2.6.24 with
> CONFIG_BLK_DEV_IDEACPI=y
>
> This boots OK, with ...
>
> $ cat /sys/module/libata/parameters/noacpi
> 0
You're not using libata at all. You're using IDE driver instead.
Please try libata ata_piix driver instead.
--
tejun
prev parent reply other threads:[~2008-02-06 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 13:09 slow resume from s2ram Brian Keck
2008-02-06 6:49 ` Tejun Heo [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=47A95874.60601@gmail.com \
--to=htejun@gmail.com \
--cc=bwkeck@gmail.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).