All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Yan Seiner <yan@seiner.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: read-only /sys/block/sda/device/queue_depth
Date: Sat, 01 Sep 2007 17:42:30 -0600	[thread overview]
Message-ID: <46D9F8E6.8010101@shaw.ca> (raw)
In-Reply-To: <fa.opJB7DxTb+exFimOMpdmVACjitE@ifi.uio.no>

Yan Seiner wrote:
> I'm running into the same issue reported here:
> 
> <http://readlist.com/lists/vger.kernel.org/linux-kernel/72/361184.html>
> 
> I am using the ata_piix module.  If I read the docs correctly, I should 
> be able to use ahci as well; I need to rebuild the kernel though (debian 
> insists on putting ata_piix into the initrd....)
> 
> dionysus:~# ls -l /sys/block/sd[abcde]/device/queue_depth
> -r--r--r-- 1 root root 4096 2007-09-01 06:00 
> /sys/block/sda/device/queue_depth
> -r--r--r-- 1 root root 4096 2007-09-01 06:00 
> /sys/block/sdb/device/queue_depth
> -r--r--r-- 1 root root 4096 2007-09-01 06:00 
> /sys/block/sdc/device/queue_depth
> -r--r--r-- 1 root root 4096 2007-09-01 06:00 
> /sys/block/sdd/device/queue_depth
> -r--r--r-- 1 root root 4096 2007-09-01 06:00 
> /sys/block/sde/device/queue_depth
> 
> If I change the perms to rw, I get an Input/Output error.  AFAICT, the 
> drives support queueing, but it's disabled.

ata_piix does not support NCQ. You have to use AHCI mode for that.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-09-01 23:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.opJB7DxTb+exFimOMpdmVACjitE@ifi.uio.no>
2007-09-01 23:42 ` Robert Hancock [this message]
2007-09-01 13:16 read-only /sys/block/sda/device/queue_depth Yan Seiner

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=46D9F8E6.8010101@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yan@seiner.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 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.