All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodney Padgett <rodney.padgett@nuth.nhs.uk>
To: linux-ide@vger.kernel.org
Subject: Re: SATA Problem: port is slow to respond
Date: Wed, 28 Mar 2007 10:15:04 +0000 (UTC)	[thread overview]
Message-ID: <loom.20070328T121013-913@post.gmane.org> (raw)
In-Reply-To: 45E69196.4070409@gmail.com

Tejun Heo <htejun <at> gmail.com> writes:

> 
> Sigmund Scheinbar wrote:
> > Tejun Heo wrote:
> >> Please apply the attached patch over 2.6.20.1 and report how it works.
> > 
> > I'm afraid that something went wrong while patching:
> 
> Sorry, it was generated against the wrong tree.  Regenerated patch attached.
> 
> > BTW.: I'm just curious, what's the "purpose" of this patch, it looks to
> > me like it is just going to ignore the problem? Or do you think that the
> > hardware is faulty?
> 
> ATAPI devices use error conditions regularly to report all sorts of
> things including media not present.  In some variants of ahci's, this
> sets seemingly unrelated error bits - JMBs set interface error and
> sb600s seem to set internal error.  These errors when interpreted
> literally require device reset to recover from thus ATAPI devices never
> get through device ready check.  So, the patch makes ahci driver
> suppress those spurious errors.
> 
I had the same problem with kernel 2.6.20.3 (from kernel.org) on the same
machine (HP dc5750). I applied your patch, and the cd drive now works! dmesg
shows no errors logged, and I can access the drive without any problem.

Thanks,

Rod.


      reply	other threads:[~2007-03-28 11:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16  9:50 SATA Problem: port is slow to respond Sigmund Scheinbar
2007-02-27 14:42 ` Tejun Heo
2007-02-27 21:26   ` Sigmund Scheinbar
2007-02-28  6:02     ` Tejun Heo
2007-03-01  8:13       ` Sigmund Scheinbar
2007-03-01  8:40         ` Tejun Heo
2007-03-28 10:15           ` Rodney Padgett [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=loom.20070328T121013-913@post.gmane.org \
    --to=rodney.padgett@nuth.nhs.uk \
    --cc=linux-ide@vger.kernel.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.