linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Alan Cox <alan@redhat.com>
Subject: Re: ata_std_qc_defer not good enough for FIS-based switching ?
Date: Wed, 14 May 2008 10:53:46 -0400	[thread overview]
Message-ID: <482AFCFA.40708@rtr.ca> (raw)
In-Reply-To: <482AFB12.3040005@rtr.ca>

Mark Lord wrote:
>..
> At the moment, I have the Sil PM plugged in, and it all behaves nicely.
> The previous failure was with the Marvell PM, so I'll hook that up next
> and retest with it.
..

It went bonkers again.  This is with 2.6.25.
I'll build 2.6.26-git and try again with that shortly.

One thing about sata_sil24 --> it *really* doesn't like to handle
hotplug events while in the midst of EH.

I unplugged the host cable from the PM, and the EH just kept on
going and going.

I then unplugged the sata_sil24 PCIe host adapter card,
and it still took quite some time to give up on the Energizer Bunny routine.  :)

Anyway, this is my main machine, so I'll be out for a spell now while
rebuilding/rebooting.

Cheers

  reply	other threads:[~2008-05-14 14:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28 21:06 ata_std_qc_defer not good enough for FIS-based switching ? Mark Lord
2008-04-28 22:08 ` Mark Lord
2008-04-28 23:11   ` Tejun Heo
2008-04-28 23:42     ` Mark Lord
2008-04-29  1:18       ` Tejun Heo
2008-04-29  2:26         ` Mark Lord
2008-05-14 14:11           ` Tejun Heo
2008-05-14 14:45             ` Mark Lord
2008-05-14 14:53               ` Mark Lord [this message]
2008-05-14 15:50                 ` Mark Lord
2008-05-14 15:59                   ` Mark Lord
2008-05-15  7:12                     ` Tejun Heo
2008-05-15  6:51                 ` Tejun Heo
2008-04-29 17:09     ` Mark Lord
2008-04-29 17:17       ` Mark Lord
2008-04-30  9:38       ` Tejun Heo
2008-04-30 14:02       ` Mark Lord

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