From: "zhao, forrest" <forrest.zhao@intel.com>
To: Tejun Heo <htejun@gmail.com>
Cc: jgarzik@pobox.com, alan@lxorguk.ukuu.org.uk, axboe@suse.de,
albertcc@tw.ibm.com, lkosewsk@gmail.com,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 08/14] libata-eh: implement ata_eh_revive()
Date: Wed, 19 Apr 2006 17:08:41 +0800 [thread overview]
Message-ID: <1145437721.3417.16.camel@forrest26.sh.intel.com> (raw)
In-Reply-To: <11447633023982-git-send-email-htejun@gmail.com>
On Tue, 2006-04-11 at 22:48 +0900, Tejun Heo wrote:
> +
> +/**
> + * ata_eh_revive - revive host port after error
> + * @ap: host port to revive
> + * @action: action to perform to revive @ap
> + * @softreset: softreset method (can be NULL)
> + * @hardreset: hardreset method (can be NULL)
> + * @postreset: postreset method (can be NULL)
> + *
> + * Perform action specified by @action to revive host port @ap
> + * after error.
> + *
> + * LOCKING:
> + * Kernel thread context (may sleep).
> + */
> +int ata_eh_revive(struct ata_port *ap, unsigned int action,
> + ata_reset_fn_t softreset, ata_reset_fn_t hardreset,
> + ata_postreset_fn_t postreset)
> +{
> + int scr_valid = ap->cbl == ATA_CBL_SATA && ap->ops->scr_read;
> + unsigned int classes[ATA_MAX_DEVICES];
> + int tries[ATA_MAX_DEVICES], reset_tries, nr_enabled;
> + struct ata_device *dev;
> + ata_reset_fn_t reset;
> + int i, down_xfermask, rc = 0;
> +
> + if (!action)
> + goto out;
> +
> + reset_tries = ATA_EH_MAX_TRIES;
> + nr_enabled = 0;
> + for (i = 0; i < ATA_MAX_DEVICES; i++) {
> + tries[i] = ATA_EH_MAX_TRIES;
> + if (ata_dev_enabled(&ap->device[i]))
> + nr_enabled++;
> + }
> +
> + /* revalidate */
> + if (action == ATA_PORT_REVALIDATE) {
> + for (i = 0; i < ATA_MAX_DEVICES; i++) {
> + struct ata_device *dev = &ap->device[i];
> + if (!ata_dev_enabled(dev) ||
> + !(dev->flags & ATA_DFLAG_FAILED))
> + continue;
> + if (ata_dev_revalidate(ap, dev, 0))
> + break;
> + }
> + if (i == ATA_MAX_DEVICES) {
> + rc = 0;
> + goto out;
> + }
> +
> + action |= ATA_PORT_SOFTRESET;
> + }
> + action &= ~ATA_PORT_REVALIDATE;
> +
> + /* Skip reset if possible. */
> + if (!nr_enabled && !(ap->flags & ATA_FLAG_FROZEN))
> + goto out;
> +
> + /* give devices some time to breath */
> + ata_eh_wait_before_reset(ap);
> +
> + if (softreset && (!hardreset || (!ata_set_sata_spd_needed(ap) &&
> + action == ATA_PORT_SOFTRESET)))
> + reset = softreset;
> + else
> + reset = hardreset;
> +
> + retry:
> + down_xfermask = 0;
> +
> + /* reset. postreset is responsible for thawing the port. */
> + printk("ata%u: %s resetting channel for error handling\n",
> + ap->id, reset == softreset ? "soft" : "hard");
> +
> + rc = ata_do_reset(ap, reset, postreset, classes);
> + if (rc)
> + goto fail_reset;
> +
> + /* revalidate and reconfigure devices */
> + for (i = 0; i < ATA_MAX_DEVICES; i++) {
> + dev = &ap->device[i];
> +
> + if (!ata_dev_enabled(dev))
> + continue;
> +
> + if (scr_valid && !sata_dev_present(ap)) {
> + rc = -EIO;
> + goto fail;
> + }
> +
> + rc = ata_dev_revalidate(ap, dev, 1);
> + if (rc)
> + goto fail;
> + }
> +
> + /* configure transfer mode */
> + if (ap->ops->set_mode) {
> + /* FIXME: make ->set_mode handle no device case and
> + * return error code and failing device on failure as
> + * ata_set_mode() does.
> + */
> + for (i = 0; i < ATA_MAX_DEVICES; i++)
> + if (ata_dev_enabled(&ap->device[i])) {
> + ap->ops->set_mode(ap);
> + break;
> + }
> + rc = 0;
> + } else
> + rc = ata_set_mode(ap, &dev);
> +
> + if (rc) {
> + down_xfermask = 1;
> + goto fail;
> + }
> +
> + goto out;
> +
> + fail_reset:
> + if (!--reset_tries) {
> + printk(KERN_ERR "ata%u: EH reset failed, giving up\n", ap->id);
> + goto out;
> + }
> + if (reset == hardreset)
> + ata_down_sata_spd_limit(ap);
> + if (hardreset)
> + reset = hardreset;
> +
> + printk(KERN_WARNING "ata%u: EH reset failed, will retry in 5 secs\n",
> + ap->id);
> + ssleep(5);
> + goto retry;
> +
> + fail:
> + switch (rc) {
> + case -EINVAL:
> + case -ENODEV:
> + tries[dev->devno] = 0;
> + break;
> + case -EIO:
> + ata_down_sata_spd_limit(ap);
> + default:
> + tries[dev->devno]--;
> + if (down_xfermask &&
> + ata_down_xfermask_limit(ap, dev, tries[dev->devno] == 1))
> + tries[dev->devno] = 0;
> + }
> +
> + if (!tries[dev->devno]) {
> + ata_dev_disable(ap, dev);
> + nr_enabled--;
> + }
> +
> + if (nr_enabled) {
> + printk(KERN_WARNING "ata%u: some devices seem to be offline, "
> + "will retry in 5 secs\n", ap->id);
> + ssleep(5);
> + } else {
> + /* no device left, repeat fast */
> + msleep(500);
> + }
> +
> + if (hardreset)
> + reset = hardreset;
> + goto retry;
> +
> + out:
> + for (i = 0; i < ATA_MAX_DEVICES; i++) {
> + dev = &ap->device[i];
> + dev->flags &= ~ATA_DFLAG_FAILED;
> + if (rc)
> + ata_dev_disable(ap, dev);
> + }
> +
> + return rc;
> +}
Tejun,
I did some initial hotplug test in our lab today. And
this is the printk output in dmesg when I unplug the
SATA disk at port 2:
ata2: stat 0x50 err 0x0 SError 0x90402 action 0x2
(irq_stat 0x04400000, PHY RDY changed)
ata2: soft resetting channel for error handling
ata2: SATA link down (SStatus 21 SControl 300)
ata2: limiting SATA link speed to 1.5 Gbps
ata2: some devices seem to be offline, will retry in 5 secs
ata2: hard resetting channel for error handling
ata2: SATA link down (SStatus 0 SControl 310)
ata2: some devices seem to be offline, will retry in 5 secs
ata2: hard resetting channel for error handling
ata2: SATA link down (SStatus 0 SControl 310)
ata2: dev 0 disabled
// why hard reset again??
ata2: hard resetting channel for error handling
ata2: SATA link down (SStatus 0 SControl 310)
// ??
ata2: dev 0 detaching (SCSI 1:0:0:0)
My question is: why hard-reset is executed again after
dev0 at ata2 has been disabled?
Could you help me understand the idea behind this logic?
Thanks,
Forrest
next prev parent reply other threads:[~2006-04-19 9:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 13:48 [PATCHSET 6/9] new EH implementation, take 2 Tejun Heo
2006-04-11 13:48 ` [PATCH 03/14] libata-eh: add per-dev ata_ering Tejun Heo
2006-04-11 13:48 ` [PATCH 07/14] libata-eh: implement ata_eh_report() Tejun Heo
2006-04-11 13:48 ` [PATCH 11/14] ata_piix: convert to new EH Tejun Heo
2006-04-11 13:48 ` [PATCH 01/14] libata-eh: add constants and flags to be used by EH Tejun Heo
2006-04-11 13:48 ` [PATCH 08/14] libata-eh: implement ata_eh_revive() Tejun Heo
2006-04-19 9:08 ` zhao, forrest [this message]
2006-04-19 10:33 ` Tejun Heo
2006-04-11 13:48 ` [PATCH 04/14] libata-eh: implement EH utility functions Tejun Heo
2006-04-11 13:48 ` [PATCH 10/14] libata-eh: implement EH methods for BMDMA controllers Tejun Heo
2006-04-11 13:48 ` [PATCH 09/14] libata-eh: implement ata_eh_finish_qcs() Tejun Heo
2006-04-11 13:48 ` [PATCH 02/14] libata-eh: implement ata_ering Tejun Heo
2006-04-11 13:48 ` [PATCH 06/14] libata-eh: implement ata_eh_autopsy() Tejun Heo
2006-04-11 13:48 ` [PATCH 05/14] libata-eh: implement ata_eh_determine_qc() Tejun Heo
2006-04-11 13:48 ` [PATCH 14/14] sata_sil24: convert to new EH Tejun Heo
2006-04-11 13:48 ` [PATCH 13/14] ahci: " Tejun Heo
2006-04-20 6:01 ` zhao, forrest
2006-04-20 7:11 ` Tejun Heo
2006-04-20 7:44 ` Jeff Garzik
2006-04-21 1:34 ` Tejun Heo
2006-04-20 9:26 ` zhao, forrest
2006-04-21 1:20 ` Tejun Heo
2006-04-11 13:48 ` [PATCH 12/14] sata_sil: " Tejun Heo
2006-04-27 9:16 ` [PATCHSET 6/9] new EH implementation, take 2 Jeff Garzik
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=1145437721.3417.16.camel@forrest26.sh.intel.com \
--to=forrest.zhao@intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=axboe@suse.de \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=lkosewsk@gmail.com \
/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).