subject:"read\-only \/sys\/block\/sda\/device\/queue

Re: read-only /sys/block/sda/device/queue_depth

2007-09-01 Thread Robert Hancock


Yan Seiner wrote:

I'm running into the same issue reported here:



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 [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

read-only /sys/block/sda/device/queue_depth

2007-09-01 Thread Yan Seiner


I'm running into the same issue reported here:



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.


dionysus:~# uname -a
Linux dionysus 2.6.22.6 #1 SMP Fri Aug 31 14:24:17 PDT 2007 x86_64 GNU/Linux

libata version 2.21 loaded.
ata_piix :00:1f.2: version 2.11
ata_piix :00:1f.2: MAP [ P0 P2 P1 P3 ]
scsi0 : ata_piix
scsi1 : ata_piix
ata1: SATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 
bmdma 0x0001f000 irq 14
ata2: SATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 
bmdma 0x0001f008 irq 15

ata1.00: Host Protected Area detected:
ata1.00: ATA-7: ST3400620AS, 3.AAC, max UDMA/133
ata1.00: 781420655 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata1.01: Host Protected Area detected:
ata1.01: ATA-7: ST3400620AS, 3.AAC, max UDMA/133
ata1.01: 781420655 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata1.00: Host Protected Area detected:
ata1.00: configured for UDMA/133
ata1.01: Host Protected Area detected:
ata1.01: configured for UDMA/133
ata2.00: ATA-7: ST3400620AS, 3.AAC, max UDMA/133
ata2.00: 781422768 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata2.01: ATA-7: ST3400620AS, 3.AAC, max UDMA/133
ata2.01: 781422768 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata2.00: configured for UDMA/133
ata2.01: configured for UDMA/133

dionysus:~# lspci -s 00:1f.2 -vvv
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) 
Serial ATA Storage Controller IDE (rev 01) (prog-if 8a [Master SecP PriP])

   Subsystem: Giga-byte Technology Unknown device b002
   Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
   Latency: 0
   Interrupt: pin B routed to IRQ 19
   Region 0: I/O ports at 01f0 [size=8]
   Region 1: I/O ports at 03f4 [size=1]
   Region 2: I/O ports at 0170 [size=8]
   Region 3: I/O ports at 0374 [size=1]
   Region 4: I/O ports at f000 [size=16]
   Capabilities: [70] Power Management version 2
   Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot+,D3cold-)

   Status: D0 PME-Enable- DSel=0 DScale=0 PME-

--
 o__
 ,>/'_  o__
 (_)\(_),>/'_  o__
Yan Seiner  (_)\(_) ,>/'_   o__ o__
Certified Personal Trainer (_)\(_)  ,>/'_   ,>/'_
Licensed Professional Engineer (_)\(_) (_)\(_)

Linux stuff has made big progress over the competition. When things sit and 
don't start right away, we have a watch, and those poor guys have to settle for 
an hourglass.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

read-only /sys/block/sda/device/queue_depth

2007-09-01 Thread Yan Seiner


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.


dionysus:~# uname -a
Linux dionysus 2.6.22.6 #1 SMP Fri Aug 31 14:24:17 PDT 2007 x86_64 GNU/Linux

libata version 2.21 loaded.
ata_piix :00:1f.2: version 2.11
ata_piix :00:1f.2: MAP [ P0 P2 P1 P3 ]
scsi0 : ata_piix
scsi1 : ata_piix
ata1: SATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 
bmdma 0x0001f000 irq 14
ata2: SATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 
bmdma 0x0001f008 irq 15

ata1.00: Host Protected Area detected:
ata1.00: ATA-7: ST3400620AS, 3.AAC, max UDMA/133
ata1.00: 781420655 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata1.01: Host Protected Area detected:
ata1.01: ATA-7: ST3400620AS, 3.AAC, max UDMA/133
ata1.01: 781420655 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata1.00: Host Protected Area detected:
ata1.00: configured for UDMA/133
ata1.01: Host Protected Area detected:
ata1.01: configured for UDMA/133
ata2.00: ATA-7: ST3400620AS, 3.AAC, max UDMA/133
ata2.00: 781422768 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata2.01: ATA-7: ST3400620AS, 3.AAC, max UDMA/133
ata2.01: 781422768 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata2.00: configured for UDMA/133
ata2.01: configured for UDMA/133

dionysus:~# lspci -s 00:1f.2 -vvv
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) 
Serial ATA Storage Controller IDE (rev 01) (prog-if 8a [Master SecP PriP])

   Subsystem: Giga-byte Technology Unknown device b002
   Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR-

   Latency: 0
   Interrupt: pin B routed to IRQ 19
   Region 0: I/O ports at 01f0 [size=8]
   Region 1: I/O ports at 03f4 [size=1]
   Region 2: I/O ports at 0170 [size=8]
   Region 3: I/O ports at 0374 [size=1]
   Region 4: I/O ports at f000 [size=16]
   Capabilities: [70] Power Management version 2
   Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot+,D3cold-)

   Status: D0 PME-Enable- DSel=0 DScale=0 PME-

--
 o__
 ,/'_  o__
 (_)\(_),/'_  o__
Yan Seiner  (_)\(_) ,/'_   o__ o__
Certified Personal Trainer (_)\(_)  ,/'_   ,/'_
Licensed Professional Engineer (_)\(_) (_)\(_)

Linux stuff has made big progress over the competition. When things sit and 
don't start right away, we have a watch, and those poor guys have to settle for 
an hourglass.

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: read-only /sys/block/sda/device/queue_depth

2007-09-01 Thread Robert Hancock


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 [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: read-only /sys/block/sda/device/queue_depth

read-only /sys/block/sda/device/queue_depth

read-only /sys/block/sda/device/queue_depth

Re: read-only /sys/block/sda/device/queue_depth

4 matches

Site Navigation

Mail list logo

Footer information