From: Robert Hancock <hancockr@shaw.ca>
To: Cal Peake <cp@absolutedigital.net>
Cc: Meelis Roos <mroos@linux.ee>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: spurious NCQ completions from FUJITSU MHW2120BH
Date: Sat, 04 Aug 2007 23:10:50 -0600 [thread overview]
Message-ID: <46B55BDA.1080900@shaw.ca> (raw)
In-Reply-To: <fa.y0XijGKloFk3CDz3kVQUCU51GDU@ifi.uio.no>
Cal Peake wrote:
> On Fri, 3 Aug 2007, Meelis Roos wrote:
>
>> Todays git gave me some EH errors during fsck (30 times mounted and time
>> to check), then recovered and works fine. Seems to be spurious NCQ
>> completion. The disk is
>>
>> Device Model: FUJITSU MHW2120BH
>> Firmware Version: 00000012
>> User Capacity: 120�034�123�776 bytes
>
> As a data point: I've got the same drive w/ same revision in my laptop and
> haven't had any NCQ errors pop up. Currently running 2.6.23-rc2.
>
> ata1.00: ATA-8: FUJITSU MHW2120BH, 00000012, max UDMA/100
> ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 0/32)
> ata1.00: configured for UDMA/100
>
> Might be dependent on the controller and/or the driver. Got a nVidia MCP51
> using sata_nv here.
That would be because you're not using NCQ. Patches to add NCQ support
for MCP51 are only in -mm tree, not in mainline.
Also, AHCI is the only controller type that is easily able to detect this..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-08-05 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.+Y6uPNp+jT45Cb8RRlG6/M5Gw1I@ifi.uio.no>
[not found] ` <fa.y0XijGKloFk3CDz3kVQUCU51GDU@ifi.uio.no>
2007-08-05 5:10 ` Robert Hancock [this message]
2007-08-03 20:47 spurious NCQ completions from FUJITSU MHW2120BH Meelis Roos
2007-08-05 1:45 ` Cal Peake
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=46B55BDA.1080900@shaw.ca \
--to=hancockr@shaw.ca \
--cc=cp@absolutedigital.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.