From: Tejun Heo <htejun@gmail.com>
To: Philipp Wagner <mail@philipp-wagner.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Hotplug with sata_nv
Date: Mon, 31 Jul 2006 05:35:01 +0900 [thread overview]
Message-ID: <44CD17F5.5010800@gmail.com> (raw)
In-Reply-To: <44BE9B67.7020901@philipp-wagner.com>
[-- Attachment #1: Type: text/plain, Size: 2087 bytes --]
Hello, Philipp,
Sorry about late reply. There were OLS and then some personal things to
attend to.
Philipp Wagner wrote:
> When I remove one drive, I get the following messages into
> /var/log/messages:
>
> Jul 19 21:59:08 srv1 kernel: ata2: exception Emask 0x10 SAct 0x0 SErr
> 0x1810000 action 0x2 frozen
> Jul 19 21:59:08 srv1 kernel: ata2: soft resetting port
> Jul 19 21:59:08 srv1 kernel: ata2: SATA link down (SStatus 0 SControl 300)
> Jul 19 21:59:08 srv1 kernel: ata2: failed to recover some devices,
> retrying in 5 secs
> Jul 19 21:59:13 srv1 kernel: ata2: hard resetting port
> Jul 19 21:59:14 srv1 kernel: ata2: SATA link down (SStatus 0 SControl 300)
> Jul 19 21:59:14 srv1 kernel: ata2: failed to recover some devices,
> retrying in 5 secs
> Jul 19 21:59:19 srv1 kernel: ata2: hard resetting port
> Jul 19 21:59:20 srv1 kernel: ata2: SATA link down (SStatus 0 SControl 300)
> Jul 19 21:59:20 srv1 kernel: ata2.00: disabled
> Jul 19 21:59:20 srv1 kernel: ata2: EH pending after completion,
> repeating EH (cnt=4)
> Jul 19 21:59:20 srv1 kernel: ata2: EH complete
>
> The files /dev/sdb* are removed and the RAID says it has been degraded,
> which is perfectly ok.
This looks good.
> Now I re-insert the drive and get the following messages into
> /var/log/messages:
>
> Jul 19 22:00:11 srv1 kernel: ata2: exception Emask 0x10 SAct 0x0 SErr
> 0x50000 action 0x2 frozen
> Jul 19 22:00:19 srv1 kernel: ata2: port is slow to respond, please be
> patient
> Jul 19 22:00:42 srv1 kernel: ata2: port failed to respond (30 secs)
> Jul 19 22:00:42 srv1 kernel: ata2: soft resetting port
> Jul 19 22:00:49 srv1 kernel: ata2: port is slow to respond, please be
> patient
> Jul 19 22:01:12 srv1 kernel: ata2: port failed to respond (30 secs)
> Jul 19 22:01:12 srv1 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113
> SControl 300)
> Jul 19 22:01:12 srv1 kernel: ata2: EH pending after completion,
> repeating EH (cnt=4)
> Jul 19 22:01:12 srv1 kernel: ata2: EH complete
Hmmm... Softreset fails but libata doesn't notice it has failed.
Can you try the attached patch?
--
tejun
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1232 bytes --]
diff --git a/drivers/scsi/sata_nv.c b/drivers/scsi/sata_nv.c
index 56da255..0ff682b 100644
--- a/drivers/scsi/sata_nv.c
+++ b/drivers/scsi/sata_nv.c
@@ -257,7 +257,9 @@ static struct ata_port_info nv_port_info
/* generic */
{
.sht = &nv_sht,
- .host_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY,
+ .host_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY |
+ ATA_FLAG_HRST_TO_RESUME |
+ ATA_FLAG_SKIP_D2H_BSY,
.pio_mask = NV_PIO_MASK,
.mwdma_mask = NV_MWDMA_MASK,
.udma_mask = NV_UDMA_MASK,
@@ -266,7 +268,9 @@ static struct ata_port_info nv_port_info
/* nforce2/3 */
{
.sht = &nv_sht,
- .host_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY,
+ .host_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY |
+ ATA_FLAG_HRST_TO_RESUME |
+ ATA_FLAG_SKIP_D2H_BSY,
.pio_mask = NV_PIO_MASK,
.mwdma_mask = NV_MWDMA_MASK,
.udma_mask = NV_UDMA_MASK,
@@ -275,7 +279,9 @@ static struct ata_port_info nv_port_info
/* ck804 */
{
.sht = &nv_sht,
- .host_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY,
+ .host_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY |
+ ATA_FLAG_HRST_TO_RESUME |
+ ATA_FLAG_SKIP_D2H_BSY,
.pio_mask = NV_PIO_MASK,
.mwdma_mask = NV_MWDMA_MASK,
.udma_mask = NV_UDMA_MASK,
next prev parent reply other threads:[~2006-07-30 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 20:51 Hotplug with sata_nv Philipp Wagner
2006-07-30 20:35 ` Tejun Heo [this message]
2006-08-13 7:58 ` Philipp Wagner
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=44CD17F5.5010800@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mail@philipp-wagner.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).