From: "Matthew \"Cheetah\" Gabeler-Lee" <cheetah-lkmlsata@fastcat.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org, ide <linux-ide@vger.kernel.org>
Subject: Re: Frequent SATA resets with sata_nv (fwd)
Date: Tue, 26 Jun 2007 12:06:37 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.0.99.0706251207230.20899@cheetah.fastcat.org> (raw)
In-Reply-To: <467ECBB8.2030706@shaw.ca>
On Sun, 24 Jun 2007, Robert Hancock wrote:
> Matthew "Cheetah" Gabeler-Lee wrote:
> > (Please cc me on replies)
> >
> > I have three samsung hdds (/sys/block/sda/device/model says SAMSUNG SP2504C)
> > in a raid configuration. My system frequently (2-3x/day) experiences
> > temporary lockups, which produce messages as below in my dmesg/syslog. The
> > system recovers, but the hang is annoying to say the least.
>
> Does this drive actually support NCQ? I can't tell from this part of the log.
I selected that model in part because it at least claimed to support
NCQ. I'm not sure if it reflects NCQ or not, but I do have
/sys/block/sd[abc]/device/queue_{depth,type} which show simple and 31
respectively. Samsung's page for the drive also says it supports NCQ:
http://www.samsung.com/Products/HardDiskDrive/SpinPointPSeries/HardDiskDrive_SpinPointPSeries_SP2504C.htm
--
-Cheetah
"Reality is that which, when you stop believing in it, doesn't go away".
-- Philip K. Dick
GPG pubkey fingerprint: A57F B354 FD30 A502 795B 9637 3EF1 3F22 A85E 2AD1
next prev parent reply other threads:[~2007-06-26 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.Z5bo5y2TvW4efa6slAJpcdPwqAA@ifi.uio.no>
2007-06-24 19:53 ` Frequent SATA resets with sata_nv (fwd) Robert Hancock
2007-06-26 16:06 ` Matthew "Cheetah" Gabeler-Lee [this message]
2007-06-26 17:29 ` Heinz Ulrich Stille
2007-06-24 0:52 Matthew "Cheetah" Gabeler-Lee
2007-06-24 17:09 ` Alistair John Strachan
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=alpine.DEB.0.99.0706251207230.20899@cheetah.fastcat.org \
--to=cheetah-lkmlsata@fastcat.org \
--cc=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).