From: David Greaves <david@dgreaves.com>
To: David Lethe <david@santools.com>
Cc: Danilo Godec <danilo.godec@agenda.si>, Wolfgang Denk <wd@denx.de>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: SATA errors?
Date: Wed, 01 Oct 2008 13:17:37 +0100 [thread overview]
Message-ID: <48E36A61.4020903@dgreaves.com> (raw)
In-Reply-To: <A20315AE59B5C34585629E258D76A97C02180F8B@34093-C3-EVS3.exchange.rackspace.com>
David Lethe wrote:
> There is no cause of concern. The 0x25 command translates to
> READ_CAPACITY10. (i.e., how many blocks does the disk hold). This
> command is emulated because the disk doesn't natively speak SCSI
> commands, which is how your specific hardware/driver/controller
> combination configures such things.
and yet look at the timestamps...
> Oct 1 10:11:30 bigxen2 kernel: ata1: waiting for device to spin up (7
> secs)
> Oct 1 10:11:40 bigxen2 kernel: ata1: soft resetting port
> Oct 1 10:11:41 bigxen2 kernel: ata1: softreset failed (1st FIS failed)
> Oct 1 10:11:41 bigxen2 kernel: ata1: softreset failed, retrying in 5 secs
> Oct 1 10:11:46 bigxen2 kernel: ata1: hard resetting port
> Oct 1 10:11:47 bigxen2 kernel: ata1: SATA link up 3.0 Gbps (SStatus
> 123 SControl 300)
> Oct 1 10:11:47 bigxen2 kernel: ata1.00: configured for UDMA/133
> Oct 1 10:11:47 bigxen2 kernel: ata1: EH complete
That looks to me like 15-17 seconds of unresponsive disk; certainly the time
around the resets are times when the driver isn't allowing disk access.
I'd say there was cause for something; although I'd cc the linux-ide group for
real insight, not linux-raid :)
David - maybe the response from the 0x25 command should not result in a reset -
or maybe the 0x25 should not be issued if it causes a state that does require a
reset.
I get similar softreset/hardreset problems with some samsung drives on some
controllers. I've not got round to investigating it yet. Sorry.
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
next prev parent reply other threads:[~2008-10-01 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 9:25 SATA errors? Danilo Godec
2008-10-01 10:08 ` Wolfgang Denk
2008-10-01 10:41 ` Danilo Godec
2008-10-01 11:48 ` David Lethe
2008-10-01 12:17 ` David Greaves [this message]
2008-10-01 13:11 ` David Lethe
2008-10-01 21:36 ` Danilo Godec
2008-10-01 22:03 ` Justin Piszcz
2008-10-03 9:52 ` Danilo Godec
2008-10-03 16:13 ` Iustin Pop
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=48E36A61.4020903@dgreaves.com \
--to=david@dgreaves.com \
--cc=danilo.godec@agenda.si \
--cc=david@santools.com \
--cc=linux-raid@vger.kernel.org \
--cc=wd@denx.de \
/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).