From: Hugh Dickins <hugh@veritas.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Jeff Chua <jeffchua@silk.corp.fedex.com>,
Jeff Garzik <jeff@garzik.org>, Matt Mackall <mpm@selenic.com>,
Jens Axboe <axboe@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: sata suspend resume ...
Date: Fri, 21 Apr 2006 13:49:21 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0604211333050.4891@blonde.wat.veritas.com> (raw)
In-Reply-To: <20060420134713.GA2360@ucw.cz>
On Thu, 20 Apr 2006, Pavel Machek wrote:
> > >
> > > System suspends ok. Resume ok. but no disk access after that.
> >
> > Not the same disk model, but I've been having similar trouble on a T43p.
>
> Could you
>
> 1) try if mdelay(2000) also helps?
>
> 2) binary-search on drivers to see which one breaks it?
Thanks for looking into this. But we already know mdelay(2000) works
around it, and that the failure is "ata1: qc timeout (cmd 0xef)" when
trying to resume the SATA disk (in my case, don't know about Jeff's):
so I'm confused as to what binary search to be doing. I just tried
backing out the time.c patch I sent originally, and substituting the
patch below, much closer to the heart of the problem: that works too.
This is with ata_piix, by the way; resuming from suspend to RAM.
Do let me know what else to try if you've got an idea.
Hugh
--- 2.6.17-rc2/drivers/scsi/libata-core.c 2006-04-19 09:14:11.000000000 +0100
+++ linux/drivers/scsi/libata-core.c 2006-04-21 13:19:54.000000000 +0100
@@ -4287,6 +4287,7 @@ static int ata_start_drive(struct ata_po
int ata_device_resume(struct ata_port *ap, struct ata_device *dev)
{
if (ap->flags & ATA_FLAG_SUSPENDED) {
+ mdelay(2000);
ap->flags &= ~ATA_FLAG_SUSPENDED;
ata_set_mode(ap);
}
next prev parent reply other threads:[~2006-04-21 12:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 15:26 Jeff Chua
2006-04-19 15:52 ` Arkadiusz Miskiewicz
2006-04-20 2:18 ` Jeff Chua
2006-04-19 16:13 ` Hugh Dickins
2006-04-19 16:56 ` Arkadiusz Miskiewicz
2006-04-19 17:08 ` Hugh Dickins
2006-04-19 21:49 ` Matt Mackall
2006-04-19 22:50 ` Hugh Dickins
2006-04-19 22:57 ` Matt Mackall
2006-04-19 23:26 ` Hugh Dickins
2006-04-20 13:25 ` Arkadiusz Miskiewicz
2006-04-20 13:47 ` Pavel Machek
2006-04-21 12:49 ` Hugh Dickins [this message]
2006-04-21 16:39 ` Pavel Machek
2006-04-21 20:44 ` Hugh Dickins
2006-04-21 20:50 ` Matt Mackall
2006-04-21 21:15 ` Pavel Machek
2006-04-21 21:36 ` Jeff Garzik
2006-04-23 12:58 ` Hugh Dickins
2006-04-29 18:06 ` Hugh Dickins
2006-04-21 23:39 ` Chris Ball
2006-04-23 12:42 ` Hugh Dickins
2006-04-23 13:52 ` 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=Pine.LNX.4.64.0604211333050.4891@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=axboe@suse.de \
--cc=jeff@garzik.org \
--cc=jeffchua@silk.corp.fedex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=pavel@suse.cz \
/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®