From: Tejun Heo <htejun@gmail.com>
To: Brian & Chamaigne Scamman <scammanbc@earthlink.net>
Cc: 'Mark Lord' <liml@rtr.ca>, jeff@garzik.org, linux-ide@vger.kernel.org
Subject: Re: [PATCHSET #upstream-fixes] git tree available
Date: Tue, 20 May 2008 23:50:10 +0900 [thread overview]
Message-ID: <4832E522.50107@gmail.com> (raw)
In-Reply-To: <006f01c8ba72$3ac5d1a0$6917a8c0@parents>
Brian & Chamaigne Scamman wrote:
> Tejun Heo wrote:
>> Can you please describe what you did exactly? sil3726/4726 has some
>> problems when its first fan out port goes online and offline while it's
>> powered up. You want to keep it occupied at all times.
>>
> Here's the current setup:
> - PMP powered via computer's power supply; on with computer
> - SSD and bridges powered via computer's power supply; on with computer
> - FC9 with new 2.6.26-rc2-hotplug-patches installed and booted
> - Once computer is booted, login, open a terminal and dmesg -c
> For the case which fails:
> - plug SSD drive/bridge into PMP port 0
> - plug eSata cable into PMP
> - plug eSata cable into eSata port on controller
> - watch the softreset timeout
> For the case which works:
> - plug eSata cable into PMP
> - plug eSata cable into eSata port on controller
> - watch the PMP become recognized
> - plug SSD drive/bridge into PMP port 0
> - watch the SSD drive become recognized
>
> Steps above are repeatable. Previously I was applying power to the PMP while
> the drives were attached (PMP, bridges and drives all receiving power at the
> same time) and then plugging in the eSata cable, but this case always failed
> as well.
>
>> Also, does putting sslep(5) right before followup-SRST help?
>>
> I'll look at adding the sslep line and the new patch (independently).
Please try the patch. I think that should work.
--
tejun
prev parent reply other threads:[~2008-05-20 14:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 16:15 [PATCHSET #upstream-fixes] libata: fix a bunch of PMP related problems Tejun Heo
2008-05-18 16:15 ` [PATCH 01/10] libata: fix sata_link_hardreset() @online out parameter handling Tejun Heo
2008-05-19 21:53 ` Jeff Garzik
2008-05-18 16:15 ` [PATCH 02/10] libata: reorganize ata_eh_reset() no reset method path Tejun Heo
2008-05-18 16:15 ` [PATCH 03/10] libata: move reset freeze/thaw handling into ata_eh_reset() Tejun Heo
2008-05-18 16:15 ` [PATCH 04/10] libata: kill hotplug related race condition Tejun Heo
2008-05-18 16:15 ` [PATCH 05/10] libata: ignore recovered PHY errors Tejun Heo
2008-05-19 21:50 ` Jeff Garzik
2008-05-18 16:15 ` [PATCH 06/10] libata: increase PMP register access timeout to 3s Tejun Heo
2008-05-18 16:15 ` [PATCH 07/10] libata: make sure PMP notification is turned off during recovery Tejun Heo
2008-05-18 16:15 ` [PATCH 08/10] libata: don't schedule LPM action seperately during probing Tejun Heo
2008-05-18 16:15 ` [PATCH 09/10] sata_sil24: don't use NCQ if marvell 4140 PMP is attached Tejun Heo
2008-05-18 21:14 ` Mark Lord
2008-05-18 16:15 ` [PATCH 10/10] libata: ignore SIMG4726 config pseudo device Tejun Heo
2008-05-18 16:29 ` [PATCHSET #upstream-fixes] git tree available Tejun Heo
2008-05-20 1:35 ` Brian & Chamaigne Scamman
2008-05-20 2:58 ` Mark Lord
2008-05-20 4:28 ` Tejun Heo
2008-05-20 4:43 ` Tejun Heo
2008-05-21 1:32 ` Brian & Chamaigne Scamman
2008-05-21 4:59 ` Tejun Heo
2008-05-21 11:14 ` Brian & Chamaigne Scamman
2008-05-21 19:42 ` Brian & Chamaigne Scamman
2008-05-22 0:40 ` Tejun Heo
2008-05-23 0:49 ` Brian & Chamaigne Scamman
2008-05-23 1:04 ` Tejun Heo
2008-05-29 3:06 ` Tejun Heo
2008-05-29 3:11 ` Brian & Chamaigne Scamman
2008-05-20 12:08 ` Brian & Chamaigne Scamman
2008-05-20 14:50 ` Tejun Heo [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=4832E522.50107@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=scammanbc@earthlink.net \
/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).