linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Mark Lord <liml@rtr.ca>
Cc: linux-ide@vger.kernel.org, torvalds@osdl.org, axboe@suse.de
Subject: Re: [PATCH alt2] libata resume fixes
Date: Sat, 27 May 2006 15:58:43 -0400	[thread overview]
Message-ID: <4478AF73.4070007@garzik.org> (raw)
In-Reply-To: <4478AC00.1020208@rtr.ca>

Mark Lord wrote:
> Okay, here's the syslog.  Find the lines that begin with ">>>>>  ",
> and you'll see ata_pci_device_resume followed by two 
> ata_scsi_device_resume.

Thanks.


> One thought about Linus's one-liner (and the original patch),
> is that two seconds may be too short --> I'd suggest a 10-second
> timeout there for notebook drive spin-up.  Or one could be very
> paranoid and use the standard ATA 31-second timeout.
> 
> I wonder if your faster 64-bit machine had that problem?
> (two seconds not long enough, whereas my 32-bit machine is slower
> gettting to that point, so two-seconds is then enough?).

Well, there's a udelay() in there to guarantee the timing, and 64-bit 
machine is definitely newer and faster, so I doubt that would explain 
the hardlock I see.  I'll test a longer ata_busy_wait() anyway, just to 
be sure.

Overall we _really really_ need to do full controller init.  I'm 
honestly surprised the delay hack works, because the resume skips ALL of 
the controller init in piix_sata_probe().  Since the Linus patch doesn't 
touch PCS at all, it is _luck_ that the controller silicon gives you a 
useful value when it goes to PCI D0 state.

I posted a version that does full bus probe as "[PATCH alt4] libata 
resume fixes" just now.

	Jeff




      reply	other threads:[~2006-05-27 19:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-27 19:13 [PATCH alt2] libata resume fixes Jeff Garzik
2006-05-27 19:21 ` Mark Lord
2006-05-27 19:23   ` Jeff Garzik
2006-05-27 19:28     ` Mark Lord
2006-05-27 19:29       ` Jeff Garzik
2006-05-27 19:44         ` Mark Lord
2006-05-27 19:58           ` Jeff Garzik [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=4478AF73.4070007@garzik.org \
    --to=jeff@garzik.org \
    --cc=axboe@suse.de \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=torvalds@osdl.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).