From: Mark Lord <lkml@rtr.ca>
To: Stefan Seyfried <seife@suse.de>
Cc: Tom Marshall <tommy@home.tig-grr.com>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [Suspend2-announce] Nigel's work and the future of Suspend2.
Date: Mon, 20 Mar 2006 08:24:40 -0500 [thread overview]
Message-ID: <441EAD18.8070300@rtr.ca> (raw)
In-Reply-To: <20060320081312.GA26527@suse.de>
> On Fri, Mar 17, 2006 at 10:08:46PM -0800, Tom Marshall wrote:
>
>> I have the opposite problem, more or less (S3 not swsusp):
>>
>> I have two identical (except for different model drives) Thinkpad T42
>> laptops that exhibit the same behavior. S3 mostly works but occasionally
>> fails to resume, for values of occasionally that vary between 1-2 successful
>> resumes before failure to several dozens.
>
>> If anyone is willing to work with me on tracking down the issue in a vendor
>> kernel (Ubuntu Dapper), I would be more than happy to apply debug patches
>> and supply any debug info requested.
Try Randy Dunlop's libata-acpi patches -- they cured suspend/resume (RAM)
on my (Dell) notebook, which previously suffered like your Thinkpad.
-ml
next prev parent reply other threads:[~2006-03-20 13:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 0:05 Nigel's work and the future of Suspend2 Nigel Cunningham
2006-03-07 13:14 ` [Suspend2-announce] " Thomas Maier
2006-03-08 12:25 ` Pavel Machek
2006-03-08 17:45 ` Thomas Maier
2006-03-08 20:39 ` Rafael J. Wysocki
2006-03-18 6:08 ` Tom Marshall
2006-03-20 8:13 ` Stefan Seyfried
2006-03-20 13:24 ` Mark Lord [this message]
2006-03-08 20:41 ` Pavel Machek
2006-03-09 11:33 ` Kasper Sandberg
2006-03-09 11:45 ` Pavel Machek
2006-03-09 14:55 ` Kasper Sandberg
2006-03-05 0:37 ` Pavel Machek
2006-03-09 21:34 ` Nigel Cunningham
2006-03-09 22:41 ` Pavel Machek
2006-03-10 4:53 ` Kasper Sandberg
2006-03-07 19:50 ` Bill Davidsen
2006-03-08 18:59 ` Lee Revell
2006-03-08 23:34 ` Nigel Cunningham
2006-03-08 12:21 ` Pavel Machek
2006-03-08 12:27 ` Nigel Cunningham
2006-03-08 21:55 ` Joshua Kugler
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=441EAD18.8070300@rtr.ca \
--to=lkml@rtr.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=seife@suse.de \
--cc=tommy@home.tig-grr.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