From: Mark Lord <liml@rtr.ca>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Linux IDE <linux-ide@vger.kernel.org>
Subject: Re: sata_mv: hard resetting port
Date: Wed, 14 Nov 2007 10:27:18 -0500 [thread overview]
Message-ID: <473B13D6.3080202@rtr.ca> (raw)
In-Reply-To: <473AC34B.8000709@wpkg.org>
Tomasz Chmielewski wrote:
> This are the log entries I saw as I started e2fsck on a 5-disk Linux
> RAID-5 array; all disks connected to a sata_mv controller:
>
> ata6.00: exception Emask 0x1 SAct 0x0 SErr 0x100000 action 0x6 frozen
> ata6.00: edma_err 0x00000084, EDMA self-disable
..
Translation:
"The port had a link CRC error, which caused it to drop out of host-queuing mode."
> ata6.00: cmd 25/00:00:bf:09:24/00:02:1c:00:00/e0 tag 0 cdb 0x0 data 262144 in
> res 51/84:00:bf:09:24/84:02:1c:00:00/e0 Emask 0x10 (ATA bus error)
> ata6: hard resetting port
> ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata6.00: configured for UDMA/133
> ata6: EH complete
> sd 5:0:0:0: [sde] 781422768 512-byte hardware sectors (400088 MB)
> sd 5:0:0:0: [sde] Write Protect is off
> sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00
> sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> ata6: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
> ata6: edma_err 0x00000020
> ata6: hard resetting port
> ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata6.00: configured for UDMA/133
> ata6: EH pending after completion, repeating EH (cnt=4)
> ata6: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0x7
> ata6: edma_err 0x00000010, dev connect
> ata6: hard resetting port
> ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata6.00: configured for UDMA/133
> ata6: EH complete
> sd 5:0:0:0: [sde] 781422768 512-byte hardware sectors (400088 MB)
> sd 5:0:0:0: [sde] Write Protect is off
> sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00
> sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sd 5:0:0:0: [sde] 781422768 512-byte hardware sectors (400088 MB)
> sd 5:0:0:0: [sde] Write Protect is off
> sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00
> sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
..
Translation:
"libata reset the link, and everything appeared okay,
so it reissued the failed command and continued.
No data loss."
> That's the Marvell controller:
>
> 01:00.0 SCSI storage controller: Marvell Technology Group Ltd.
> MV88SX6081 8-port SATA II PCI-X Controller (rev 09)
next prev parent reply other threads:[~2007-11-14 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 9:43 sata_mv: hard resetting port Tomasz Chmielewski
2007-11-14 15:27 ` Mark Lord [this message]
2007-11-14 15:36 ` Tomasz Chmielewski
2007-11-14 16:11 ` Mark Lord
2007-11-15 3:36 ` Tejun Heo
2007-11-15 4:12 ` Mark Lord
2007-11-15 10:16 ` Tomasz Chmielewski
2007-11-15 10:26 ` Tomasz Chmielewski
2007-11-15 14:31 ` Mark Lord
2007-11-15 19:22 ` 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=473B13D6.3080202@rtr.ca \
--to=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=mangoo@wpkg.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).