linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Harald Arnesen <skogtun.linux@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jgarzik@redhat.com>
Subject: Re: [Bisected] Latest git will not boot on MacBook
Date: Tue, 13 May 2008 17:55:15 +0900	[thread overview]
Message-ID: <48295773.9030301@gmail.com> (raw)
In-Reply-To: <8120cfd40805100705keff68a2kb117aab7d64f76ff@mail.gmail.com>

Harald Arnesen wrote:
> See attached photo of screen.
> git bisect gives this:
> 
> 
> 78ab88f04f44bed566d51dce0c7cbfeff6449a06 is first bad commit
> commit 78ab88f04f44bed566d51dce0c7cbfeff6449a06
> Author: Tejun Heo <htejun@gmail.com>
> Date:   Thu May 1 23:41:41 2008 +0900
> 
>     libata: improve post-reset device ready test
> 
>     Some controllers (jmb and inic162x) use 0x77 and 0x7f to indicate that
>     the device isn't ready yet.  It looks like they use 0xff if device
>     presence is detected but connection isn't established.  0x77 or 0x7f
>     after connection is established and use the value from signature FIS
>     after receiving it.
> 
>     This patch implements ata_check_ready(), which takes TF status value
>     and determines whether the port is ready or not considering the above
>     and other conditions, and use it in @check_ready() functions.  This is
>     safe as both 0x77 and 0x7f aren't valid ready status value even though
>     they have BSY bit cleared.
> 
>     This fixes hot plug detection failures which can be triggered with
>     certain drives if they aren't already spun up when the data connector
>     is hot plugged.
> 
>     Tested on sil, sil24, ahci (jmb/ich), piix and inic162x combined with
>     eight drives from all major vendors.
> 
>     Signed-off-by: Tejun Heo <htejun@gmail.com>
>     Signed-off-by: Jeff Garzik <jgarzik@redhat.com>

The change was reverted and I'm trying to come up with a better version. 
  Thanks.

-- 
tejun

       reply	other threads:[~2008-05-13  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8120cfd40805100705keff68a2kb117aab7d64f76ff@mail.gmail.com>
2008-05-13  8:55 ` Tejun Heo [this message]
2008-05-13  9:26   ` [Bisected] Latest git will not boot on MacBook Harald Arnesen

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=48295773.9030301@gmail.com \
    --to=htejun@gmail.com \
    --cc=jgarzik@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skogtun.linux@gmail.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;
as well as URLs for NNTP newsgroup(s).