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 <jeff@garzik.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: sata_mv & pmp support
Date: Wed, 16 Apr 2008 11:10:30 +0900	[thread overview]
Message-ID: <48056016.6020900@gmail.com> (raw)
In-Reply-To: <48055E7C.1060004@rtr.ca>

Mark Lord wrote:
> Mark Lord wrote:
>>
>> Yeah, I'm happy now.  :)
>>
>> It seems very rock solid, actually, at least on the one PM I have that 
>> works.
>> The Fed-Ex guy is due tomorrow with a fresh Marvell PM for me,
>> but I might send some stuff out for #upstream in the interim.
>>
>> Still gotta reboot/retest with a 60x1 chipset first, though.
> ..
> 
> Both command-based and FIS-based switching seem to work just fine.
> But there is a problem, maybe you could help with ?
> 
> I've just noticed that, if I unplug/replug the host-side SATA cable
> on the Sil3726 PM, and *then* "insmod sata_mv", the PM is not found.
> 
> If I then simply do "rmmod sata_mv ; insmod sata_mv", then the PM is found.
> 
> This happens with the original hardreset code from Jeff,
> as well as the updated sata_mv code that I've posted earlier.
> So it is not anything I've broken (recently :) ).
> 
> Very strange.. I wonder if it also happens with the Marvell PM,
> except I don't have one here to test with at the moment.
> 
> Ever heard of anything strange like that?

IIRC, ICH8 ahci + 4726 fails the initial reset sequence because the PMP 
comes up after the hardreset code times out, which triggers another EH 
iteration which works out fine.  If the problem is caused by the PMP not 
responding fast enough, it should cause a hotplug event afterwards. 
Maybe there's a race condition where hotplug events can be lost?

-- 
tejun

  reply	other threads:[~2008-04-16  2:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07 16:25 [PATCH #upstream 1/2] libata: kill dead code paths in reset path Tejun Heo
2008-04-07 16:46 ` [PATCH #upstream 2/2] libata: move link onlineness check out of softreset methods Tejun Heo
2008-04-12  4:35 ` [PATCH #upstream 1/2] libata: kill dead code paths in reset path Jeff Garzik
2008-04-13 16:27   ` Mark Lord
2008-04-14 20:52     ` sata_mv & pmp support Mark Lord
2008-04-15  2:01       ` Tejun Heo
2008-04-15 14:03         ` Mark Lord
2008-04-15 14:04           ` Mark Lord
     [not found]       ` <4803C850.9010901@rtr.ca>
2008-04-15  2:07         ` Tejun Heo
2008-04-15 19:59           ` Mark Lord
2008-04-15 20:14             ` Mark Lord
2008-04-15 22:36               ` Tejun Heo
2008-04-15 22:53                 ` Mark Lord
2008-04-16  2:03                   ` Mark Lord
2008-04-16  2:10                     ` Tejun Heo [this message]
2008-04-16  7:05                       ` Gwendal Grignou
2008-04-16 12:43                         ` Mark Lord
2008-04-16 12:37                       ` Mark Lord
2008-04-16 12:45                       ` Mark Lord
2008-04-16 15:41                         ` Mark Lord
2008-04-16 22:19                           ` 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=48056016.6020900@gmail.com \
    --to=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --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).