All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Sebastian Greco <lkml@fliagreco.com.ar>
To: Tejun Heo <htejun@gmail.com>
Cc: Marcus Haebler <haebler@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: SATA problems
Date: Tue, 20 Feb 2007 13:24:47 -0300	[thread overview]
Message-ID: <45DB20CF.7080300@fliagreco.com.ar> (raw)
In-Reply-To: <45DB0717.90507@gmail.com>

Tejun Heo wrote:
> * Pablo, the bug you saw was bad interaction between blacklisted NCQ
> device and dynamic queue depth adjustment.  Patches are submitted to fix
> the problem.  Just drop the blacklist patch.  Your drives should work
> fine in NCQ mode.  My gut feeling is that your problem is power related
> from the beginning.
>
> * Marcus, you're on via's ahci controller, right?  The problem you saw
> was bad interaction between blacklisted NCQ _controller_ and dynamic
> queue depth adjustment.  Patches submitted.
>
> Thanks.
>
>   
I had the same problems with a new Power Supply, Now everything is ok 
with the old Power Supply and the new drives.

Pablo.

  reply	other threads:[~2007-02-20 16:25 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02 14:08 SATA problems Pablo Sebastian Greco
2007-01-03 12:20 ` Tejun Heo
2007-01-03 15:08   ` Pablo Sebastian Greco
2007-01-04  5:02     ` Tejun Heo
2007-01-04 13:17       ` Pablo Sebastian Greco
2007-01-05  3:15         ` Pablo Sebastian Greco
2007-01-08  2:23           ` Tejun Heo
2007-01-08  2:49             ` Jeff Garzik
2007-01-08 12:22             ` Pablo Sebastian Greco
2007-01-09 22:58               ` Pablo Sebastian Greco
2007-01-10  1:55                 ` Tejun Heo
2007-01-23 17:45                   ` Pablo Sebastian Greco
2007-01-24  1:54                     ` Tejun Heo
2007-02-17 12:49                       ` Marcus Haebler
2007-02-17 16:47                         ` Pablo Sebastian Greco
2007-02-20 14:35                           ` Tejun Heo
2007-02-20 16:24                             ` Pablo Sebastian Greco [this message]
2007-02-21  3:08                               ` Tejun Heo
2007-02-21 15:18                                 ` Pablo Sebastian Greco
2007-02-21  0:55                             ` Marcus Haebler
2007-02-21  3:55                               ` Tejun Heo
2007-02-21  5:57                                 ` Marcus Haebler
2007-02-21  6:24                                   ` Marcus Haebler
2007-02-21  7:25                                     ` Paul Rolland
2007-02-21 13:04                                       ` Marcus Haebler
     [not found] <8vX5T-4hg-5@gated-at.bofh.it>
     [not found] ` <8w0n1-15u-27@gated-at.bofh.it>
2007-06-14 16:58   ` Nigel Kukard
2007-06-14 17:33     ` Jeff Garzik
2007-06-18  8:05       ` Nigel Kukard
  -- strict thread matches above, loose matches on Subject: below --
2007-06-14 12:36 Nigel Kukard
2007-06-14 16:21 ` Jeff Garzik
2007-06-14 18:28   ` Dave Jones
2007-06-18 20:07     ` Dave Jones
2007-06-19  4:57       ` Nigel Kukard
2007-08-30  9:24         ` Nigel Kukard
2007-09-10  9:02           ` Andrew Morton
2007-09-13  8:55             ` Tejun Heo
2004-02-11 17:52 SATA Problems Dott. Surricani
2004-02-11 18:08 ` Armen Kaleshian
     [not found]   ` <402A72F0.9030005@surricani.cjb.net>
2004-02-11 18:25     ` Armen Kaleshian

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=45DB20CF.7080300@fliagreco.com.ar \
    --to=lkml@fliagreco.com.ar \
    --cc=haebler@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@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.