From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: "zhao, forrest" <forrest.zhao@intel.com>,
linux-ide@vger.kernel.org, Hannes Reinecke <hare@suse.de>
Subject: Re: ata_piix resume from S3 on T43P failed
Date: Sat, 13 May 2006 00:19:12 -0400 [thread overview]
Message-ID: <44655E40.2090004@garzik.org> (raw)
In-Reply-To: <4462F667.3060504@gmail.com>
Tejun Heo wrote:
> zhao, forrest wrote:
>> Hi, Tejun
>>
>> We just tested your git tree on thinkpad T43P laptop, and found that
>> after ata_piix resumed from S3, SATA disk can't be read/write anymore.
>> But according to the test result of kernel 2.6.16-rc6 on T43P, ata_piix
>> can resume from S3 successfully.
>>
>> We know that this problem may be not related to your patches, but I
>> think you know the libata development status very well, maybe you can
>> give us some clue about what happened to ata_piix between 2.6.16-rc6 and
>> your git tree.
>>
>
> Hello, Zhao.
>
> I haven't really followed AHCI suspend/resume stuff but AFAICT it never
> made to #upstream. I don't know whether it was included in -rc# or not.
> But it sounds like it did.
Hannes @ SuSE posted an AHCI suspend/resume patch that needs to go in.
Unfortunately AHCI is a high rate of churn, so it's still in my
'Pending' folder :/
Jeff
next prev parent reply other threads:[~2006-05-13 4:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 8:05 ata_piix resume from S3 on T43P failed zhao, forrest
2006-05-11 8:31 ` Tejun Heo
2006-05-11 8:35 ` Tejun Heo
2006-05-11 9:46 ` zhao, forrest
2006-05-11 10:39 ` Tejun Heo
2006-05-12 5:02 ` zhao, forrest
2006-05-11 10:55 ` Jens Axboe
2006-05-12 5:51 ` zhao, forrest
2006-05-12 10:17 ` Jens Axboe
2006-05-12 10:56 ` Tejun Heo
2006-05-16 3:56 ` zhao, forrest
2006-05-17 11:03 ` Jens Axboe
2006-05-17 12:56 ` Jeff Garzik
2006-05-17 13:02 ` Jens Axboe
2006-05-22 7:32 ` Jeff Garzik
2006-05-13 4:19 ` Jeff Garzik [this message]
2006-05-16 1:58 ` zhao, forrest
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=44655E40.2090004@garzik.org \
--to=jeff@garzik.org \
--cc=forrest.zhao@intel.com \
--cc=hare@suse.de \
--cc=htejun@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.