All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
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:41:04 -0400	[thread overview]
Message-ID: <48061E10.4000604@rtr.ca> (raw)
In-Reply-To: <4805F4E6.7020903@rtr.ca>

Mark Lord wrote:
> Tejun Heo wrote:
>> Mark Lord wrote:
> ..
>>> 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. 
> ..
> 
> So I ought to be able to insert (for debug purposes only) a msleep(3000)
> at an appropriate location in the code, and suddenly see this problem go 
> away?
> 
> Not for upstream -- the eventual hotplug support in sata_mv is the real solution.
> But just to confirm that this is indeed the issue.
..

Heh.. darned near exactly 3 seconds does it, alright.

Okay, I won't fuss over this for now -- it works if the PM is plugged in
at boot (because the BIOS fiddles it first), and it works when warmplugged
so long as sata_mv is unloaded and reloaded.

This will get fixed completely with the hotplug support fixes coming later this week.

Cheers

  reply	other threads:[~2008-04-16 15:41 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
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 [this message]
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=48061E10.4000604@rtr.ca \
    --to=liml@rtr.ca \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --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.