linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: Jeff Garzik <jgarzik@pobox.com>, Alan Cox <alan@redhat.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Port Multiplier drives not always all found on cold plug
Date: Sun, 18 May 2008 02:52:28 +0900	[thread overview]
Message-ID: <482F1B5C.2000006@gmail.com> (raw)
In-Reply-To: <482F16AB.1040003@rtr.ca>

Mark Lord wrote:
> Tejun Heo wrote:
>>
>> I've been studying things for last two days and discovered a number of 
>> things.  I'll soon post patch series.  Thanks a lot for digging into 
>> PMP stuff.  It's great to have someone else's eyes on this stuff.
> ..
> 
> Yeah.  It really does help when two or more people totally independently
> implement a driver on top of something like that.  For the most part,
> this stuff seems to be working rather well, though.  Good job!
> 
> Gwendal has been complaining to me about undetected drives on PMP
> with sata_mv.  My patchset to fix much of that will be posted here shortly.
> 
> But apparently, even with those fixes, he *still* has troubles,
> though not as bad as before.  I'm trying to get a nice annotated trace
> from him so we can debug that further -- could be due to some of the
> stuff you are looking at too, I suppose.

Issues I've found are...

* PMP r/w timeout is too short.  It's currently 250ms.  This is from
   SIMG PMPs and was mainly to avoid longish sequential multiple timeouts
   when access PMP regs via polled commands which is not the case
   anymore and mv 4140 needs more time occasionally.

* SDB Notify is not masked during fan-out port resets if PMP hasn't been
   reset in that pass.  This causes PMP register access failure because
   SDB Notify is received while PMP register write is in progress for
   fan-out reset.  I missed this because most of my testing was before
   PMP register access was converted to IRQ driven.

* With the above two fixed, this is peripheral but this is what
   triggered the above two on initial probes.  ata_lpm_schedule() is
   called during probe right after SCSI scan is complete which schedules
   EH immediately, reliably triggering above two on certain hardware
   combinations.

* sil3124/32 and mv4140 combination for some reason can't do NCQ
   reliably.  I don't know why.  I'll blacklist it for the time being
   and contact both companies about this.

* recovered errors shouldn't trigger resets.  (this is peripheral too
   with the first two issues fixed).

I have 8 patches to address the above issues && obscure hotplug 
problems.  I'll send the patches once after more testing.

Thanks.

-- 
tejun

  reply	other threads:[~2008-05-17 17:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 16:34 Port Multiplier drives not always all found on cold plug Mark Lord
2008-05-16 16:46 ` Mark Lord
2008-05-16 16:54   ` Mark Lord
2008-05-16 17:27     ` Mark Lord
2008-05-16 18:06       ` Mark Lord
2008-05-17 14:21         ` Tejun Heo
2008-05-17 17:32           ` Mark Lord
2008-05-17 17:52             ` Tejun Heo [this message]
2008-05-17 19:16               ` Mark Lord
2008-05-18  5:23                 ` Tejun Heo
2008-06-02  3:38                   ` JR Wilbert
2008-06-09  1:47                     ` Tejun Heo

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=482F1B5C.2000006@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=liml@rtr.ca \
    --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 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).