* libata pm
@ 2008-01-26 18:03 dusty
2008-01-26 20:05 ` dusty
0 siblings, 1 reply; 16+ messages in thread
From: dusty @ 2008-01-26 18:03 UTC (permalink / raw)
To: htejun; +Cc: linux-ide
[-- Attachment #1: Type: text/plain, Size: 6556 bytes --]
I'm currently running
Linux *** 2.6.23 #1 SMP PREEMPT Sat Jan 26 17:59:58 CET 2008 x86_64
Intel(R) Pentium(R) D CPU 3.20GHz GenuineIntel GNU/Linux
with the libata-tj-2.6.23-20071011 path for 2.6.23
and for testing purposes
linux-2.6.24-rc6-mm1
on a Asus P5WDG2-WS with two PCI-X Dawicontrol DC 4300 Controllers and two
Dawicontrol DC 6510 PM port multipliers to get 16 sata ports. (the linux
partition is on a ide drive)
the second raid array with 8 Samsung HD-LJ 501 works great without any
errors. but the first raid with 8 Maxtor 6V300F0 produces one error after
another after mounting the filesystem:
Filesystem "dm-0": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-0
Ending clean XFS mount for filesystem: dm-0
Filesystem "dm-1": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-1
Ending clean XFS mount for filesystem: dm-1
ata6.04: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xb
ata6: SError: { PHYRdyChg DevExch }
ata6.04: hard resetting link
ata6.04: SATA link down (SStatus 0 SControl 300)
ata6: failed to recover some devices, retrying in 5 secs
ata6.04: hard resetting link
ata6.04: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata6.04: configured for UDMA/100
ata6: EH complete
sd 5:0:0:0: [sdh] 586114704 512-byte hardware sectors (300091 MB)
sd 5:0:0:0: [sdh] Write Protect is off
sd 5:0:0:0: [sdh] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:1:0:0: [sdi] 586114704 512-byte hardware sectors (300091 MB)
sd 5:1:0:0: [sdi] Write Protect is off
sd 5:1:0:0: [sdi] Mode Sense: 00 3a 00 00
sd 5:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:2:0:0: [sdj] 586114704 512-byte hardware sectors (300091 MB)
sd 5:2:0:0: [sdj] Write Protect is off
sd 5:2:0:0: [sdj] Mode Sense: 00 3a 00 00
sd 5:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:3:0:0: [sdk] 586114704 512-byte hardware sectors (300091 MB)
sd 5:3:0:0: [sdk] Write Protect is off
sd 5:3:0:0: [sdk] Mode Sense: 00 3a 00 00
sd 5:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:4:0:0: [sdl] 586114704 512-byte hardware sectors (300091 MB)
sd 5:4:0:0: [sdl] Write Protect is off
sd 5:4:0:0: [sdl] Mode Sense: 00 3a 00 00
sd 5:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata6.00: failed to read SCR 1 (Emask=0x40)
ata6.01: failed to read SCR 1 (Emask=0x40)
ata6.02: failed to read SCR 1 (Emask=0x40)
ata6.03: failed to read SCR 1 (Emask=0x40)
ata6.04: failed to read SCR 1 (Emask=0x40)
ata6.05: failed to read SCR 1 (Emask=0x40)
ata6.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata6.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata6.01: cmd c8/00:10:97:26:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 8192 in
res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata6.01: status: { DRDY }
ata6.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata6.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata6.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata6.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata6.15: hard resetting link
ata6.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata6.00: hard resetting link
ata6.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata6.01: hard resetting link
ata6.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.02: hard resetting link
ata6.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.03: hard resetting link
ata6.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.04: hard resetting link
ata6.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.05: hard resetting link
ata6.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata6.00: configured for UDMA/100
ata6.01: configured for UDMA/100
ata6.02: configured for UDMA/100
ata6.03: configured for UDMA/100
ata6.04: configured for UDMA/100
ata6: EH complete
sd 5:0:0:0: [sdh] 586114704 512-byte hardware sectors (300091 MB)
sd 5:0:0:0: [sdh] Write Protect is off
sd 5:0:0:0: [sdh] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:1:0:0: [sdi] 586114704 512-byte hardware sectors (300091 MB)
sd 5:1:0:0: [sdi] Write Protect is off
sd 5:1:0:0: [sdi] Mode Sense: 00 3a 00 00
sd 5:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:2:0:0: [sdj] 586114704 512-byte hardware sectors (300091 MB)
sd 5:2:0:0: [sdj] Write Protect is off
sd 5:2:0:0: [sdj] Mode Sense: 00 3a 00 00
sd 5:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:3:0:0: [sdk] 586114704 512-byte hardware sectors (300091 MB)
sd 5:3:0:0: [sdk] Write Protect is off
sd 5:3:0:0: [sdk] Mode Sense: 00 3a 00 00
sd 5:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:4:0:0: [sdl] 586114704 512-byte hardware sectors (300091 MB)
sd 5:4:0:0: [sdl] Write Protect is off
sd 5:4:0:0: [sdl] Mode Sense: 00 3a 00 00
sd 5:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:0:0:0: [sdh] 586114704 512-byte hardware sectors (300091 MB)
sd 5:0:0:0: [sdh] Write Protect is off
sd 5:0:0:0: [sdh] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:1:0:0: [sdi] 586114704 512-byte hardware sectors (300091 MB)
sd 5:1:0:0: [sdi] Write Protect is off
sd 5:1:0:0: [sdi] Mode Sense: 00 3a 00 00
sd 5:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:2:0:0: [sdj] 586114704 512-byte hardware sectors (300091 MB)
sd 5:2:0:0: [sdj] Write Protect is off
sd 5:2:0:0: [sdj] Mode Sense: 00 3a 00 00
sd 5:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:3:0:0: [sdk] 586114704 512-byte hardware sectors (300091 MB)
sd 5:3:0:0: [sdk] Write Protect is off
sd 5:3:0:0: [sdk] Mode Sense: 00 3a 00 00
sd 5:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 5:4:0:0: [sdl] 586114704 512-byte hardware sectors (300091 MB)
sd 5:4:0:0: [sdl] Write Protect is off
sd 5:4:0:0: [sdl] Mode Sense: 00 3a 00 00
sd 5:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
these messages repeat themself for hours...
attached to this message is th dmesg output and hdparam -i for all devices
[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 29417 bytes --]
sata_sil24 0000:05:01.0: version 1.1
ACPI: PCI Interrupt 0000:05:01.0[A] -> GSI 24 (level, low) -> IRQ 24
sata_sil24 0000:05:01.0: Applying completion IRQ loss on PCI-X errata fix
scsi2 : sata_sil24
scsi3 : sata_sil24
scsi4 : sata_sil24
scsi5 : sata_sil24
ata3: SATA max UDMA/100 host m128@0xfeaffc00 port 0xfeaf0000 irq 24
ata4: SATA max UDMA/100 host m128@0xfeaffc00 port 0xfeaf2000 irq 24
ata5: SATA max UDMA/100 host m128@0xfeaffc00 port 0xfeaf4000 irq 24
ata6: SATA max UDMA/100 host m128@0xfeaffc00 port 0xfeaf6000 irq 24
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata3.00: ATA-7: Maxtor 6V300F0, VA111630, max UDMA/133
ata3.00: 586114704 sectors, multi 16: LBA48 NCQ (not used)
ata3.00: configured for UDMA/100
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata4.00: ATA-7: Maxtor 6V300F0, VA111630, max UDMA/133
ata4.00: 586114704 sectors, multi 16: LBA48 NCQ (not used)
ata4.00: configured for UDMA/100
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata5.00: ATA-7: Maxtor 6V300F0, VA111630, max UDMA/133
ata5.00: 586114704 sectors, multi 16: LBA48 NCQ (not used)
ata5.00: configured for UDMA/100
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata6.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9
ata6.00: hard resetting link
ata6.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata6.01: hard resetting link
ata6.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.02: hard resetting link
ata6.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.03: hard resetting link
ata6.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.04: hard resetting link
ata6.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.05: hard resetting link
ata6.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata6.00: ATA-7: Maxtor 6V300F0, VA111630, max UDMA/133
ata6.00: 586114704 sectors, multi 16: LBA48 NCQ (not used)
ata6.00: configured for UDMA/100
ata6.01: ATA-7: Maxtor 6V300F0, VA111630, max UDMA/133
ata6.01: 586114704 sectors, multi 0: LBA48 NCQ (not used)
ata6.01: configured for UDMA/100
ata6.02: ATA-7: Maxtor 6V300F0, VA111630, max UDMA/133
ata6.02: 586114704 sectors, multi 0: LBA48 NCQ (not used)
ata6.02: configured for UDMA/100
ata6.03: ATA-7: Maxtor 6V300F0, VA111630, max UDMA/133
ata6.03: 586114704 sectors, multi 0: LBA48 NCQ (not used)
ata6.03: configured for UDMA/100
ata6.04: ATA-7: Maxtor 6V300F0, VA111630, max UDMA/133
ata6.04: 586114704 sectors, multi 0: LBA48 NCQ (not used)
ata6.04: configured for UDMA/100
ata6: EH complete
scsi 2:0:0:0: Direct-Access ATA Maxtor 6V300F0 VA11 PQ: 0 ANSI: 5
sd 2:0:0:0: [sde] 586114704 512-byte hardware sectors (300091 MB)
sd 2:0:0:0: [sde] Write Protect is off
sd 2:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sde] 586114704 512-byte hardware sectors (300091 MB)
sd 2:0:0:0: [sde] Write Protect is off
sd 2:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sde: sde1
sd 2:0:0:0: [sde] Attached SCSI disk
sd 2:0:0:0: Attached scsi generic sg4 type 0
scsi 3:0:0:0: Direct-Access ATA Maxtor 6V300F0 VA11 PQ: 0 ANSI: 5
sd 3:0:0:0: [sdf] 586114704 512-byte hardware sectors (300091 MB)
sd 3:0:0:0: [sdf] Write Protect is off
sd 3:0:0:0: [sdf] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:0:0:0: [sdf] 586114704 512-byte hardware sectors (300091 MB)
sd 3:0:0:0: [sdf] Write Protect is off
sd 3:0:0:0: [sdf] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdf: sdf1
sd 3:0:0:0: [sdf] Attached SCSI disk
sd 3:0:0:0: Attached scsi generic sg5 type 0
scsi 4:0:0:0: Direct-Access ATA Maxtor 6V300F0 VA11 PQ: 0 ANSI: 5
sd 4:0:0:0: [sdg] 586114704 512-byte hardware sectors (300091 MB)
sd 4:0:0:0: [sdg] Write Protect is off
sd 4:0:0:0: [sdg] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 4:0:0:0: [sdg] 586114704 512-byte hardware sectors (300091 MB)
sd 4:0:0:0: [sdg] Write Protect is off
sd 4:0:0:0: [sdg] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdg: sdg1
sd 4:0:0:0: [sdg] Attached SCSI disk
sd 4:0:0:0: Attached scsi generic sg6 type 0
scsi 5:0:0:0: Direct-Access ATA Maxtor 6V300F0 VA11 PQ: 0 ANSI: 5
sd 5:0:0:0: [sdh] 586114704 512-byte hardware sectors (300091 MB)
sd 5:0:0:0: [sdh] Write Protect is off
sd 5:0:0:0: [sdh] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 5:0:0:0: [sdh] 586114704 512-byte hardware sectors (300091 MB)
sd 5:0:0:0: [sdh] Write Protect is off
sd 5:0:0:0: [sdh] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdh: sdh1
sd 5:0:0:0: [sdh] Attached SCSI disk
sd 5:0:0:0: Attached scsi generic sg7 type 0
scsi 5:1:0:0: Direct-Access ATA Maxtor 6V300F0 VA11 PQ: 0 ANSI: 5
sd 5:1:0:0: [sdi] 586114704 512-byte hardware sectors (300091 MB)
sd 5:1:0:0: [sdi] Write Protect is off
sd 5:1:0:0: [sdi] Mode Sense: 00 3a 00 00
sd 5:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 5:1:0:0: [sdi] 586114704 512-byte hardware sectors (300091 MB)
sd 5:1:0:0: [sdi] Write Protect is off
sd 5:1:0:0: [sdi] Mode Sense: 00 3a 00 00
sd 5:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdi: sdi1
sd 5:1:0:0: [sdi] Attached SCSI disk
sd 5:1:0:0: Attached scsi generic sg8 type 0
scsi 5:2:0:0: Direct-Access ATA Maxtor 6V300F0 VA11 PQ: 0 ANSI: 5
sd 5:2:0:0: [sdj] 586114704 512-byte hardware sectors (300091 MB)
sd 5:2:0:0: [sdj] Write Protect is off
sd 5:2:0:0: [sdj] Mode Sense: 00 3a 00 00
sd 5:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 5:2:0:0: [sdj] 586114704 512-byte hardware sectors (300091 MB)
sd 5:2:0:0: [sdj] Write Protect is off
sd 5:2:0:0: [sdj] Mode Sense: 00 3a 00 00
sd 5:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdj: sdj1
sd 5:2:0:0: [sdj] Attached SCSI disk
sd 5:2:0:0: Attached scsi generic sg9 type 0
scsi 5:3:0:0: Direct-Access ATA Maxtor 6V300F0 VA11 PQ: 0 ANSI: 5
sd 5:3:0:0: [sdk] 586114704 512-byte hardware sectors (300091 MB)
sd 5:3:0:0: [sdk] Write Protect is off
sd 5:3:0:0: [sdk] Mode Sense: 00 3a 00 00
sd 5:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 5:3:0:0: [sdk] 586114704 512-byte hardware sectors (300091 MB)
sd 5:3:0:0: [sdk] Write Protect is off
sd 5:3:0:0: [sdk] Mode Sense: 00 3a 00 00
sd 5:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdk: sdk1
sd 5:3:0:0: [sdk] Attached SCSI disk
sd 5:3:0:0: Attached scsi generic sg10 type 0
scsi 5:4:0:0: Direct-Access ATA Maxtor 6V300F0 VA11 PQ: 0 ANSI: 5
sd 5:4:0:0: [sdl] 586114704 512-byte hardware sectors (300091 MB)
sd 5:4:0:0: [sdl] Write Protect is off
sd 5:4:0:0: [sdl] Mode Sense: 00 3a 00 00
sd 5:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 5:4:0:0: [sdl] 586114704 512-byte hardware sectors (300091 MB)
sd 5:4:0:0: [sdl] Write Protect is off
sd 5:4:0:0: [sdl] Mode Sense: 00 3a 00 00
sd 5:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdl: sdl1
sd 5:4:0:0: [sdl] Attached SCSI disk
sd 5:4:0:0: Attached scsi generic sg11 type 0
ACPI: PCI Interrupt 0000:05:02.0[A] -> GSI 28 (level, low) -> IRQ 28
sata_sil24 0000:05:02.0: Applying completion IRQ loss on PCI-X errata fix
scsi6 : sata_sil24
scsi7 : sata_sil24
scsi8 : sata_sil24
scsi9 : sata_sil24
ata7: SATA max UDMA/100 host m128@0xfeaff800 port 0xfeae8000 irq 28
ata8: SATA max UDMA/100 host m128@0xfeaff800 port 0xfeaea000 irq 28
ata9: SATA max UDMA/100 host m128@0xfeaff800 port 0xfeaec000 irq 28
ata10: SATA max UDMA/100 host m128@0xfeaff800 port 0xfeaee000 irq 28
ata6.04: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xb
ata6: SError: { PHYRdyChg DevExch }
ata6.04: hard resetting link
ata6.04: SATA link down (SStatus 0 SControl 300)
ata6: failed to recover some devices, retrying in 5 secs
ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata7.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
ata7.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata7.00: configured for UDMA/100
ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata8.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
ata8.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata8.00: configured for UDMA/100
ata6.04: hard resetting link
ata6.04: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata6.04: configured for UDMA/100
ata6: EH complete
sd 5:0:0:0: [sdh] 586114704 512-byte hardware sectors (300091 MB)
sd 5:0:0:0: [sdh] Write Protect is off
sd 5:0:0:0: [sdh] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 5:1:0:0: [sdi] 586114704 512-byte hardware sectors (300091 MB)
sd 5:1:0:0: [sdi] Write Protect is off
sd 5:1:0:0: [sdi] Mode Sense: 00 3a 00 00
sd 5:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 5:2:0:0: [sdj] 586114704 512-byte hardware sectors (300091 MB)
sd 5:2:0:0: [sdj] Write Protect is off
sd 5:2:0:0: [sdj] Mode Sense: 00 3a 00 00
sd 5:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 5:3:0:0: [sdk] 586114704 512-byte hardware sectors (300091 MB)
sd 5:3:0:0: [sdk] Write Protect is off
sd 5:3:0:0: [sdk] Mode Sense: 00 3a 00 00
sd 5:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 5:4:0:0: [sdl] 586114704 512-byte hardware sectors (300091 MB)
sd 5:4:0:0: [sdl] Write Protect is off
sd 5:4:0:0: [sdl] Mode Sense: 00 3a 00 00
sd 5:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata9.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
ata9.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata9.00: configured for UDMA/100
ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata10.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9
ata10.00: hard resetting link
ata10.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.01: hard resetting link
ata10.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.02: hard resetting link
ata10.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.03: hard resetting link
ata10.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.04: hard resetting link
ata10.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.05: hard resetting link
ata10.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata10.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
ata10.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata10.00: configured for UDMA/100
ata10.01: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
ata10.01: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata10.01: configured for UDMA/100
ata10.02: ATA-8: SAMSUNG HD501LJ, CR100-11, max UDMA7
ata10.02: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata10.02: configured for UDMA/100
ata10.03: ATA-8: SAMSUNG HD501LJ, CR100-11, max UDMA7
ata10.03: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata10.03: configured for UDMA/100
ata10.04: ATA-8: SAMSUNG HD501LJ, CR100-11, max UDMA7
ata10.04: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata10.04: configured for UDMA/100
ata10: EH complete
scsi 6:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 6:0:0:0: [sdm] 976773168 512-byte hardware sectors (500108 MB)
sd 6:0:0:0: [sdm] Write Protect is off
sd 6:0:0:0: [sdm] Mode Sense: 00 3a 00 00
sd 6:0:0:0: [sdm] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 6:0:0:0: [sdm] 976773168 512-byte hardware sectors (500108 MB)
sd 6:0:0:0: [sdm] Write Protect is off
sd 6:0:0:0: [sdm] Mode Sense: 00 3a 00 00
sd 6:0:0:0: [sdm] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdm: sdm1
sd 6:0:0:0: [sdm] Attached SCSI disk
sd 6:0:0:0: Attached scsi generic sg12 type 0
scsi 7:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 7:0:0:0: [sdn] 976773168 512-byte hardware sectors (500108 MB)
sd 7:0:0:0: [sdn] Write Protect is off
sd 7:0:0:0: [sdn] Mode Sense: 00 3a 00 00
sd 7:0:0:0: [sdn] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 7:0:0:0: [sdn] 976773168 512-byte hardware sectors (500108 MB)
sd 7:0:0:0: [sdn] Write Protect is off
sd 7:0:0:0: [sdn] Mode Sense: 00 3a 00 00
sd 7:0:0:0: [sdn] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdn: sdn1
sd 7:0:0:0: [sdn] Attached SCSI disk
sd 7:0:0:0: Attached scsi generic sg13 type 0
scsi 8:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 8:0:0:0: [sdo] 976773168 512-byte hardware sectors (500108 MB)
sd 8:0:0:0: [sdo] Write Protect is off
sd 8:0:0:0: [sdo] Mode Sense: 00 3a 00 00
sd 8:0:0:0: [sdo] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 8:0:0:0: [sdo] 976773168 512-byte hardware sectors (500108 MB)
sd 8:0:0:0: [sdo] Write Protect is off
sd 8:0:0:0: [sdo] Mode Sense: 00 3a 00 00
sd 8:0:0:0: [sdo] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdo: sdo1
sd 8:0:0:0: [sdo] Attached SCSI disk
sd 8:0:0:0: Attached scsi generic sg14 type 0
scsi 9:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 9:0:0:0: [sdp] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdp] Write Protect is off
sd 9:0:0:0: [sdp] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 9:0:0:0: [sdp] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdp] Write Protect is off
sd 9:0:0:0: [sdp] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdp: sdp1
sd 9:0:0:0: [sdp] Attached SCSI disk
sd 9:0:0:0: Attached scsi generic sg15 type 0
scsi 9:1:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 9:1:0:0: [sdq] 976773168 512-byte hardware sectors (500108 MB)
sd 9:1:0:0: [sdq] Write Protect is off
sd 9:1:0:0: [sdq] Mode Sense: 00 3a 00 00
sd 9:1:0:0: [sdq] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 9:1:0:0: [sdq] 976773168 512-byte hardware sectors (500108 MB)
sd 9:1:0:0: [sdq] Write Protect is off
sd 9:1:0:0: [sdq] Mode Sense: 00 3a 00 00
sd 9:1:0:0: [sdq] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdq: sdq1
sd 9:1:0:0: [sdq] Attached SCSI disk
sd 9:1:0:0: Attached scsi generic sg16 type 0
scsi 9:2:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 9:2:0:0: [sdr] 976773168 512-byte hardware sectors (500108 MB)
sd 9:2:0:0: [sdr] Write Protect is off
sd 9:2:0:0: [sdr] Mode Sense: 00 3a 00 00
sd 9:2:0:0: [sdr] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 9:2:0:0: [sdr] 976773168 512-byte hardware sectors (500108 MB)
sd 9:2:0:0: [sdr] Write Protect is off
sd 9:2:0:0: [sdr] Mode Sense: 00 3a 00 00
sd 9:2:0:0: [sdr] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdr: sdr1
sd 9:2:0:0: [sdr] Attached SCSI disk
sd 9:2:0:0: Attached scsi generic sg17 type 0
scsi 9:3:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 9:3:0:0: [sds] 976773168 512-byte hardware sectors (500108 MB)
sd 9:3:0:0: [sds] Write Protect is off
sd 9:3:0:0: [sds] Mode Sense: 00 3a 00 00
sd 9:3:0:0: [sds] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 9:3:0:0: [sds] 976773168 512-byte hardware sectors (500108 MB)
sd 9:3:0:0: [sds] Write Protect is off
sd 9:3:0:0: [sds] Mode Sense: 00 3a 00 00
sd 9:3:0:0: [sds] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sds: sds1
sd 9:3:0:0: [sds] Attached SCSI disk
sd 9:3:0:0: Attached scsi generic sg18 type 0
scsi 9:4:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 9:4:0:0: [sdt] 976773168 512-byte hardware sectors (500108 MB)
sd 9:4:0:0: [sdt] Write Protect is off
sd 9:4:0:0: [sdt] Mode Sense: 00 3a 00 00
sd 9:4:0:0: [sdt] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 9:4:0:0: [sdt] 976773168 512-byte hardware sectors (500108 MB)
sd 9:4:0:0: [sdt] Write Protect is off
sd 9:4:0:0: [sdt] Mode Sense: 00 3a 00 00
sd 9:4:0:0: [sdt] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdt: sdt1
sd 9:4:0:0: [sdt] Attached SCSI disk
sd 9:4:0:0: Attached scsi generic sg19 type 0
ACPI: PCI Interrupt 0000:01:03.0[A] -> GSI 21 (level, low) -> IRQ 21
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21] MMIO=[fe5fb800-fe5fbfff] Max Packet=[2048] IR/IT contexts=[4/8]
ieee1394: raw1394: /dev/raw1394 device initialized
ehci_hcd: block sizes: qh 160 qtd 96 itd 192 sitd 96
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 20 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
drivers/usb/core/inode.c: creating file 'devices'
drivers/usb/core/inode.c: creating file '001'
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: reset hcs_params 0x104208 dbg=1 cc=4 pcc=2 ordered !ppc ports=8
ehci_hcd 0000:00:1d.7: reset hcc_params 6871 thresh 7 uframes 1024 64 bit addr
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 128 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: supports USB remote wakeup
ehci_hcd 0000:00:1d.7: irq 20, io mem 0xfebfbc00
ehci_hcd 0000:00:1d.7: reset command 080002 (park)=0 ithresh=8 period=1024 Reset HALT
ehci_hcd 0000:00:1d.7: init command 010001 (park)=0 ithresh=1 period=1024 RUN
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: default language 0x0409
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.23 ehci_hcd
usb usb1: SerialNumber: 0000:00:1d.7
usb usb1: uevent
usb usb1: usb_probe_device
usb usb1: configuration #1 chosen from 1 choice
usb usb1: adding 1-0:1.0 (config #1, interface 0)
usb 1-0:1.0: uevent
usb 1-0:1.0: uevent
hub 1-0:1.0: usb_probe_interface
hub 1-0:1.0: usb_probe_interface - got id
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
hub 1-0:1.0: standalone hub
hub 1-0:1.0: no power switching (usb 1.0)
hub 1-0:1.0: individual port over-current protection
hub 1-0:1.0: Single TT
hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
hub 1-0:1.0: power on to power good time: 20ms
hub 1-0:1.0: local power source is good
hub 1-0:1.0: trying to enable port power on non-switchable hub
hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0000
drivers/usb/core/inode.c: creating file '001'
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ohci_hcd: block sizes: ed 80 td 96
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
drivers/usb/core/inode.c: creating file '002'
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: detected 2 ports
uhci_hcd 0000:00:1d.0: uhci_check_and_reset_hc: cmd = 0x0000
uhci_hcd 0000:00:1d.0: Performing full reset
uhci_hcd 0000:00:1d.0: irq 20, io base 0x0000e480
usb usb2: default language 0x0409
usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.23 uhci_hcd
usb usb2: SerialNumber: 0000:00:1d.0
usb usb2: uevent
usb usb2: usb_probe_device
usb usb2: configuration #1 chosen from 1 choice
usb usb2: adding 2-0:1.0 (config #1, interface 0)
usb 2-0:1.0: uevent
usb 2-0:1.0: uevent
hub 2-0:1.0: usb_probe_interface
hub 2-0:1.0: usb_probe_interface - got id
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
hub 2-0:1.0: standalone hub
hub 2-0:1.0: no power switching (usb 1.0)
hub 2-0:1.0: individual port over-current protection
hub 2-0:1.0: power on to power good time: 2ms
hub 2-0:1.0: local power source is good
hub 2-0:1.0: trying to enable port power on non-switchable hub
hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0000
drivers/usb/core/inode.c: creating file '001'
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
drivers/usb/core/inode.c: creating file '003'
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: detected 2 ports
uhci_hcd 0000:00:1d.1: uhci_check_and_reset_hc: cmd = 0x0000
uhci_hcd 0000:00:1d.1: Performing full reset
uhci_hcd 0000:00:1d.1: irq 17, io base 0x0000e800
usb usb3: default language 0x0409
usb usb3: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: UHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.23 uhci_hcd
usb usb3: SerialNumber: 0000:00:1d.1
usb usb3: uevent
usb usb3: usb_probe_device
usb usb3: configuration #1 chosen from 1 choice
usb usb3: adding 3-0:1.0 (config #1, interface 0)
usb 3-0:1.0: uevent
usb 3-0:1.0: uevent
hub 3-0:1.0: usb_probe_interface
hub 3-0:1.0: usb_probe_interface - got id
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
hub 3-0:1.0: standalone hub
hub 3-0:1.0: no power switching (usb 1.0)
hub 3-0:1.0: individual port over-current protection
hub 3-0:1.0: power on to power good time: 2ms
hub 3-0:1.0: local power source is good
hub 3-0:1.0: trying to enable port power on non-switchable hub
hub 3-0:1.0: state 7 ports 2 chg 0000 evt 0000
drivers/usb/core/inode.c: creating file '001'
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
drivers/usb/core/inode.c: creating file '004'
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: detected 2 ports
uhci_hcd 0000:00:1d.2: uhci_check_and_reset_hc: cmd = 0x0000
uhci_hcd 0000:00:1d.2: Performing full reset
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000e880
usb usb4: default language 0x0409
usb usb4: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: UHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.23 uhci_hcd
usb usb4: SerialNumber: 0000:00:1d.2
usb usb4: uevent
usb usb4: usb_probe_device
usb usb4: configuration #1 chosen from 1 choice
usb usb4: adding 4-0:1.0 (config #1, interface 0)
usb 4-0:1.0: uevent
usb 4-0:1.0: uevent
hub 4-0:1.0: usb_probe_interface
hub 4-0:1.0: usb_probe_interface - got id
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
hub 4-0:1.0: standalone hub
hub 4-0:1.0: no power switching (usb 1.0)
hub 4-0:1.0: individual port over-current protection
hub 4-0:1.0: power on to power good time: 2ms
hub 4-0:1.0: local power source is good
hub 4-0:1.0: trying to enable port power on non-switchable hub
hub 4-0:1.0: state 7 ports 2 chg 0000 evt 0000
drivers/usb/core/inode.c: creating file '001'
ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
drivers/usb/core/inode.c: creating file '005'
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: detected 2 ports
uhci_hcd 0000:00:1d.3: uhci_check_and_reset_hc: cmd = 0x0000
uhci_hcd 0000:00:1d.3: Performing full reset
uhci_hcd 0000:00:1d.3: irq 19, io base 0x0000ec00
usb usb5: default language 0x0409
usb usb5: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: UHCI Host Controller
usb usb5: Manufacturer: Linux 2.6.23 uhci_hcd
usb usb5: SerialNumber: 0000:00:1d.3
usb usb5: uevent
usb usb5: usb_probe_device
usb usb5: configuration #1 chosen from 1 choice
usb usb5: adding 5-0:1.0 (config #1, interface 0)
usb 5-0:1.0: uevent
usb 5-0:1.0: uevent
hub 5-0:1.0: usb_probe_interface
hub 5-0:1.0: usb_probe_interface - got id
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
hub 5-0:1.0: standalone hub
hub 5-0:1.0: no power switching (usb 1.0)
hub 5-0:1.0: individual port over-current protection
hub 5-0:1.0: power on to power good time: 2ms
hub 5-0:1.0: local power source is good
hub 5-0:1.0: trying to enable port power on non-switchable hub
hub 5-0:1.0: state 7 ports 2 chg 0000 evt 0000
drivers/usb/core/inode.c: creating file '001'
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver libusual
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input2
Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 sec (nowayout= 0)
raid6: int64x1 1475 MB/s
raid6: int64x2 1948 MB/s
raid6: int64x4 2527 MB/s
raid6: int64x8 1794 MB/s
raid6: sse2x1 2383 MB/s
raid6: sse2x2 2079 MB/s
raid6: sse2x4 3100 MB/s
raid6: using algorithm sse2x4 (3100 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
oprofile: using NMI interrupt.
IPv4 over IPv4 tunneling driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Bridge firewalling registered
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
Freeing unused kernel memory: 244k freed
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0011d80000a4e2a2]
usb usb2: suspend_rh (auto-stop)
usb usb3: suspend_rh (auto-stop)
usb usb4: suspend_rh (auto-stop)
usb usb5: suspend_rh (auto-stop)
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
usb usb2: uevent
usb 2-0:1.0: uevent
usb 2-0:1.0: uevent
usb usb3: uevent
usb 3-0:1.0: uevent
usb 3-0:1.0: uevent
usb usb4: uevent
usb 4-0:1.0: uevent
usb 4-0:1.0: uevent
usb usb5: uevent
usb 5-0:1.0: uevent
usb 5-0:1.0: uevent
usb usb1: uevent
usb 1-0:1.0: uevent
usb 1-0:1.0: uevent
EXT3 FS on hda3, internal journal
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:03:00.0 to 64
sky2 0000:03:00.0: v1.18 addr 0xfe7fc000 irq 16 Yukon-XL (0xb3) rev 3
sky2 eth0: addr 00:17:31:2d:e6:a9
sky2 eth1: addr 00:17:31:2d:e6:aa
md: md1 stopped.
md: bind<sdg1>
md: bind<sdf1>
md: bind<sdh1>
md: bind<sdl1>
md: bind<sdk1>
md: bind<sdi1>
md: bind<sdj1>
md: bind<sde1>
raid5: device sde1 operational as raid disk 0
raid5: device sdj1 operational as raid disk 7
raid5: device sdi1 operational as raid disk 6
raid5: device sdk1 operational as raid disk 5
raid5: device sdl1 operational as raid disk 4
raid5: device sdh1 operational as raid disk 3
raid5: device sdf1 operational as raid disk 2
raid5: device sdg1 operational as raid disk 1
raid5: allocated 8476kB for md1
raid5: raid level 6 set md1 active with 8 out of 8 devices, algorithm 2
RAID5 conf printout:
--- rd:8 wd:8
disk 0, o:1, dev:sde1
disk 1, o:1, dev:sdg1
disk 2, o:1, dev:sdf1
disk 3, o:1, dev:sdh1
disk 4, o:1, dev:sdl1
disk 5, o:1, dev:sdk1
disk 6, o:1, dev:sdi1
disk 7, o:1, dev:sdj1
md1: bitmap initialized from disk: read 9/9 pages, set 1 bits
created bitmap (140 pages) for device md1
md: md2 stopped.
md: bind<sdt1>
md: bind<sds1>
md: bind<sdp1>
md: bind<sdo1>
md: bind<sdn1>
md: bind<sdm1>
md: bind<sdr1>
md: bind<sdq1>
raid5: device sdq1 operational as raid disk 0
raid5: device sdr1 operational as raid disk 7
raid5: device sdm1 operational as raid disk 6
raid5: device sdn1 operational as raid disk 5
raid5: device sdo1 operational as raid disk 4
raid5: device sdp1 operational as raid disk 3
raid5: device sds1 operational as raid disk 2
raid5: device sdt1 operational as raid disk 1
raid5: allocated 8476kB for md2
raid5: raid level 6 set md2 active with 8 out of 8 devices, algorithm 2
RAID5 conf printout:
--- rd:8 wd:8
disk 0, o:1, dev:sdq1
disk 1, o:1, dev:sdt1
disk 2, o:1, dev:sds1
disk 3, o:1, dev:sdp1
disk 4, o:1, dev:sdo1
disk 5, o:1, dev:sdn1
disk 6, o:1, dev:sdm1
disk 7, o:1, dev:sdr1
md2: bitmap initialized from disk: read 15/15 pages, set 0 bits
created bitmap (233 pages) for device md2
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 4096564k swap on /dev/hda2. Priority:-1 extents:1 across:4096564k
sky2 eth0: enabling interface
sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
sky2 eth1: enabling interface
ip_tables: (C) 2000-2006 Netfilter Core Team
sky2 eth1: Link is up at 100 Mbps, full duplex, flow control both
[-- Attachment #3: hdparm.txt --]
[-- Type: text/plain, Size: 10519 bytes --]
/dev/sde:
Model=Maxtor 6V300F0 , FwRev=VA111630, SerialNo=V602NCVG
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
/dev/sdf:
Model=Maxtor 6V300F0 , FwRev=VA111630, SerialNo=V60CJFRG
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
/dev/sdg:
Model=Maxtor 6V300F0 , FwRev=VA111630, SerialNo=V609JETG
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
/dev/sdh:
Model=Maxtor 6V300F0 , FwRev=VA111630, SerialNo=V60DX1ZG
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
/dev/sdi:
Model=Maxtor 6V300F0 , FwRev=VA111630, SerialNo=V606E2PG
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
/dev/sdj:
Model=Maxtor 6V300F0 , FwRev=VA111630, SerialNo=V606F26G
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
/dev/sdk:
Model=Maxtor 6V300F0 , FwRev=VA111630, SerialNo=V606EAPG
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
/dev/sdl:
Model=Maxtor 6V300F0 , FwRev=VA111630, SerialNo=V60CJCHG
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
/dev/sdm:
Model=SAMSUNG HD501LJ , FwRev=CR100-10, SerialNo=S0MUJ13P119746
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-3,4,5,6,7
* signifies the current active mode
/dev/sdn:
Model=SAMSUNG HD501LJ , FwRev=CR100-10, SerialNo=S0MUJ13P119744
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-3,4,5,6,7
* signifies the current active mode
/dev/sdo:
Model=SAMSUNG HD501LJ , FwRev=CR100-10, SerialNo=S0MUJ13P119747
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-3,4,5,6,7
* signifies the current active mode
/dev/sdp:
Model=SAMSUNG HD501LJ , FwRev=CR100-10, SerialNo=S0MUJ13P119745
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-3,4,5,6,7
* signifies the current active mode
/dev/sdq:
Model=SAMSUNG HD501LJ , FwRev=CR100-10, SerialNo=S0MUJ13P798046
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-3,4,5,6,7
* signifies the current active mode
/dev/sdr:
Model=SAMSUNG HD501LJ , FwRev=CR100-11, SerialNo=S0MUJ1FP901642
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-3,4,5,6,7
* signifies the current active mode
/dev/sds:
Model=SAMSUNG HD501LJ , FwRev=CR100-11, SerialNo=S0MUJ1DP924383
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-3,4,5,6,7
* signifies the current active mode
/dev/sdt:
Model=SAMSUNG HD501LJ , FwRev=CR100-11, SerialNo= S0ZFJ1MP905874
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-3,4,5,6,7
* signifies the current active mode
[-- Attachment #4: lspci-nn.txt --]
[-- Type: text/plain, Size: 2535 bytes --]
00:00.0 Host bridge [0600]: Intel Corporation 82975X Memory Controller Hub [8086:277c] (rev c0)
00:01.0 PCI bridge [0604]: Intel Corporation 82975X PCI Express Root Port [8086:277d] (rev c0)
00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 01)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 [8086:27d0] (rev 01)
00:1c.4 PCI bridge [0604]: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 5 [8086:27e0] (rev 01)
00:1c.5 PCI bridge [0604]: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 6 [8086:27e2] (rev 01)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 [8086:27c8] (rev 01)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 [8086:27c9] (rev 01)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 [8086:27ca] (rev 01)
00:1d.3 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 [8086:27cb] (rev 01)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller [8086:27cc] (rev 01)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01)
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01)
00:1f.2 IDE interface [0101]: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller [8086:27c0] (rev 01)
00:1f.3 SMBus [0c05]: Intel Corporation 82801G (ICH7 Family) SMBus Controller [8086:27da] (rev 01)
01:01.0 VGA compatible controller [0300]: Matrox Graphics, Inc. MGA 1064SG [Mystique] [102b:051a] (rev 02)
01:03.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) [104c:8023]
02:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE614x SATA II PCI-E controller [11ab:6141] (rev 01)
03:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8062 PCI-E IPMI Gigabit Ethernet Controller [11ab:4343] (rev 14)
04:00.0 PCI bridge [0604]: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A [8086:032c] (rev 09)
05:01.0 RAID bus controller [0104]: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller [1095:3124] (rev 01)
05:02.0 RAID bus controller [0104]: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller [1095:3124] (rev 02)
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-01-26 18:03 libata pm dusty
@ 2008-01-26 20:05 ` dusty
2008-01-26 23:33 ` Tejun Heo
0 siblings, 1 reply; 16+ messages in thread
From: dusty @ 2008-01-26 20:05 UTC (permalink / raw)
To: dusty; +Cc: htejun, linux-ide
I could solve the problem by ncq blacklisting the "Maxtor 6V300F0" devices
in libata-core.c
Am Sa, 26.01.2008, 18:03, schrieb dusty@gmx.li:
> I'm currently running
>
>
> Linux *** 2.6.23 #1 SMP PREEMPT Sat Jan 26 17:59:58 CET 2008 x86_64
> Intel(R) Pentium(R) D CPU 3.20GHz GenuineIntel GNU/Linux
> with the libata-tj-2.6.23-20071011 path for 2.6.23
>
> and for testing purposes
>
> linux-2.6.24-rc6-mm1
>
>
> on a Asus P5WDG2-WS with two PCI-X Dawicontrol DC 4300 Controllers and
> two Dawicontrol DC 6510 PM port multipliers to get 16 sata ports. (the
> linux partition is on a ide drive)
>
> the second raid array with 8 Samsung HD-LJ 501 works great without any
> errors. but the first raid with 8 Maxtor 6V300F0 produces one error after
> another after mounting the filesystem:
>
> Filesystem "dm-0": Disabling barriers, not supported by the underlying
> device XFS mounting filesystem dm-0
> Ending clean XFS mount for filesystem: dm-0
> Filesystem "dm-1": Disabling barriers, not supported by the underlying
> device XFS mounting filesystem dm-1
> Ending clean XFS mount for filesystem: dm-1
> ata6.04: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xb
> ata6: SError: { PHYRdyChg DevExch }
> ata6.04: hard resetting link
> ata6.04: SATA link down (SStatus 0 SControl 300)
> ata6: failed to recover some devices, retrying in 5 secs
> ata6.04: hard resetting link
> ata6.04: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata6.04: configured for UDMA/100
> ata6: EH complete
> sd 5:0:0:0: [sdh] 586114704 512-byte hardware sectors (300091 MB) sd
> 5:0:0:0: [sdh] Write Protect is off
> sd 5:0:0:0: [sdh] Mode Sense: 00 3a 00 00 sd 5:0:0:0: [sdh] Write cache:
> enabled, read cache: enabled, doesn't support DPO or FUA sd 5:1:0:0: [sdi]
> 586114704 512-byte hardware sectors (300091 MB)
> sd 5:1:0:0: [sdi] Write Protect is off sd 5:1:0:0: [sdi] Mode Sense: 00 3a
> 00 00
> sd 5:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA sd 5:2:0:0: [sdj] 586114704 512-byte hardware sectors
> (300091 MB)
> sd 5:2:0:0: [sdj] Write Protect is off sd 5:2:0:0: [sdj] Mode Sense: 00 3a
> 00 00
> sd 5:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA sd 5:3:0:0: [sdk] 586114704 512-byte hardware sectors
> (300091 MB)
> sd 5:3:0:0: [sdk] Write Protect is off sd 5:3:0:0: [sdk] Mode Sense: 00 3a
> 00 00
> sd 5:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA sd 5:4:0:0: [sdl] 586114704 512-byte hardware sectors
> (300091 MB)
> sd 5:4:0:0: [sdl] Write Protect is off sd 5:4:0:0: [sdl] Mode Sense: 00 3a
> 00 00
> sd 5:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA ata6.00: failed to read SCR 1 (Emask=0x40)
> ata6.01: failed to read SCR 1 (Emask=0x40)
> ata6.02: failed to read SCR 1 (Emask=0x40)
> ata6.03: failed to read SCR 1 (Emask=0x40)
> ata6.04: failed to read SCR 1 (Emask=0x40)
> ata6.05: failed to read SCR 1 (Emask=0x40)
> ata6.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata6.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata6.01: cmd c8/00:10:97:26:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 8192
> in res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ata6.01:
> status: { DRDY }
> ata6.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata6.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata6.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata6.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata6.15: hard resetting link
> ata6.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata6.00: hard resetting link
> ata6.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata6.01: hard resetting link
> ata6.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata6.02: hard resetting link
> ata6.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata6.03: hard resetting link
> ata6.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata6.04: hard resetting link
> ata6.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata6.05: hard resetting link
> ata6.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata6.00: configured for UDMA/100
> ata6.01: configured for UDMA/100
> ata6.02: configured for UDMA/100
> ata6.03: configured for UDMA/100
> ata6.04: configured for UDMA/100
> ata6: EH complete
> sd 5:0:0:0: [sdh] 586114704 512-byte hardware sectors (300091 MB) sd
> 5:0:0:0: [sdh] Write Protect is off
> sd 5:0:0:0: [sdh] Mode Sense: 00 3a 00 00 sd 5:0:0:0: [sdh] Write cache:
> enabled, read cache: enabled, doesn't support DPO or FUA sd 5:1:0:0: [sdi]
> 586114704 512-byte hardware sectors (300091 MB)
> sd 5:1:0:0: [sdi] Write Protect is off sd 5:1:0:0: [sdi] Mode Sense: 00 3a
> 00 00
> sd 5:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA sd 5:2:0:0: [sdj] 586114704 512-byte hardware sectors
> (300091 MB)
> sd 5:2:0:0: [sdj] Write Protect is off sd 5:2:0:0: [sdj] Mode Sense: 00 3a
> 00 00
> sd 5:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA sd 5:3:0:0: [sdk] 586114704 512-byte hardware sectors
> (300091 MB)
> sd 5:3:0:0: [sdk] Write Protect is off sd 5:3:0:0: [sdk] Mode Sense: 00 3a
> 00 00
> sd 5:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA sd 5:4:0:0: [sdl] 586114704 512-byte hardware sectors
> (300091 MB)
> sd 5:4:0:0: [sdl] Write Protect is off sd 5:4:0:0: [sdl] Mode Sense: 00 3a
> 00 00
> sd 5:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA sd 5:0:0:0: [sdh] 586114704 512-byte hardware sectors
> (300091 MB)
> sd 5:0:0:0: [sdh] Write Protect is off sd 5:0:0:0: [sdh] Mode Sense: 00 3a
> 00 00
> sd 5:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA sd 5:1:0:0: [sdi] 586114704 512-byte hardware sectors
> (300091 MB)
> sd 5:1:0:0: [sdi] Write Protect is off sd 5:1:0:0: [sdi] Mode Sense: 00 3a
> 00 00
> sd 5:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA sd 5:2:0:0: [sdj] 586114704 512-byte hardware sectors
> (300091 MB)
> sd 5:2:0:0: [sdj] Write Protect is off sd 5:2:0:0: [sdj] Mode Sense: 00 3a
> 00 00
> sd 5:2:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA sd 5:3:0:0: [sdk] 586114704 512-byte hardware sectors
> (300091 MB)
> sd 5:3:0:0: [sdk] Write Protect is off sd 5:3:0:0: [sdk] Mode Sense: 00 3a
> 00 00
> sd 5:3:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA sd 5:4:0:0: [sdl] 586114704 512-byte hardware sectors
> (300091 MB)
> sd 5:4:0:0: [sdl] Write Protect is off sd 5:4:0:0: [sdl] Mode Sense: 00 3a
> 00 00
> sd 5:4:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
>
>
>
> these messages repeat themself for hours...
>
> attached to this message is th dmesg output and hdparam -i for all
> devices
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-01-26 20:05 ` dusty
@ 2008-01-26 23:33 ` Tejun Heo
2008-01-27 1:38 ` dusty
0 siblings, 1 reply; 16+ messages in thread
From: Tejun Heo @ 2008-01-26 23:33 UTC (permalink / raw)
To: dusty; +Cc: linux-ide
dusty@gmx.li wrote:
> I could solve the problem by ncq blacklisting the "Maxtor 6V300F0" devices
> in libata-core.c
That's a strange story. The reported error was PHY readiness changed
and Device exchanged, both of which point to hotplug event. Maybe
something causes the firmware to reset? What happen if you only leave
two drives on the port multiplier and remove the NCQ blacklist? Also,
does the error ever occur on the drives which are connected directly to
the controller?
--
tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-01-26 23:33 ` Tejun Heo
@ 2008-01-27 1:38 ` dusty
2008-01-27 19:34 ` dusty
0 siblings, 1 reply; 16+ messages in thread
From: dusty @ 2008-01-27 1:38 UTC (permalink / raw)
To: Tejun Heo; +Cc: dusty, linux-ide
Am Sa, 26.01.2008, 23:33, schrieb Tejun Heo:
> dusty@gmx.li wrote:
>> I could solve the problem by ncq blacklisting the "Maxtor 6V300F0"
>> devices in libata-core.c
>
> That's a strange story. The reported error was PHY readiness changed
> and Device exchanged, both of which point to hotplug event. Maybe
> something causes the firmware to reset? What happen if you only leave two
> drives on the port multiplier and remove the NCQ blacklist? Also, does
> the error ever occur on the drives which are connected directly to the
> controller?
>
>
> --
> tejun
>
>
No the error only occures on the drives on the pm. I can test the pm with
two Maxtor drives tomorrow (currently backing up the raid).
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-01-27 1:38 ` dusty
@ 2008-01-27 19:34 ` dusty
2008-01-28 1:17 ` Tejun Heo
0 siblings, 1 reply; 16+ messages in thread
From: dusty @ 2008-01-27 19:34 UTC (permalink / raw)
Cc: Tejun Heo, dusty, linux-ide
Am So, 27.01.2008, 01:38, schrieb dusty@gmx.li:
> Am Sa, 26.01.2008, 23:33, schrieb Tejun Heo:
>
>> dusty@gmx.li wrote:
>>> I could solve the problem by ncq blacklisting the "Maxtor 6V300F0"
>>> devices in libata-core.c
>>
>> That's a strange story. The reported error was PHY readiness changed
>> and Device exchanged, both of which point to hotplug event. Maybe
>> something causes the firmware to reset? What happen if you only leave
>> two drives on the port multiplier and remove the NCQ blacklist? Also,
>> does the error ever occur on the drives which are connected directly to
>> the controller?
>>
>>
>> --
>> tejun
>>
>>
>
> No the error only occures on the drives on the pm. I can test the pm with
> two Maxtor drives tomorrow (currently backing up the raid).
>
>
With one, two and three drives on the pm I got no errors, so I tried to
change the power supply. I got two power supplies for the 16 harddrives
and the second one (with all Maxtor drives and the first pm) was failing.
After changing the power supply all problems where gone. Sorry for the
confusion.
The only remaining issue is that some sata links are only working with 1.5
gbps and I can't figure out why. (ata3,4,5,6.x are the Maxtor drives and
ata7,8,9,10.x are the Samsung ones)
jasmin ~ # dmesg | grep Gbps
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata6.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata6.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata10.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-01-27 19:34 ` dusty
@ 2008-01-28 1:17 ` Tejun Heo
2008-01-28 10:31 ` dusty
0 siblings, 1 reply; 16+ messages in thread
From: Tejun Heo @ 2008-01-28 1:17 UTC (permalink / raw)
To: dusty; +Cc: linux-ide
Hello,
dusty@gmx.li wrote:
> With one, two and three drives on the pm I got no errors, so I tried to
> change the power supply. I got two power supplies for the 16 harddrives
> and the second one (with all Maxtor drives and the first pm) was failing.
> After changing the power supply all problems where gone. Sorry for the
> confusion.
It's amazing that, in SATA, PSU-problem-verified / PSU-problem-suggested
ratio is significant. I don't think this ever was the case with PATA.
SATA link seems much more susceptible to power quality and allows
hooking up whole lot of drives.
> The only remaining issue is that some sata links are only working with 1.5
> gbps and I can't figure out why. (ata3,4,5,6.x are the Maxtor drives and
> ata7,8,9,10.x are the Samsung ones)
>
> jasmin ~ # dmesg | grep Gbps
> ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata6.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata6.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata6.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata6.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata6.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata6.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata10.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata10.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata10.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata10.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata10.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata10.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Hmm... That's how the hardware negotiated transfer rate w/ each other.
SControl is telling the hardware that there's no speed limit and to go
as high as it can but somehow 3.0Gbps negotiation failed and the link
speed is limited to 1.5Gbps for some of the ports. Is the result always
the same? What happens if you swap drives between ports? Also, if you
have an extra PSU lying around, can you hook it up with some of the
drives such that the load is more distributed.
Oh.. Another note on PSU. I don't know whether this still holds for
more recent ones but mid-to-high range multi-lane PSUs sometimes have
lesser juice on 12v rail available for disks than low cost single lane
PSUs. This is because high power 12v lanes are allocated to power video
cards and disks can only pull power from (usually) single weak 12v lane.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-01-28 1:17 ` Tejun Heo
@ 2008-01-28 10:31 ` dusty
2008-01-28 12:03 ` Tejun Heo
0 siblings, 1 reply; 16+ messages in thread
From: dusty @ 2008-01-28 10:31 UTC (permalink / raw)
To: Tejun Heo; +Cc: dusty, linux-ide
Hello,
Am Mo, 28.01.2008, 01:17, schrieb Tejun Heo:
> Hello,
>
>
> dusty@gmx.li wrote:
>> With one, two and three drives on the pm I got no errors, so I tried to
>> change the power supply. I got two power supplies for the 16
>> harddrives and the second one (with all Maxtor drives and the first pm)
>> was failing. After changing the power supply all problems where gone.
>> Sorry for the
>> confusion.
>
> It's amazing that, in SATA, PSU-problem-verified / PSU-problem-suggested
> ratio is significant. I don't think this ever was the case with PATA. SATA
> link seems much more susceptible to power quality and allows hooking up
> whole lot of drives.
>
>
>> The only remaining issue is that some sata links are only working with
>> 1.5
>> gbps and I can't figure out why. (ata3,4,5,6.x are the Maxtor drives and
>> ata7,8,9,10.x are the Samsung ones)
>>
>
> Hmm... That's how the hardware negotiated transfer rate w/ each other.
> SControl is telling the hardware that there's no speed limit and to go
> as high as it can but somehow 3.0Gbps negotiation failed and the link speed
> is limited to 1.5Gbps for some of the ports. Is the result always the
> same? What happens if you swap drives between ports? Also, if you have
> an extra PSU lying around, can you hook it up with some of the drives such
> that the load is more distributed.
>
> Oh.. Another note on PSU. I don't know whether this still holds for
> more recent ones but mid-to-high range multi-lane PSUs sometimes have
> lesser juice on 12v rail available for disks than low cost single lane
> PSUs. This is because high power 12v lanes are allocated to power video
> cards and disks can only pull power from (usually) single weak 12v lane.
>
> Thanks.
>
>
> --
> tejun
>
>
Shuffling the drives did not change anything to the linkspeed of the 3
ports running with 1.5 Gbps. Looks like the problem is port-related.
The first PSU (Multilane) offers (measured) 12,20 V on both lanes. This
falls during read/write access on all drives attached down to 12,10 V.
The second PSU (Singlelane) offers (measured) 11,75 V. This doesn't change
during read/write access on all drives attached. I tested the second PSU
without anything attached and it still offered 11,75 V.
I will try to add another PSU this evening and remeasure.
Currently the whole machine needs about 350W.
The PSUs are Targan 500W (Multilane - 2x12V 10A) and Noname 350W
(Singlelane - 1x12V 10A) so this 'should' be enough...
This night i copied the backup back to the first raid (the Maxtor drives)
without any error but during the transfer i got this on the second
(mounted but unused) raid:
ata10.00: failed to read SCR 1 (Emask=0x40)
ata10.01: failed to read SCR 1 (Emask=0x40)
ata10.02: failed to read SCR 1 (Emask=0x40)
ata10.03: failed to read SCR 1 (Emask=0x40)
ata10.04: failed to read SCR 1 (Emask=0x40)
ata10.05: failed to read SCR 1 (Emask=0x40)
ata10.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.02: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 1 cdb 0x0 data 0
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata10.02: status: { DRDY }
ata10.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.15: hard resetting link
ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata10.00: hard resetting link
ata10.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.01: hard resetting link
ata10.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.02: hard resetting link
ata10.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.03: hard resetting link
ata10.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.04: hard resetting link
ata10.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.05: hard resetting link
ata10.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata10.00: configured for UDMA/100
ata10.01: configured for UDMA/100
ata10.02: configured for UDMA/100
ata10.03: configured for UDMA/100
ata10.04: configured for UDMA/100
ata10: EH complete
sd 9:0:0:0: [sdp] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdp] Write Protect is off
sd 9:0:0:0: [sdp] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:1:0:0: [sdq] 976773168 512-byte hardware sectors (500108 MB)
sd 9:1:0:0: [sdq] Write Protect is off
sd 9:1:0:0: [sdq] Mode Sense: 00 3a 00 00
sd 9:1:0:0: [sdq] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:2:0:0: [sdr] 976773168 512-byte hardware sectors (500108 MB)
sd 9:2:0:0: [sdr] Write Protect is off
sd 9:2:0:0: [sdr] Mode Sense: 00 3a 00 00
sd 9:2:0:0: [sdr] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:3:0:0: [sds] 976773168 512-byte hardware sectors (500108 MB)
sd 9:3:0:0: [sds] Write Protect is off
sd 9:3:0:0: [sds] Mode Sense: 00 3a 00 00
sd 9:3:0:0: [sds] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:4:0:0: [sdt] 976773168 512-byte hardware sectors (500108 MB)
sd 9:4:0:0: [sdt] Write Protect is off
sd 9:4:0:0: [sdt] Mode Sense: 00 3a 00 00
sd 9:4:0:0: [sdt] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:0:0:0: [sdp] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdp] Write Protect is off
sd 9:0:0:0: [sdp] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:1:0:0: [sdq] 976773168 512-byte hardware sectors (500108 MB)
sd 9:1:0:0: [sdq] Write Protect is off
sd 9:1:0:0: [sdq] Mode Sense: 00 3a 00 00
sd 9:1:0:0: [sdq] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:2:0:0: [sdr] 976773168 512-byte hardware sectors (500108 MB)
sd 9:2:0:0: [sdr] Write Protect is off
sd 9:2:0:0: [sdr] Mode Sense: 00 3a 00 00
sd 9:2:0:0: [sdr] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:3:0:0: [sds] 976773168 512-byte hardware sectors (500108 MB)
sd 9:3:0:0: [sds] Write Protect is off
sd 9:3:0:0: [sds] Mode Sense: 00 3a 00 00
sd 9:3:0:0: [sds] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:4:0:0: [sdt] 976773168 512-byte hardware sectors (500108 MB)
sd 9:4:0:0: [sdt] Write Protect is off
sd 9:4:0:0: [sdt] Mode Sense: 00 3a 00 00
sd 9:4:0:0: [sdt] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata10.00: failed to read SCR 1 (Emask=0x40)
ata10.01: failed to read SCR 1 (Emask=0x40)
ata10.02: failed to read SCR 1 (Emask=0x40)
ata10.03: failed to read SCR 1 (Emask=0x40)
ata10.04: failed to read SCR 1 (Emask=0x40)
ata10.05: failed to read SCR 1 (Emask=0x40)
ata10.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.02: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 1 cdb 0x0 data 0
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata10.02: status: { DRDY }
ata10.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.03: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 3 cdb 0x0 data 0
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata10.03: status: { DRDY }
ata10.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.15: hard resetting link
ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata10.00: hard resetting link
ata10.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.01: hard resetting link
ata10.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.02: hard resetting link
ata10.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.03: hard resetting link
ata10.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.04: hard resetting link
ata10.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.05: hard resetting link
ata10.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata10.00: configured for UDMA/100
ata10.01: configured for UDMA/100
ata10.02: configured for UDMA/100
ata10.03: configured for UDMA/100
ata10.04: configured for UDMA/100
ata10: EH complete
sd 9:0:0:0: [sdp] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdp] Write Protect is off
sd 9:0:0:0: [sdp] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:1:0:0: [sdq] 976773168 512-byte hardware sectors (500108 MB)
sd 9:1:0:0: [sdq] Write Protect is off
sd 9:1:0:0: [sdq] Mode Sense: 00 3a 00 00
sd 9:1:0:0: [sdq] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:2:0:0: [sdr] 976773168 512-byte hardware sectors (500108 MB)
sd 9:2:0:0: [sdr] Write Protect is off
sd 9:2:0:0: [sdr] Mode Sense: 00 3a 00 00
sd 9:2:0:0: [sdr] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:3:0:0: [sds] 976773168 512-byte hardware sectors (500108 MB)
sd 9:3:0:0: [sds] Write Protect is off
sd 9:3:0:0: [sds] Mode Sense: 00 3a 00 00
sd 9:3:0:0: [sds] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:4:0:0: [sdt] 976773168 512-byte hardware sectors (500108 MB)
sd 9:4:0:0: [sdt] Write Protect is off
sd 9:4:0:0: [sdt] Mode Sense: 00 3a 00 00
sd 9:4:0:0: [sdt] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:0:0:0: [sdp] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdp] Write Protect is off
sd 9:0:0:0: [sdp] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:1:0:0: [sdq] 976773168 512-byte hardware sectors (500108 MB)
sd 9:1:0:0: [sdq] Write Protect is off
sd 9:1:0:0: [sdq] Mode Sense: 00 3a 00 00
sd 9:1:0:0: [sdq] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:2:0:0: [sdr] 976773168 512-byte hardware sectors (500108 MB)
sd 9:2:0:0: [sdr] Write Protect is off
sd 9:2:0:0: [sdr] Mode Sense: 00 3a 00 00
sd 9:2:0:0: [sdr] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:3:0:0: [sds] 976773168 512-byte hardware sectors (500108 MB)
sd 9:3:0:0: [sds] Write Protect is off
sd 9:3:0:0: [sds] Mode Sense: 00 3a 00 00
sd 9:3:0:0: [sds] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:4:0:0: [sdt] 976773168 512-byte hardware sectors (500108 MB)
sd 9:4:0:0: [sdt] Write Protect is off
sd 9:4:0:0: [sdt] Mode Sense: 00 3a 00 00
sd 9:4:0:0: [sdt] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-01-28 10:31 ` dusty
@ 2008-01-28 12:03 ` Tejun Heo
2008-01-30 21:34 ` dusty
0 siblings, 1 reply; 16+ messages in thread
From: Tejun Heo @ 2008-01-28 12:03 UTC (permalink / raw)
To: dusty; +Cc: linux-ide
Hello, Dusty.
dusty@gmx.li wrote:
> Shuffling the drives did not change anything to the linkspeed of the 3
> ports running with 1.5 Gbps. Looks like the problem is port-related.
Hmm... Okay. Maybe the signal traces or connectors have some problems.
But 3.0Gbps on downstream port doesn't make any difference anyway so
unless it leads to errors, it should be fine.
> The first PSU (Multilane) offers (measured) 12,20 V on both lanes. This
> falls during read/write access on all drives attached down to 12,10 V.
That explains the PHY dropouts. I've even seen drives to do hard reset
accompanying emergency head unload due to voltage dropping when high IO
load hits. Of course, data in cache is lost.
> The second PSU (Singlelane) offers (measured) 11,75 V. This doesn't change
> during read/write access on all drives attached. I tested the second PSU
> without anything attached and it still offered 11,75 V.
11.75 is still in spec and it doesn't fluctuate. I like this power much
better.
> I will try to add another PSU this evening and remeasure.
> Currently the whole machine needs about 350W.
> The PSUs are Targan 500W (Multilane - 2x12V 10A)
Maybe one of the lane is only connected to video power connectors?
IIRC, that was the idea of multilane power anyway.
> and Noname 350W (Singlelane - 1x12V 10A) so this 'should' be enough...
>
> This night i copied the backup back to the first raid (the Maxtor drives)
> without any error but during the transfer i got this on the second
> (mounted but unused) raid:
> ata10.00: failed to read SCR 1 (Emask=0x40)
> ata10.01: failed to read SCR 1 (Emask=0x40)
> ata10.02: failed to read SCR 1 (Emask=0x40)
> ata10.03: failed to read SCR 1 (Emask=0x40)
> ata10.04: failed to read SCR 1 (Emask=0x40)
> ata10.05: failed to read SCR 1 (Emask=0x40)
> ata10.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata10.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata10.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata10.02: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 1 cdb 0x0 data 0
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Timeout during heavy IO can be caused from a number of things and bad
power is one of them.
Please lemme know your test result.
--
tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-01-28 12:03 ` Tejun Heo
@ 2008-01-30 21:34 ` dusty
2008-01-31 1:13 ` Tejun Heo
0 siblings, 1 reply; 16+ messages in thread
From: dusty @ 2008-01-30 21:34 UTC (permalink / raw)
To: Tejun Heo; +Cc: dusty, linux-ide
>> Shuffling the drives did not change anything to the linkspeed of the 3
>> ports running with 1.5 Gbps. Looks like the problem is port-related.
>
> Hmm... Okay. Maybe the signal traces or connectors have some problems.
> But 3.0Gbps on downstream port doesn't make any difference anyway so
> unless it leads to errors, it should be fine.
>
>> The first PSU (Multilane) offers (measured) 12,20 V on both lanes. This
>> falls during read/write access on all drives attached down to 12,10 V.
>>
>
> That explains the PHY dropouts. I've even seen drives to do hard reset
> accompanying emergency head unload due to voltage dropping when high IO
> load hits. Of course, data in cache is lost.
>
>> The second PSU (Singlelane) offers (measured) 11,75 V. This doesn't
>> change during read/write access on all drives attached. I tested the
>> second PSU without anything attached and it still offered 11,75 V.
>
> 11.75 is still in spec and it doesn't fluctuate. I like this power much
> better.
>
>> I will try to add another PSU this evening and remeasure.
>> Currently the whole machine needs about 350W.
>> The PSUs are Targan 500W (Multilane - 2x12V 10A)
>>
>
> Maybe one of the lane is only connected to video power connectors?
> IIRC, that was the idea of multilane power anyway.
>
>
> Please lemme know your test result.
>
Sorry for my late answer, but i had to sort this out first.
After replacing the first PSU with a new Corsair 650W the power no longer
fluctuated more than 0,01 V (and this only when booting up the drives...)
I did a full resync on both raid arrays and got no more errors or resets,
but there were some inconsitencies during sync and the xfs filesystem on
both arrays had to be repaired. Are these problems caused by the pm resets
?
Thanks for your patience.
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-01-30 21:34 ` dusty
@ 2008-01-31 1:13 ` Tejun Heo
2008-02-01 13:42 ` dusty
0 siblings, 1 reply; 16+ messages in thread
From: Tejun Heo @ 2008-01-31 1:13 UTC (permalink / raw)
To: dusty; +Cc: linux-ide
dusty@gmx.li wrote:
> Sorry for my late answer, but i had to sort this out first.
> After replacing the first PSU with a new Corsair 650W the power no longer
> fluctuated more than 0,01 V (and this only when booting up the drives...)
> I did a full resync on both raid arrays and got no more errors or resets,
> but there were some inconsitencies during sync and the xfs filesystem on
> both arrays had to be repaired. Are these problems caused by the pm resets
> ?
libata EH won't lose any data as long as the hardware doesn't. If power
fluctuates causing your drive to briefly power down - this does happen
and you can hear the drive doing emergency unload when it happens, the
data in write buffer can be lost. On coming back, all that libata can
know is that the PHY suffered brief connection loss, so it resets the
device and goes on, so the data in the cache is lost now. It's
basically pulling the power plug from the harddrive while write is going
on and connecting it back quickly. You're bound to lose data.
--
tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-01-31 1:13 ` Tejun Heo
@ 2008-02-01 13:42 ` dusty
2008-02-01 13:53 ` Tejun Heo
2008-02-01 14:06 ` Mark Lord
0 siblings, 2 replies; 16+ messages in thread
From: dusty @ 2008-02-01 13:42 UTC (permalink / raw)
To: Tejun Heo; +Cc: dusty, linux-ide
>> Sorry for my late answer, but i had to sort this out first.
>> After replacing the first PSU with a new Corsair 650W the power no
>> longer fluctuated more than 0,01 V (and this only when booting up the
>> drives...) I did a full resync on both raid arrays and got no more
>> errors or resets, but there were some inconsitencies during sync and the
>> xfs filesystem on both arrays had to be repaired. Are these problems
>> caused by the pm resets ?
>>
>
> libata EH won't lose any data as long as the hardware doesn't. If power
> fluctuates causing your drive to briefly power down - this does happen and
> you can hear the drive doing emergency unload when it happens, the data in
> write buffer can be lost. On coming back, all that libata can know is
> that the PHY suffered brief connection loss, so it resets the device and
> goes on, so the data in the cache is lost now. It's basically pulling the
> power plug from the harddrive while write is going on and connecting it
> back quickly. You're bound to lose data.
>
After I got the new PSU and the raid was in full sync without any error
for 48h, I thought all problems were gone. Today the sata errors
reappeared and whenever the load is high enough I get the following:
ata10.00: failed to read SCR 1 (Emask=0x40)
ata10.01: failed to read SCR 1 (Emask=0x40)
ata10.02: failed to read SCR 1 (Emask=0x40)
ata10.03: failed to read SCR 1 (Emask=0x40)
ata10.04: failed to read SCR 1 (Emask=0x40)
ata10.05: failed to read SCR 1 (Emask=0x40)
ata10.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.02: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata10.02: status: { DRDY }
ata10.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.15: hard resetting link
ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata10.00: hard resetting link
ata10.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.01: hard resetting link
ata10.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.02: hard resetting link
ata10.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.03: hard resetting link
ata10.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.04: hard resetting link
ata10.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.05: hard resetting link
ata10.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata10.00: configured for UDMA/100
ata10.01: configured for UDMA/100
ata10.02: configured for UDMA/100
ata10.03: configured for UDMA/100
ata10.04: configured for UDMA/100
ata10: EH complete
sd 9:0:0:0: [sdl] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdl] Write Protect is off
sd 9:0:0:0: [sdl] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:1:0:0: [sdm] 976773168 512-byte hardware sectors (500108 MB)
sd 9:1:0:0: [sdm] Write Protect is off
sd 9:1:0:0: [sdm] Mode Sense: 00 3a 00 00
sd 9:1:0:0: [sdm] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:2:0:0: [sdn] 976773168 512-byte hardware sectors (500108 MB)
sd 9:2:0:0: [sdn] Write Protect is off
sd 9:2:0:0: [sdn] Mode Sense: 00 3a 00 00
sd 9:2:0:0: [sdn] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:3:0:0: [sdo] 976773168 512-byte hardware sectors (500108 MB)
sd 9:3:0:0: [sdo] Write Protect is off
sd 9:3:0:0: [sdo] Mode Sense: 00 3a 00 00
sd 9:3:0:0: [sdo] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:4:0:0: [sdp] 976773168 512-byte hardware sectors (500108 MB)
sd 9:4:0:0: [sdp] Write Protect is off
sd 9:4:0:0: [sdp] Mode Sense: 00 3a 00 00
sd 9:4:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:0:0:0: [sdl] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdl] Write Protect is off
sd 9:0:0:0: [sdl] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:1:0:0: [sdm] 976773168 512-byte hardware sectors (500108 MB)
sd 9:1:0:0: [sdm] Write Protect is off
sd 9:1:0:0: [sdm] Mode Sense: 00 3a 00 00
sd 9:1:0:0: [sdm] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:2:0:0: [sdn] 976773168 512-byte hardware sectors (500108 MB)
sd 9:2:0:0: [sdn] Write Protect is off
sd 9:2:0:0: [sdn] Mode Sense: 00 3a 00 00
sd 9:2:0:0: [sdn] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:3:0:0: [sdo] 976773168 512-byte hardware sectors (500108 MB)
sd 9:3:0:0: [sdo] Write Protect is off
sd 9:3:0:0: [sdo] Mode Sense: 00 3a 00 00
sd 9:3:0:0: [sdo] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:4:0:0: [sdp] 976773168 512-byte hardware sectors (500108 MB)
sd 9:4:0:0: [sdp] Write Protect is off
sd 9:4:0:0: [sdp] Mode Sense: 00 3a 00 00
sd 9:4:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata10.00: failed to read SCR 1 (Emask=0x40)
ata10.01: failed to read SCR 1 (Emask=0x40)
ata10.02: failed to read SCR 1 (Emask=0x40)
ata10.03: failed to read SCR 1 (Emask=0x40)
ata10.04: failed to read SCR 1 (Emask=0x40)
ata10.05: failed to read SCR 1 (Emask=0x40)
ata10.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.02: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 2 cdb 0x0 data 0
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata10.02: status: { DRDY }
ata10.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.15: hard resetting link
ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata10.00: hard resetting link
ata10.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.01: hard resetting link
ata10.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.02: hard resetting link
ata10.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.03: hard resetting link
ata10.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.04: hard resetting link
ata10.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.05: hard resetting link
ata10.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata10.00: configured for UDMA/100
ata10.01: configured for UDMA/100
ata10.02: configured for UDMA/100
ata10.03: configured for UDMA/100
ata10.04: configured for UDMA/100
ata10: EH complete
sd 9:0:0:0: [sdl] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdl] Write Protect is off
sd 9:0:0:0: [sdl] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:1:0:0: [sdm] 976773168 512-byte hardware sectors (500108 MB)
sd 9:1:0:0: [sdm] Write Protect is off
sd 9:1:0:0: [sdm] Mode Sense: 00 3a 00 00
sd 9:1:0:0: [sdm] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:2:0:0: [sdn] 976773168 512-byte hardware sectors (500108 MB)
sd 9:2:0:0: [sdn] Write Protect is off
sd 9:2:0:0: [sdn] Mode Sense: 00 3a 00 00
sd 9:2:0:0: [sdn] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:3:0:0: [sdo] 976773168 512-byte hardware sectors (500108 MB)
sd 9:3:0:0: [sdo] Write Protect is off
sd 9:3:0:0: [sdo] Mode Sense: 00 3a 00 00
sd 9:3:0:0: [sdo] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:4:0:0: [sdp] 976773168 512-byte hardware sectors (500108 MB)
sd 9:4:0:0: [sdp] Write Protect is off
sd 9:4:0:0: [sdp] Mode Sense: 00 3a 00 00
sd 9:4:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:0:0:0: [sdl] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdl] Write Protect is off
sd 9:0:0:0: [sdl] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:1:0:0: [sdm] 976773168 512-byte hardware sectors (500108 MB)
sd 9:1:0:0: [sdm] Write Protect is off
sd 9:1:0:0: [sdm] Mode Sense: 00 3a 00 00
sd 9:1:0:0: [sdm] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:2:0:0: [sdn] 976773168 512-byte hardware sectors (500108 MB)
sd 9:2:0:0: [sdn] Write Protect is off
sd 9:2:0:0: [sdn] Mode Sense: 00 3a 00 00
sd 9:2:0:0: [sdn] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:3:0:0: [sdo] 976773168 512-byte hardware sectors (500108 MB)
sd 9:3:0:0: [sdo] Write Protect is off
sd 9:3:0:0: [sdo] Mode Sense: 00 3a 00 00
sd 9:3:0:0: [sdo] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:4:0:0: [sdp] 976773168 512-byte hardware sectors (500108 MB)
sd 9:4:0:0: [sdp] Write Protect is off
sd 9:4:0:0: [sdp] Mode Sense: 00 3a 00 00
sd 9:4:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-02-01 13:42 ` dusty
@ 2008-02-01 13:53 ` Tejun Heo
2008-02-01 14:06 ` Mark Lord
1 sibling, 0 replies; 16+ messages in thread
From: Tejun Heo @ 2008-02-01 13:53 UTC (permalink / raw)
To: dusty; +Cc: linux-ide
dusty@gmx.li wrote:
>>> Sorry for my late answer, but i had to sort this out first.
>>> After replacing the first PSU with a new Corsair 650W the power no
>>> longer fluctuated more than 0,01 V (and this only when booting up the
>>> drives...) I did a full resync on both raid arrays and got no more
>>> errors or resets, but there were some inconsitencies during sync and the
>>> xfs filesystem on both arrays had to be repaired. Are these problems
>>> caused by the pm resets ?
>>>
>> libata EH won't lose any data as long as the hardware doesn't. If power
>> fluctuates causing your drive to briefly power down - this does happen and
>> you can hear the drive doing emergency unload when it happens, the data in
>> write buffer can be lost. On coming back, all that libata can know is
>> that the PHY suffered brief connection loss, so it resets the device and
>> goes on, so the data in the cache is lost now. It's basically pulling the
>> power plug from the harddrive while write is going on and connecting it
>> back quickly. You're bound to lose data.
>>
> After I got the new PSU and the raid was in full sync without any error
> for 48h, I thought all problems were gone. Today the sata errors
> reappeared and whenever the load is high enough I get the following:
>
> ata10.02: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata10.02: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 2 cdb 0x0 data 0
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Those are time outs for FLUSH. libata told the drive to flush its cache
onto the media and the drive failed to finish that in 30secs. As FLUSH
itself is a non-data command, this problem usually isn't caused by
transport layer problems. This is a pretty good clue that the drive is
knee-deep in s**t. What does 'smartctl -a' tell you about the drive?
--
tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-02-01 13:42 ` dusty
2008-02-01 13:53 ` Tejun Heo
@ 2008-02-01 14:06 ` Mark Lord
2008-02-01 15:05 ` Tejun Heo
2008-02-01 15:12 ` dusty
1 sibling, 2 replies; 16+ messages in thread
From: Mark Lord @ 2008-02-01 14:06 UTC (permalink / raw)
To: dusty; +Cc: Tejun Heo, linux-ide
dusty@gmx.li wrote:
>>> Sorry for my late answer, but i had to sort this out first.
>>> After replacing the first PSU with a new Corsair 650W the power no
>>> longer fluctuated more than 0,01 V (and this only when booting up the
>>> drives...) I did a full resync on both raid arrays and got no more
>>> errors or resets, but there were some inconsitencies during sync and the
>>> xfs filesystem on both arrays had to be repaired. Are these problems
>>> caused by the pm resets ?
>>>
>> libata EH won't lose any data as long as the hardware doesn't. If power
>> fluctuates causing your drive to briefly power down - this does happen and
>> you can hear the drive doing emergency unload when it happens, the data in
>> write buffer can be lost. On coming back, all that libata can know is
>> that the PHY suffered brief connection loss, so it resets the device and
>> goes on, so the data in the cache is lost now. It's basically pulling the
>> power plug from the harddrive while write is going on and connecting it
>> back quickly. You're bound to lose data.
>>
> After I got the new PSU and the raid was in full sync without any error
> for 48h, I thought all problems were gone. Today the sata errors
> reappeared and whenever the load is high enough I get the following:
..
What exact brand/model drives are those again (hdparm --Istdout, please) ?
If I have a similar unit here, I may try to reproduce this.
Cheers
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-02-01 14:06 ` Mark Lord
@ 2008-02-01 15:05 ` Tejun Heo
2008-02-05 18:50 ` dusty
2008-02-01 15:12 ` dusty
1 sibling, 1 reply; 16+ messages in thread
From: Tejun Heo @ 2008-02-01 15:05 UTC (permalink / raw)
To: Mark Lord; +Cc: dusty, linux-ide
Mark Lord wrote:
>> After I got the new PSU and the raid was in full sync without any error
>> for 48h, I thought all problems were gone. Today the sata errors
>> reappeared and whenever the load is high enough I get the following:
> ..
>
> What exact brand/model drives are those again (hdparm --Istdout, please) ?
>
> If I have a similar unit here, I may try to reproduce this.
Dusty, can you please provide the info for Mark? Let's see if Mark can
reproduce this.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-02-01 14:06 ` Mark Lord
2008-02-01 15:05 ` Tejun Heo
@ 2008-02-01 15:12 ` dusty
1 sibling, 0 replies; 16+ messages in thread
From: dusty @ 2008-02-01 15:12 UTC (permalink / raw)
To: Mark Lord; +Cc: dusty, Tejun Heo, linux-ide
Am Fr, 1.02.2008, 14:06, schrieb Mark Lord:
> dusty@gmx.li wrote:
>>>> Sorry for my late answer, but i had to sort this out first.
>>>> After replacing the first PSU with a new Corsair 650W the power no
>>>> longer fluctuated more than 0,01 V (and this only when booting up
>>>> the drives...) I did a full resync on both raid arrays and got no
>>>> more errors or resets, but there were some inconsitencies during
>>>> sync and the xfs filesystem on both arrays had to be repaired. Are
>>>> these problems caused by the pm resets ?
>>>>
>>> libata EH won't lose any data as long as the hardware doesn't. If
>>> power fluctuates causing your drive to briefly power down - this does
>>> happen and you can hear the drive doing emergency unload when it
>>> happens, the data in write buffer can be lost. On coming back, all
>>> that libata can know is that the PHY suffered brief connection loss,
>>> so it resets the device and goes on, so the data in the cache is lost
>>> now. It's basically pulling the power plug from the harddrive while
>>> write is going on and connecting it back quickly. You're bound to
>>> lose data.
>>>
>> After I got the new PSU and the raid was in full sync without any error
>> for 48h, I thought all problems were gone. Today the sata errors
>> reappeared and whenever the load is high enough I get the following:
> ..
>
>
> What exact brand/model drives are those again (hdparm --Istdout, please)
> ?
>
>
> If I have a similar unit here, I may try to reproduce this.
>
>
Yes, of course. This is the failing drive:
hdparm --Istdout /dev/sdn
/dev/sdn:
0040 3fff c837 0010 8856 022a 003f 0000
0000 0000 5330 4d55 4a31 4650 3930 3136
3432 2020 2020 2020 0003 8000 0004 4352
3130 302d 3131 5341 4d53 554e 4720 4844
3530 314c 4a20 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8010
0000 2f00 4000 0200 0200 0007 3fff 0010
003f fc10 00fb 0000 ffff 0fff 0000 0007
0003 0078 0078 0078 0078 0000 0000 0000
0000 0000 0000 001f 0706 0000 004c 0040
01f8 0052 746b 7f01 4123 7469 bc01 4123
20ff 0054 0054 0000 fffe 0000 fe00 0000
0000 0000 0000 0000 6030 3a38 0000 0000
0000 0000 0000 0000 5000 0f00 1b90 1642
0000 0000 0000 0000 0000 0000 0000 4014
4014 0000 0000 0000 0000 0000 0000 0000
0021 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 ffff 0400 0e00 0003
0000 9a00 0300 2400 6a20 3231 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 003f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 100f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0001 0400 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 9ca5
And now all others: (All the same model Samsung HD501LJ)
hdparm --Istdout /dev/sdo
/dev/sdo:
0040 3fff c837 0010 8856 022a 003f 0000
0000 0000 5330 4d55 4a31 4450 3932 3433
3833 2020 2020 2020 0003 8000 0004 4352
3130 302d 3131 5341 4d53 554e 4720 4844
3530 314c 4a20 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8010
0000 2f00 4000 0200 0200 0007 3fff 0010
003f fc10 00fb 0000 ffff 0fff 0000 0007
0003 0078 0078 0078 0078 0000 0000 0000
0000 0000 0000 001f 0706 0000 004c 0040
01f8 0052 746b 7f01 4123 7469 bc01 4123
20ff 0054 0054 0000 fffe 0000 fe00 0000
0000 0000 0000 0000 6030 3a38 0000 0000
0000 0000 0000 0000 5000 0f00 1b92 4383
0000 0000 0000 0000 0000 0000 0000 4014
4014 0000 0000 0000 0000 0000 0000 0000
0021 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 ffff 0400 0e00 0003
0000 9a00 0300 2400 6a20 3231 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 003f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 100f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0001 0400 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 27a5
hdparm --Istdout /dev/sdp
/dev/sdp:
0040 3fff c837 0010 8856 022a 003f 0000
0000 0000 2020 2020 2020 5330 5a46 4a31
4d50 3930 3538 3734 0003 8000 0004 4352
3130 302d 3131 5341 4d53 554e 4720 4844
3530 314c 4a20 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8010
0000 2f00 4000 0200 0200 0007 3fff 0010
003f fc10 00fb 0000 ffff 0fff 0000 0007
0003 0078 0078 0078 0078 0000 0000 0000
0000 0000 0000 001f 0706 0000 004c 0040
01f8 0052 746b 7f01 4123 7469 be01 4123
20ff 0054 0054 0000 fffe 0000 fe80 0000
0000 0000 0000 0000 6030 3a38 0000 0000
0000 0000 0000 0000 5000 0f00 0b0f 0100
0000 0000 0000 0000 0000 0000 0000 4014
4014 0000 0000 0000 0000 0000 0000 0000
0021 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 ffff 0400 0e00 0003
0000 9a00 0300 2400 6a20 3231 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 003f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 100f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0001 0400 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 f2a5
hdparm --Istdout /dev/sdi
/dev/sdi:
0040 3fff c837 0010 8856 022a 003f 0000
0000 0000 5330 4d55 4a31 3350 3131 3937
3436 2020 2020 2020 0003 8000 0004 4352
3130 302d 3130 5341 4d53 554e 4720 4844
3530 314c 4a20 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8010
0000 2f00 4000 0200 0200 0007 3fff 0010
003f fc10 00fb 0110 ffff 0fff 0000 0007
0003 0078 0078 0078 0078 0000 0000 0000
0000 0000 0000 001f 0706 0000 004c 0040
01f8 0052 746b 7f01 4123 7469 bc01 4123
20ff 0054 0054 0000 fffe 0000 fe00 0000
0000 0000 0000 0000 6030 3a38 0000 0000
0000 0000 0000 0000 5000 0f00 1b11 9746
0000 0000 0000 0000 0000 0000 0000 4010
4010 0000 0000 0000 0000 0000 0000 0000
0021 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 ffff 0400 0e00 0003
0000 9a00 0300 2400 6420 3231 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 003f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 100f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0001 0400 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 a1a5
hdparm --Istdout /dev/sdj
/dev/sdj:
0040 3fff c837 0010 8856 022a 003f 0000
0000 0000 5330 4d55 4a31 3350 3131 3937
3434 2020 2020 2020 0003 8000 0004 4352
3130 302d 3130 5341 4d53 554e 4720 4844
3530 314c 4a20 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8010
0000 2f00 4000 0200 0200 0007 3fff 0010
003f fc10 00fb 0110 ffff 0fff 0000 0007
0003 0078 0078 0078 0078 0000 0000 0000
0000 0000 0000 001f 0706 0000 004c 0040
01f8 0052 746b 7f01 4123 7469 bc01 4123
20ff 0054 0054 0000 fffe 0000 fe00 0000
0000 0000 0000 0000 6030 3a38 0000 0000
0000 0000 0000 0000 5000 0f00 1b11 9744
0000 0000 0000 0000 0000 0000 0000 4010
4010 0000 0000 0000 0000 0000 0000 0000
0021 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 ffff 0400 0e00 0003
0000 9a00 0300 2400 6420 3231 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 003f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 100f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0001 0400 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 a5a5
hdparm --Istdout /dev/sdk
/dev/sdk:
0040 3fff c837 0010 8856 022a 003f 0000
0000 0000 5330 4d55 4a31 3350 3131 3937
3437 2020 2020 2020 0003 8000 0004 4352
3130 302d 3130 5341 4d53 554e 4720 4844
3530 314c 4a20 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8010
0000 2f00 4000 0200 0200 0007 3fff 0010
003f fc10 00fb 0110 ffff 0fff 0000 0007
0003 0078 0078 0078 0078 0000 0000 0000
0000 0000 0000 001f 0706 0000 004c 0040
01f8 0052 746b 7f01 4123 7469 bc01 4123
20ff 0054 0054 0000 fffe 0000 fe00 0000
0000 0000 0000 0000 6030 3a38 0000 0000
0000 0000 0000 0000 5000 0f00 1b11 9747
0000 0000 0000 0000 0000 0000 0000 4010
4010 0000 0000 0000 0000 0000 0000 0000
0021 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 ffff 0400 0e00 0003
0000 9a00 0300 2400 6420 3231 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 003f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 100f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0001 0400 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 9fa5
hdparm --Istdout /dev/sdl
/dev/sdl:
0040 3fff c837 0010 8856 022a 003f 0000
0000 0000 5330 4d55 4a31 3350 3131 3937
3435 2020 2020 2020 0003 8000 0004 4352
3130 302d 3130 5341 4d53 554e 4720 4844
3530 314c 4a20 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8010
0000 2f00 4000 0200 0200 0007 3fff 0010
003f fc10 00fb 0110 ffff 0fff 0000 0007
0003 0078 0078 0078 0078 0000 0000 0000
0000 0000 0000 001f 0706 0000 004c 0040
01f8 0052 746b 7f01 4123 7469 bc01 4123
20ff 0054 0054 0000 fffe 0000 fe00 0000
0000 0000 0000 0000 6030 3a38 0000 0000
0000 0000 0000 0000 5000 0f00 1b11 9745
0000 0000 0000 0000 0000 0000 0000 4010
4010 0000 0000 0000 0000 0000 0000 0000
0021 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 ffff 0400 0e00 0003
0000 9a00 0300 2400 6420 3231 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 003f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 100f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0001 0400 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 a3a5
hdparm --Istdout /dev/sdm
/dev/sdm:
0040 3fff c837 0010 8856 022a 003f 0000
0000 0000 5330 4d55 4a31 3350 3739 3830
3436 2020 2020 2020 0003 8000 0004 4352
3130 302d 3130 5341 4d53 554e 4720 4844
3530 314c 4a20 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8010
0000 2f00 4000 0200 0200 0007 3fff 0010
003f fc10 00fb 0000 ffff 0fff 0000 0007
0003 0078 0078 0078 0078 0000 0000 0000
0000 0000 0000 001f 0706 0000 004c 0040
01f8 0052 746b 7f01 4123 7469 bc01 4123
20ff 0054 0054 0000 fffe 0000 fe00 0000
0000 0000 0000 0000 6030 3a38 0000 0000
0000 0000 0000 0000 5000 0f00 1b79 8046
0000 0000 0000 0000 0000 0000 0000 4010
4010 0000 0000 0000 0000 0000 0000 0000
0021 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 ffff 0400 0e00 0003
0000 9a00 0300 2400 6420 3231 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 003f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 100f 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0001 0400 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 5ba5
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: libata pm
2008-02-01 15:05 ` Tejun Heo
@ 2008-02-05 18:50 ` dusty
0 siblings, 0 replies; 16+ messages in thread
From: dusty @ 2008-02-05 18:50 UTC (permalink / raw)
To: Tejun Heo; +Cc: Mark Lord, dusty, linux-ide
Hi everybody,
it looks like this will be a never ending story...
>>> After I got the new PSU and the raid was in full sync without any
>>> error for 48h, I thought all problems were gone. Today the sata errors
>>> reappeared and whenever the load is high enough I get the following:
>>>
I exchanged two (probably failing) of the eight harddrives with new ones.
All remaining disks have a good smart state and are fully readable when
the raid is not active. As long as I mount the filesystem on the raid
readonly there wont happen any error, but the moment I mount it rw and try
to copy something to the fs on the raid I get the already known timeout.
At least I get a little bit desperate now...
ata10.00: failed to read SCR 1 (Emask=0x40)
ata10.01: failed to read SCR 1 (Emask=0x40)
ata10.02: failed to read SCR 1 (Emask=0x40)
ata10.03: failed to read SCR 1 (Emask=0x40)
ata10.04: failed to read SCR 1 (Emask=0x40)
ata10.05: failed to read SCR 1 (Emask=0x40)
ata10.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.01: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 1 cdb 0x0 data 0
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata10.01: status: { DRDY }
ata10.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.15: hard resetting link
ata10.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata10.00: hard resetting link
ata10.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.01: hard resetting link
ata10.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.02: hard resetting link
ata10.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.03: hard resetting link
ata10.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.04: hard resetting link
ata10.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.05: hard resetting link
ata10.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata10.00: configured for UDMA/100
ata10.01: configured for UDMA/100
ata10.03: configured for UDMA/100
ata10.04: configured for UDMA/100
ata10: EH complete
sd 9:0:0:0: [sdl] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdl] Write Protect is off
sd 9:0:0:0: [sdl] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:1:0:0: [sdm] 976773168 512-byte hardware sectors (500108 MB)
sd 9:1:0:0: [sdm] Write Protect is off
sd 9:1:0:0: [sdm] Mode Sense: 00 3a 00 00
sd 9:1:0:0: [sdm] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:2:0:0: [sdn] 976773168 512-byte hardware sectors (500108 MB)
sd 9:2:0:0: [sdn] Write Protect is off
sd 9:2:0:0: [sdn] Mode Sense: 00 3a 00 00
sd 9:2:0:0: [sdn] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:3:0:0: [sdo] 976773168 512-byte hardware sectors (500108 MB)
sd 9:3:0:0: [sdo] Write Protect is off
sd 9:3:0:0: [sdo] Mode Sense: 00 3a 00 00
sd 9:3:0:0: [sdo] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 9:4:0:0: [sdp] 976773168 512-byte hardware sectors (500108 MB)
sd 9:4:0:0: [sdp] Write Protect is off
sd 9:4:0:0: [sdp] Mode Sense: 00 3a 00 00
sd 9:4:0:0: [sdp] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2008-02-05 18:50 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-26 18:03 libata pm dusty
2008-01-26 20:05 ` dusty
2008-01-26 23:33 ` Tejun Heo
2008-01-27 1:38 ` dusty
2008-01-27 19:34 ` dusty
2008-01-28 1:17 ` Tejun Heo
2008-01-28 10:31 ` dusty
2008-01-28 12:03 ` Tejun Heo
2008-01-30 21:34 ` dusty
2008-01-31 1:13 ` Tejun Heo
2008-02-01 13:42 ` dusty
2008-02-01 13:53 ` Tejun Heo
2008-02-01 14:06 ` Mark Lord
2008-02-01 15:05 ` Tejun Heo
2008-02-05 18:50 ` dusty
2008-02-01 15:12 ` dusty
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).