All of lore.kernel.org
 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
Subject: Re: [PATCH alt4 v3] libata resume fixes
Date: Sat, 27 May 2006 17:21:13 -0400	[thread overview]
Message-ID: <4478C2C9.3030703@garzik.org> (raw)
In-Reply-To: <4478C0A1.4050003@rtr.ca>

Mark Lord wrote:
> The alt4_v3 patch from Jeff also still fails here.
> 
> The screen stays off for 30 seconds, then comes on,
> but the error-recovery attempts do NOT appear in the syslog
> as they did with the alt4_v2 patch.  The disk LED is still
> stuck on, and the syslog shows only this, from early on:
> 
> qc timeout (cmd 0xe1)
> do_simple_cmd: ata command failed: 4

0xE1 is IDLE IMMEDIATE, so it looks like it is making progress.

This makes me realize that ata_bus_probe() won't get the job done alone, 
we must do:

* host init
* phy init
* idle immediate
* the rest of bus probe

Good, good data points here...

	Jeff





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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-27 19:58 [PATCH alt4] libata resume fixes Jeff Garzik
2006-05-27 20:10 ` [PATCH alt4 v2] " Jeff Garzik
2006-05-27 20:14   ` Jeff Garzik
2006-05-27 20:30     ` Mark Lord
     [not found]     ` <4478B611.2030201@rtr.ca>
2006-05-27 20:32       ` Jeff Garzik
2006-05-27 20:41         ` Mark Lord
2006-05-27 20:56           ` Jeff Garzik
2006-05-27 21:00             ` Mark Lord
2006-05-27 21:06               ` Jeff Garzik
2006-05-27 21:09                 ` Mark Lord
2006-05-27 21:14                   ` Jeff Garzik
2006-05-27 20:13 ` [PATCH alt4] " Mark Lord
2006-05-27 20:52 ` [PATCH alt4 v3] " Jeff Garzik
2006-05-27 20:56   ` Mark Lord
2006-05-27 21:11     ` Jeff Garzik
2006-05-27 21:15       ` Mark Lord
2006-05-27 21:25         ` Jeff Garzik
2006-05-27 21:12     ` Mark Lord
2006-05-27 21:21       ` Jeff Garzik [this message]
2006-05-29  3:53         ` zhao, forrest
2006-05-29  5:25           ` Jeff Garzik

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=4478C2C9.3030703@garzik.org \
    --to=jeff@garzik.org \
    --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 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.