* sil24 PMP works with ST3500641AS but not HDS721010KLA330
@ 2007-10-02 17:04 Marc MERLIN
2007-10-02 17:15 ` Marc MERLIN
` (3 more replies)
0 siblings, 4 replies; 10+ messages in thread
From: Marc MERLIN @ 2007-10-02 17:04 UTC (permalink / raw)
To: htejun, linux-ide
Howdy,
I've had a system with 2.6.22.1 for a while, running 10 drives
behind a PMP on a sil24 card with no problems.
Recently, I swapped 5 250GB drives with 5 TB drives.
The 5 TB drives eventually get detected, but do not work reliably.
Details are below.
This is all on 2.6.22.1-libata-tj-20070803.
I noticed that 20070808 is out, but it says it fixed NCQ over PMP,
and NCQ was working fine with my 500GB drives, so I'm not sure it's that.
I'll try upgrading, but I'm pasting my current info below in case there
are other things I should try
Thanks
Marc
At boot time, the good (500GB) drives give:
> ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata4.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x9/0x9
> ata4.00: hard resetting link
> ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.01: hard resetting link
> ata4.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.02: hard resetting link
> ata4.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.03: hard resetting link
> ata4.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.04: hard resetting link
> ata4.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.05: hard resetting link
> ata4.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata4.00: ATA-7: ST3500641AS, 3.AAE, max UDMA/133
> ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
> ata4.00: configured for UDMA/100
> ata4.01: ATA-7: ST3500641AS, 3.AAE, max UDMA/133
> ata4.01: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.01: configured for UDMA/100
> ata4.02: ATA-7: ST3500641AS, 3.AAE, max UDMA/133
> ata4.02: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.02: configured for UDMA/100
> ata4.03: ATA-7: ST3500641AS, 3.AAD, max UDMA/133
> ata4.03: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.03: configured for UDMA/100
> ata4.04: ATA-7: ST3500641AS, 3.AAD, max UDMA/133
> ata4.04: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.04: configured for UDMA/100
> ata4: EH complete
> (...)
> PM: Adding info for No Bus:target4:0:0
> scsi 4:0:0:0: Direct-Access ATA ST3500641AS 3.AA PQ: 0 ANSI: 5
> PM: Adding info for scsi:4:0:0:0
> sd 4:0:0:0: [sdh] 976773168 512-byte hardware sectors (500108 MB)
> sd 4:0:0:0: [sdh] Write Protect is off
> sd 4:0:0:0: [sdh] Mode Sense: 00 3a 00 00
> sd 4:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sd 4:0:0:0: [sdh] 976773168 512-byte hardware sectors (500108 MB)
> sd 4:0:0:0: [sdh] Write Protect is off
> sd 4:0:0:0: [sdh] Mode Sense: 00 3a 00 00
> sd 4:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sdh: sdh1
> sd 4:0:0:0: [sdh] Attached SCSI disk
The new drives give:
> ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x9/0x9
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.01: hard resetting link
> ata3.01: softreset failed (timeout)
> ata3.01: hard resetting link
> ata3.01: COMRESET failed (errno=-5)
> ata3.01: reset failed, giving up
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.01: hard resetting link
> ata3.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.02: hard resetting link
> ata3.02: softreset failed (timeout)
> ata3.02: hard resetting link
> ata3.02: COMRESET failed (errno=-5)
> ata3.02: reset failed, giving up
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.01: hard resetting link
> ata3.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.02: hard resetting link
> ata3.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.03: hard resetting link
> ata3.03: softreset failed (timeout)
> ata3.03: hard resetting link
> ata3.03: COMRESET failed (errno=-5)
> ata3.03: reset failed, giving up
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.01: hard resetting link
> ata3.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.02: hard resetting link
> ata3.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.03: hard resetting link
> ata3.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.04: hard resetting link
> ata3.04: softreset failed (timeout)
> ata3.04: hard resetting link
> ata3.04: COMRESET failed (errno=-5)
> ata3.04: reset failed, giving up
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.01: hard resetting link
> ata3.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.02: hard resetting link
> ata3.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.03: hard resetting link
> ata3.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.04: hard resetting link
> ata3.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.05: hard resetting link
> ata3.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata3.00: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32)
> ata3.00: configured for UDMA/100
> ata3.01: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata3.01: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata3.01: configured for UDMA/100
> ata3.02: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata3.02: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata3.02: configured for UDMA/100
> ata3.03: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata3.03: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata3.03: configured for UDMA/100
> ata3.04: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata3.04: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata3.04: configured for UDMA/100
> ata3: EH complete
> (...)
> PM: Adding info for No Bus:target3:0:0
> scsi 3:0:0:0: Direct-Access ATA Hitachi HDS72101 GKAO PQ: 0 ANSI: 5
> PM: Adding info for scsi:3:0:0:0
> sd 3:0:0:0: [sdc] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 3:0:0:0: [sdc] Write Protect is off
> sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sd 3:0:0:0: [sdc] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 3:0:0:0: [sdc] Write Protect is off
> sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sdc: sdc1
> sd 3:0:0:0: [sdc] Attached SCSI dis
While building the RAID array, I got a couple of these, although the array
did sync overnight.
> ata3.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata3.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata3.02: exception Emask 0x100 SAct 0x400 SErr 0x0 action 0x6 frozen
> ata3.02: cmd 60/28:50:3f:91:85/00:00:0a:00:00/40 tag 10 cdb 0x0 data 20480 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.03: exception Emask 0x100 SAct 0x58228004 SErr 0x0 action 0x6 frozen
> ata3.03: cmd 60/08:10:57:8f:85/00:00:0a:00:00/40 tag 2 cdb 0x0 data 4096 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.03: cmd 60/28:78:3f:91:85/00:00:0a:00:00/40 tag 15 cdb 0x0 data 20480 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.03: cmd 60/a8:88:3f:8e:85/00:00:0a:00:00/40 tag 17 cdb 0x0 data 86016 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.03: cmd 60/58:a8:e7:8e:85/00:00:0a:00:00/40 tag 21 cdb 0x0 data 45056 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.03: cmd 60/18:d8:3f:8f:85/00:00:0a:00:00/40 tag 27 cdb 0x0 data 12288 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.03: cmd 60/00:e0:3f:90:85/01:00:0a:00:00/40 tag 28 cdb 0x0 data 131072 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.03: cmd 60/e0:f0:5f:8f:85/00:00:0a:00:00/40 tag 30 cdb 0x0 data 114688 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.04: exception Emask 0x100 SAct 0x139 SErr 0x0 action 0x6 frozen
> ata3.04: cmd 61/00:00:3f:8d:85/01:00:0a:00:00/40 tag 0 cdb 0x0 data 131072 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.04: cmd 61/98:18:3f:8c:85/00:00:0a:00:00/40 tag 3 cdb 0x0 data 77824 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.04: cmd 61/68:20:d7:8c:85/00:00:0a:00:00/40 tag 4 cdb 0x0 data 53248 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.04: cmd 61/d0:28:3f:8b:85/00:00:0a:00:00/40 tag 5 cdb 0x0 data 106496 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.04: cmd 61/30:40:0f:8c:85/00:00:0a:00:00/40 tag 8 cdb 0x0 data 24576 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.01: hard resetting link
> ata3.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.02: hard resetting link
> ata3.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.03: hard resetting link
> ata3.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.04: hard resetting link
> ata3.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.05: hard resetting link
> ata3.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata3.00: configured for UDMA/100
> ata3.01: configured for UDMA/100
> ata3.02: configured for UDMA/100
> ata3.03: configured for UDMA/100
> ata3.04: configured for UDMA/100
> ata3: EH complete
(...)
Eventually, the array went down when I mkfsed it:
> ata3.00: exception Emask 0x100 SAct 0xfdf57e SErr 0x0 action 0x6 frozen
> ata3.00: cmd 61/08:08:e7:02:c6/00:00:03:00:00/40 tag 1 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:10:bf:02:c6/00:00:03:00:00/40 tag 2 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:18:c7:02:c6/00:00:03:00:00/40 tag 3 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:20:3f:03:c6/00:00:03:00:00/40 tag 4 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:28:df:02:c6/00:00:03:00:00/40 tag 5 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:30:47:03:c6/00:00:03:00:00/40 tag 6 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/90:40:d7:01:c6/00:00:03:00:00/40 tag 8 cdb 0x0 data 73728 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/30:50:67:02:c6/00:00:03:00:00/40 tag 10 cdb 0x0 data 24576 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/18:60:97:02:c6/00:00:03:00:00/40 tag 12 cdb 0x0 data 12288 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:68:af:02:c6/00:00:03:00:00/40 tag 13 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:70:b7:02:c6/00:00:03:00:00/40 tag 14 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/10:78:cf:02:c6/00:00:03:00:00/40 tag 15 cdb 0x0 data 8192 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/50:80:ef:02:c6/00:00:03:00:00/40 tag 16 cdb 0x0 data 40960 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:90:4f:03:c6/00:00:03:00:00/40 tag 18 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:98:57:03:c6/00:00:03:00:00/40 tag 19 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:a0:5f:03:c6/00:00:03:00:00/40 tag 20 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:a8:67:03:c6/00:00:03:00:00/40 tag 21 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:b0:6f:03:c6/00:00:03:00:00/40 tag 22 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.00: cmd 61/08:b8:77:03:c6/00:00:03:00:00/40 tag 23 cdb 0x0 data 4096 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.01: exception Emask 0x100 SAct 0x800 SErr 0x0 action 0x6 frozen
> ata3.01: cmd 60/08:58:4f:00:c6/00:00:03:00:00/40 tag 11 cdb 0x0 data 4096 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.02: exception Emask 0x100 SAct 0x1 SErr 0x0 action 0x6 frozen
> ata3.02: cmd 60/08:00:4f:00:c6/00:00:03:00:00/40 tag 0 cdb 0x0 data 4096 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.03: exception Emask 0x100 SAct 0x1020200 SErr 0x0 action 0x6 frozen
> ata3.03: cmd 60/10:48:3f:08:c5/00:00:03:00:00/40 tag 9 cdb 0x0 data 8192 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.03: cmd 61/30:88:f7:02:c5/00:00:03:00:00/40 tag 17 cdb 0x0 data 24576 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.03: cmd 60/08:c0:4f:00:c6/00:00:03:00:00/40 tag 24 cdb 0x0 data 4096 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.04: exception Emask 0x100 SAct 0x80 SErr 0x0 action 0x6 frozen
> ata3.04: cmd 60/08:38:4f:00:c6/00:00:03:00:00/40 tag 7 cdb 0x0 data 4096 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata3.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.01: hard resetting link
> ata3.01: softreset failed (timeout)
> ata3.01: hard resetting link
> ata3.01: COMRESET failed (errno=-5)
> ata3.01: reset failed, giving up
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.01: hard resetting link
> ata3.01: softreset failed (timeout)
> ata3.01: hard resetting link
> ata3.01: COMRESET failed (errno=-5)
> ata3.01: reset failed, giving up
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.01: hard resetting link
> ata3.01: softreset failed (timeout)
> ata3.01: hard resetting link
> ata3.01: COMRESET failed (errno=-5)
> ata3.01: reset failed, giving up
> ata3.01: failed to recover link after 3 tries, disabling
> ata3.01: disabled
> ata3: failed to recover PMP, retrying in 5 secs
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.02: hard resetting link
> ata3.02: softreset failed (timeout)
> ata3.02: hard resetting link
> ata3.02: COMRESET failed (errno=-5)
> ata3.02: reset failed, giving up
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.02: hard resetting link
> ata3.02: softreset failed (timeout)
> ata3.02: hard resetting link
> ata3.02: COMRESET failed (errno=-5)
> ata3.02: reset failed, giving up
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.02: hard resetting link
> ata3.02: softreset failed (timeout)
> ata3.02: hard resetting link
> ata3.02: COMRESET failed (errno=-5)
> ata3.02: reset failed, giving up
> ata3.02: failed to recover link after 3 tries, disabling
> ata3.02: disabled
> ata3: failed to recover PMP, retrying in 5 secs
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.03: hard resetting link
> ata3.03: softreset failed (timeout)
> ata3.03: hard resetting link
> ata3.03: COMRESET failed (errno=-5)
> ata3.03: reset failed, giving up
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.03: hard resetting link
> ata3.03: softreset failed (timeout)
> ata3.03: hard resetting link
> ata3.03: COMRESET failed (errno=-5)
> ata3.03: reset failed, giving up
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.03: hard resetting link
> ata3.03: softreset failed (timeout)
> ata3.03: hard resetting link
> ata3.03: COMRESET failed (errno=-5)
> ata3.03: reset failed, giving up
> ata3.03: failed to recover link after 3 tries, disabling
> ata3.03: disabled
> ata3: failed to recover PMP, retrying in 5 secs
>
> ata3.15: hard resetting link
> ata3.15: softreset failed (timeout)
> ata3.15: hard resetting link
> ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.00: hard resetting link
> ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.05: hard resetting link
> ata3.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata3.00: configured for UDMA/100
> ata3: EH pending after completion, repeating EH (cnt=4)
> sd 3:2:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
> sd 3:2:0:0: [sde] Sense Key : Aborted Command [current] [descriptor]
> Descriptor sense data with sense descriptors (in hex):
> 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
> 00 00 00 00
> sd 3:2:0:0: [sde] Add. Sense: No additional sense information
> end_request: I/O error, dev sde, sector 63307855
> sd 3:2:0:0: rejecting I/O to offline device
> raid5: Disk failure on sde1, disabling device. Operation continuing on 4 devices
> sd 3:2:0:0: rejecting I/O to offline device
> sd 3:4:0:0: rejecting I/O to offline device
> raid5: Disk failure on sdg1, disabling device. Operation continuing on 3 devices
> sd 3:4:0:0: rejecting I/O to offline device
> sage repeated 29 times
> sd 3:3:0:0: rejecting I/O to offline device
> raid5: Disk failure on sdf1, disabling device. Operation continuing on 2 devices
> sd 3:3:0:0: rejecting I/O to offline device
> sage repeated 26 times
> sd 3:1:0:0: rejecting I/O to offline device
> raid5: Disk failure on sdd1, disabling device. Operation continuing on 1 devices
> sd 3:1:0:0: rejecting I/O to offline device
> sage repeated 12 times
> sd 3:2:0:0: rejecting I/O to offline device
> sage repeated 11 times
> sd 3:4:0:0: [sdg] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
> sd 3:4:0:0: [sdg] Sense Key : Aborted Command [current] [descriptor]
> Descriptor sense data with sense descriptors (in hex):
> 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
> 00 00 00 00
> sd 3:4:0:0: [sdg] Add. Sense: No additional sense information
> end_request: I/O error, dev sdg, sector 63307855
> raid5:md5: read error not correctable (sector 63307792 on sdg1).
> sd 3:4:0:0: rejecting I/O to offline device
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sil24 PMP works with ST3500641AS but not HDS721010KLA330
2007-10-02 17:04 sil24 PMP works with ST3500641AS but not HDS721010KLA330 Marc MERLIN
@ 2007-10-02 17:15 ` Marc MERLIN
2007-10-03 2:28 ` Marc MERLIN
` (2 subsequent siblings)
3 siblings, 0 replies; 10+ messages in thread
From: Marc MERLIN @ 2007-10-02 17:15 UTC (permalink / raw)
To: htejun, linux-ide
On Tue, Oct 02, 2007 at 10:04:45AM -0700, Marc MERLIN wrote:
> Howdy,
>
> I've had a system with 2.6.22.1 for a while, running 10 drives
> behind a PMP on a sil24 card with no problems.
I forgot a couple of details:
the PMP is a sil 3726CB
the sil24 card is a 3124
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sil24 PMP works with ST3500641AS but not HDS721010KLA330
2007-10-02 17:04 sil24 PMP works with ST3500641AS but not HDS721010KLA330 Marc MERLIN
2007-10-02 17:15 ` Marc MERLIN
@ 2007-10-03 2:28 ` Marc MERLIN
2007-10-03 2:32 ` Marc MERLIN
2007-10-03 3:30 ` Tejun Heo
2007-10-07 17:22 ` sil24 PMP works with ST3500641AS but not HDS721010KLA330 (mostly solved) Marc MERLIN
3 siblings, 1 reply; 10+ messages in thread
From: Marc MERLIN @ 2007-10-03 2:28 UTC (permalink / raw)
To: htejun, linux-ide
On Tue, Oct 02, 2007 at 10:04:45AM -0700, Marc MERLIN wrote:
> Howdy,
>
> I've had a system with 2.6.22.1 for a while, running 10 drives
> behind a PMP on a sil24 card with no problems.
>
> Recently, I swapped 5 250GB drives with 5 TB drives.
> The 5 TB drives eventually get detected, but do not work reliably.
>
> Details are below.
>
> This is all on 2.6.22.1-libata-tj-20070803.
> I noticed that 20070808 is out, but it says it fixed NCQ over PMP,
> and NCQ was working fine with my 500GB drives, so I'm not sure it's that.
I tried with 20070808. Boot was better, so it seems to have helped.
I guess the NCQ fix was relevant for my TB drives but not needed for the 500GB ones.
I still got this when the array was built, but it didn't seem to prevent it from
being built and from working:
ata3.04: exception Emask 0x0 SAct 0xff SErr 0x0 action 0x2 frozen
ata3.04: cmd 61/c0:00:7f:94:04/00:00:71:00:00/40 tag 0 cdb 0x0 data 98304 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/00:08:3f:95:04/01:00:71:00:00/40 tag 1 cdb 0x0 data 131072 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/08:10:77:94:04/00:00:71:00:00/40 tag 2 cdb 0x0 data 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/90:18:3f:96:04/00:00:71:00:00/40 tag 3 cdb 0x0 data 73728 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/20:20:57:93:04/01:00:71:00:00/40 tag 4 cdb 0x0 data 147456 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/70:28:cf:96:04/00:00:71:00:00/40 tag 5 cdb 0x0 data 57344 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/00:30:3f:97:04/01:00:71:00:00/40 tag 6 cdb 0x0 data 131072 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/20:38:3f:98:04/01:00:71:00:00/40 tag 7 cdb 0x0 data 147456 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.15: hard resetting link
ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata3.00: hard resetting link
ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.01: hard resetting link
ata3.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.02: hard resetting link
ata3.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.03: hard resetting link
ata3.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.04: hard resetting link
ata3.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.05: hard resetting link
ata3.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: configured for UDMA/100
ata3.01: configured for UDMA/100
ata3.02: configured for UDMA/100
ata3.03: configured for UDMA/100
ata3.04: configured for UDMA/100
ata3: EH complete
sd 3:0:0:0: [sdc] 1953525168 512-byte hardware sectors (1000205 MB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:1:0:0: [sdd] 1953525168 512-byte hardware sectors (1000205 MB)
sd 3:1:0:0: [sdd] Write Protect is off
sd 3:1:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 3:1:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:2:0:0: [sde] 1953525168 512-byte hardware sectors (1000205 MB)
sd 3:2:0:0: [sde] Write Protect is off
sd 3:2:0:0: [sde] Mode Sense: 00 3a 00 00
sd 3:2:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:3:0:0: [sdf] 1953525168 512-byte hardware sectors (1000205 MB)
sd 3:3:0:0: [sdf] Write Protect is off
sd 3:3:0:0: [sdf] Mode Sense: 00 3a 00 00
sd 3:3:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:4:0:0: [sdg] 1953525168 512-byte hardware sectors (1000205 MB)
sd 3:4:0:0: [sdg] Write Protect is off
sd 3:4:0:0: [sdg] Mode Sense: 00 3a 00 00
sd 3:4:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:0:0:0: [sdc] 1953525168 512-byte hardware sectors (1000205 MB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:1:0:0: [sdd] 1953525168 512-byte hardware sectors (1000205 MB)
sd 3:1:0:0: [sdd] Write Protect is off
sd 3:1:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 3:1:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:2:0:0: [sde] 1953525168 512-byte hardware sectors (1000205 MB)
sd 3:2:0:0: [sde] Write Protect is off
sd 3:2:0:0: [sde] Mode Sense: 00 3a 00 00
sd 3:2:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:3:0:0: [sdf] 1953525168 512-byte hardware sectors (1000205 MB)
sd 3:3:0:0: [sdf] Write Protect is off
sd 3:3:0:0: [sdf] Mode Sense: 00 3a 00 00
sd 3:3:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:4:0:0: [sdg] 1953525168 512-byte hardware sectors (1000205 MB)
sd 3:4:0:0: [sdg] Write Protect is off
sd 3:4:0:0: [sdg] Mode Sense: 00 3a 00 00
sd 3:4:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sil24 PMP works with ST3500641AS but not HDS721010KLA330
2007-10-03 2:28 ` Marc MERLIN
@ 2007-10-03 2:32 ` Marc MERLIN
0 siblings, 0 replies; 10+ messages in thread
From: Marc MERLIN @ 2007-10-03 2:32 UTC (permalink / raw)
To: htejun, linux-ide
On Tue, Oct 02, 2007 at 07:28:57PM -0700, Marc MERLIN wrote:
> On Tue, Oct 02, 2007 at 10:04:45AM -0700, Marc MERLIN wrote:
> > Howdy,
> >
> > I've had a system with 2.6.22.1 for a while, running 10 drives
> > behind a PMP on a sil24 card with no problems.
> >
> > Recently, I swapped 5 250GB drives with 5 TB drives.
> > The 5 TB drives eventually get detected, but do not work reliably.
> >
> > Details are below.
> >
> > This is all on 2.6.22.1-libata-tj-20070803.
> > I noticed that 20070808 is out, but it says it fixed NCQ over PMP,
> > and NCQ was working fine with my 500GB drives, so I'm not sure it's that.
>
> I tried with 20070808. Boot was better, so it seems to have helped.
> I guess the NCQ fix was relevant for my TB drives but not needed for the 500GB ones.
>
> I still got this when the array was built, but it didn't seem to prevent it from
> being built and from working:
Grr, never mind. Right as I sent this, the array died when I mke2fs'ed it.
Any other suggestions?
ata3.00: exception Emask 0x100 SAct 0x610 SErr 0x0 action 0x6 frozen
ata3.00: cmd 60/18:20:4f:00:48/00:00:02:00:00/40 tag 4 cdb 0x0 data 12288 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.00: cmd 60/10:48:67:00:48/00:00:02:00:00/40 tag 9 cdb 0x0 data 8192 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.00: cmd 60/28:50:77:00:48/00:00:02:00:00/40 tag 10 cdb 0x0 data 20480 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.01: exception Emask 0x100 SAct 0x10000 SErr 0x0 action 0x6 frozen
ata3.01: cmd 60/50:80:4f:00:48/00:00:02:00:00/40 tag 16 cdb 0x0 data 40960 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.02: exception Emask 0x100 SAct 0x20000 SErr 0x0 action 0x6 frozen
ata3.02: cmd 60/50:88:4f:00:48/00:00:02:00:00/40 tag 17 cdb 0x0 data 40960 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.03: exception Emask 0x100 SAct 0x8020 SErr 0x0 action 0x6 frozen
ata3.03: cmd 60/50:28:4f:00:48/00:00:02:00:00/40 tag 5 cdb 0x0 data 40960 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.03: cmd 60/10:78:3f:08:47/00:00:02:00:00/40 tag 15 cdb 0x0 data 8192 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: exception Emask 0x100 SAct 0x7fc48cf SErr 0x0 action 0x6 frozen
ata3.04: cmd 61/38:00:e7:01:48/00:00:02:00:00/40 tag 0 cdb 0x0 data 28672 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/70:08:cf:06:47/00:00:02:00:00/40 tag 1 cdb 0x0 data 57344 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/18:10:bf:01:48/00:00:02:00:00/40 tag 2 cdb 0x0 data 12288 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/10:18:d7:01:48/00:00:02:00:00/40 tag 3 cdb 0x0 data 8192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/20:30:1f:02:48/00:00:02:00:00/40 tag 6 cdb 0x0 data 16384 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/10:38:3f:02:48/00:00:02:00:00/40 tag 7 cdb 0x0 data 8192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/40:58:7f:03:47/00:00:02:00:00/40 tag 11 cdb 0x0 data 32768 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/60:70:d7:03:47/00:00:02:00:00/40 tag 14 cdb 0x0 data 49152 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/58:90:3f:04:47/00:00:02:00:00/40 tag 18 cdb 0x0 data 45056 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/08:98:ff:05:47/00:00:02:00:00/40 tag 19 cdb 0x0 data 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/08:a0:5f:06:47/00:00:02:00:00/40 tag 20 cdb 0x0 data 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/10:a8:bf:06:47/00:00:02:00:00/40 tag 21 cdb 0x0 data 8192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/00:b0:3f:07:47/01:00:02:00:00/40 tag 22 cdb 0x0 data 131072 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/a8:b8:9f:00:48/00:00:02:00:00/40 tag 23 cdb 0x0 data 86016 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/18:c0:47:01:48/00:00:02:00:00/40 tag 24 cdb 0x0 data 12288 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/20:c8:5f:01:48/00:00:02:00:00/40 tag 25 cdb 0x0 data 16384 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.04: cmd 61/40:d0:7f:01:48/00:00:02:00:00/40 tag 26 cdb 0x0 data 32768 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen
ata3.15: hard resetting link
ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata3.00: hard resetting link
ata3.00: softreset failed (timeout)
ata3.00: hard resetting link
ata3.00: COMRESET failed (errno=-5)
ata3.00: reset failed, giving up
ata3.15: hard resetting link
ata3.15: softreset failed (timeout)
ata3.15: hard resetting link
ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata3.00: hard resetting link
ata3.00: softreset failed (timeout)
ata3.00: hard resetting link
ata3.00: COMRESET failed (errno=-5)
ata3.00: reset failed, giving up
ata3.15: hard resetting link
ata3.15: softreset failed (timeout)
ata3.15: hard resetting link
ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata3.00: hard resetting link
ata3.00: softreset failed (timeout)
ata3.00: hard resetting link
ata3.00: COMRESET failed (errno=-5)
ata3.00: reset failed, giving up
ata3.00: failed to recover link after 3 tries, disabling
ata3.00: disabled
ata3: failed to recover PMP, retrying in 5 secs
ata3.03: failed to recover link after 3 tries, disabling
ata3.03: disabled
ata3: failed to recover PMP, retrying in 5 secs
ata3.15: hard resetting link
ata3.15: softreset failed (timeout)
ata3.15: hard resetting link
ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
ata3.04: hard resetting link
ata3.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.05: hard resetting link
ata3.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.04: configured for UDMA/100
sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sd 3:0:0:0: [sdc] Sense Key : Aborted Command [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
00 00 00 00
sd 3:0:0:0: [sdc] Add. Sense: No additional sense information
end_request: I/O error, dev sdc, sector 38273103
sd 3:3:0:0: [sdf] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sd 3:3:0:0: [sdf] Sense Key : Aborted Command [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
00 00 00 00
sd 3:3:0:0: [sdf] Add. Sense: No additional sense information
end_request: I/O error, dev sdf, sector 38273103
sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sd 3:0:0:0: [sdc] Sense Key : Aborted Command [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
00 00 00 00
sd 3:0:0:0: [sdc] Add. Sense: No additional sense information
end_request: I/O error, dev sdc, sector 38273127
sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sd 3:0:0:0: [sdc] Sense Key : Aborted Command [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
00 00 00 00
sd 3:0:0:0: [sdc] Add. Sense: No additional sense information
end_request: I/O error, dev sdc, sector 38273143
sd 3:0:0:0: rejecting I/O to offline device
raid5: Disk failure on sdc1, disabling device. Operation continuing on 4 devices
sd 3:3:0:0: rejecting I/O to offline device
sd 3:0:0:0: rejecting I/O to offline device
raid5: Disk failure on sdf1, disabling device. Operation continuing on 3 devices
sd 3:3:0:0: rejecting I/O to offline device
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sil24 PMP works with ST3500641AS but not HDS721010KLA330
2007-10-02 17:04 sil24 PMP works with ST3500641AS but not HDS721010KLA330 Marc MERLIN
2007-10-02 17:15 ` Marc MERLIN
2007-10-03 2:28 ` Marc MERLIN
@ 2007-10-03 3:30 ` Tejun Heo
2007-10-03 5:59 ` Marc MERLIN
2007-10-07 17:22 ` sil24 PMP works with ST3500641AS but not HDS721010KLA330 (mostly solved) Marc MERLIN
3 siblings, 1 reply; 10+ messages in thread
From: Tejun Heo @ 2007-10-03 3:30 UTC (permalink / raw)
To: Marc MERLIN; +Cc: linux-ide
Marc MERLIN wrote:
> Howdy,
>
> I've had a system with 2.6.22.1 for a while, running 10 drives
> behind a PMP on a sil24 card with no problems.
>
> Recently, I swapped 5 250GB drives with 5 TB drives.
> The 5 TB drives eventually get detected, but do not work reliably.
1. Does booting with fewer number of drives (say 5) help?
2. Does limiting PHY speed to 1.5Gbps using DIP switch on the harddrive
help?
--
tejun
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sil24 PMP works with ST3500641AS but not HDS721010KLA330
2007-10-03 3:30 ` Tejun Heo
@ 2007-10-03 5:59 ` Marc MERLIN
2007-10-03 6:38 ` Marc MERLIN
0 siblings, 1 reply; 10+ messages in thread
From: Marc MERLIN @ 2007-10-03 5:59 UTC (permalink / raw)
To: Tejun Heo; +Cc: linux-ide
On Wed, Oct 03, 2007 at 12:30:08PM +0900, Tejun Heo wrote:
> 1. Does booting with fewer number of drives (say 5) help?
Boot is ok with 10 drives now with your latest code (20070808 instead
of 20070803)
> 2. Does limiting PHY speed to 1.5Gbps using DIP switch on the harddrive
> help?
Those drives do not have any DIP switches at all. Can I limit this in
software in the driver maybe?
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sil24 PMP works with ST3500641AS but not HDS721010KLA330
2007-10-03 5:59 ` Marc MERLIN
@ 2007-10-03 6:38 ` Marc MERLIN
2007-10-03 14:08 ` Marc MERLIN
0 siblings, 1 reply; 10+ messages in thread
From: Marc MERLIN @ 2007-10-03 6:38 UTC (permalink / raw)
To: Tejun Heo; +Cc: linux-ide
On Tue, Oct 02, 2007 at 10:59:36PM -0700, Marc MERLIN wrote:
> On Wed, Oct 03, 2007 at 12:30:08PM +0900, Tejun Heo wrote:
> > 1. Does booting with fewer number of drives (say 5) help?
>
> Boot is ok with 10 drives now with your latest code (20070808 instead
> of 20070803)
Let me correct this.
Actually 20070803 vs 20070808 doesn't seem to make a difference at boot.
Sometimes the boot is clean, sometimes it's not.
I removed the 5 good drives, moved the 5 "bad" TB ones to the good slots
(i.e. using another swappable backplane, other cables, and another PMP chip
(I have two chips: one in port 1 and 2 of my sil3124).
Unfortunately, moving the drives to all these new things yielded the same
unreliable boot detection so far.
I reseated the drives one more time just to be sure. This time they booted
ok, but I'm pretty sure it's just the random works/doesn't work thing.
I'll rebuild the array overnight and let you know in 8-9h if the array
rebuilt and if it can take a mke2fs without blowing up.
In the meantime, if you have any suggestions for slowing the drive's speed
down to 1.5Gbps, or other ways to debug those random erros I'm seeing, I'm
all ears.
Here is a link to the drive specs if that helps:
http://www.hitachigst.com/portal/site/en/menuitem.8027a91c954924ae4bda9f30eac4f0a0/
Thanks
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sil24 PMP works with ST3500641AS but not HDS721010KLA330
2007-10-03 6:38 ` Marc MERLIN
@ 2007-10-03 14:08 ` Marc MERLIN
0 siblings, 0 replies; 10+ messages in thread
From: Marc MERLIN @ 2007-10-03 14:08 UTC (permalink / raw)
To: Tejun Heo; +Cc: linux-ide
On Tue, Oct 02, 2007 at 11:38:40PM -0700, Marc MERLIN wrote:
> I reseated the drives one more time just to be sure. This time they booted
> ok, but I'm pretty sure it's just the random works/doesn't work thing.
> I'll rebuild the array overnight and let you know in 8-9h if the array
> rebuilt and if it can take a mke2fs without blowing up.
The array just rebuilt, I ran mke2fs, and things indeed blew up like before.
At this point, I'm not sure what else I can try.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sil24 PMP works with ST3500641AS but not HDS721010KLA330 (mostly solved)
2007-10-02 17:04 sil24 PMP works with ST3500641AS but not HDS721010KLA330 Marc MERLIN
` (2 preceding siblings ...)
2007-10-03 3:30 ` Tejun Heo
@ 2007-10-07 17:22 ` Marc MERLIN
2007-10-08 1:06 ` Tejun Heo
3 siblings, 1 reply; 10+ messages in thread
From: Marc MERLIN @ 2007-10-07 17:22 UTC (permalink / raw)
To: htejun, linux-ide
On Tue, Oct 02, 2007 at 10:04:45AM -0700, Marc MERLIN wrote:
> Howdy,
>
> I've had a system with 2.6.22.1 for a while, running 10 drives
> behind a PMP on a sil24 card with no problems.
>
> Recently, I swapped 5 250GB drives with 5 TB drives.
> The 5 TB drives eventually get detected, but do not work reliably.
It took many days of moving things around and trying, and I think I finally
got to something that works.
Unfortuantely, it still boots with errors and resets, but works reliably
after that. This however means that while I was changing things, I missed
which thing I changed and that fixed the problem (since it lookid like it
was still broken).
I had already changed all the sata cables and tried plugging the drives
directly into the PMP, but that didn't help.
I did eventually add a second SATA card, but the new drives weren't even
seen on that card, until I upgraded the bios on it (it was some early 4.x
bios, and 6.x was available). Upgrading the bios on that card allowed the
drives to be seen (I also upgraded the other card from a later 4.x to 6.x
too).
I then upgraded the bios on both PMPs (sil 3726CB). By then, when I tried
the disk array on my almost similar PMP with a 3132 (2 port PCIe) and it
booted and worked flawlessly.
Unfortunately, when I would put it back in my original system with a 3124,
I would get some boot errors, until I let it boot once anyway, and realized
that it did recover from those errors now and worked reasonably fine
afterwards (see the few exception frozen errors below:
ata4.01: exc eption Emask 0x0 SAct 0x4000000 SErr 0x0 action 0x2 frozen
ata4.01: cmd 60/20:d0:1f:27:8b/00:00:6a:00:00/40 tag 26 cdb 0x0 data 16384 in
ata4.04: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x2 frozen
ata4.04: cmd 60/08:38:b7:2d:b3/00:00:6b:00:00/40 tag 7 cdb 0x0 data 4096 in
ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
ata4.00: cmd 60/68:00:d7:d0:ba/00:00:6b:00:00/40 tag 0 cdb 0x0 data 53248 in
ata4.01: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x2 frozen
ata4.01: cmd 60/58:30:3f:ca:f1/00:00:46:00:00/40 tag 6 cdb 0x0 data 45056 in )
Unfortunately, I don't know for sure if it's the card or the PMP bios upgrade
that improved the situation enough to fix it, but either way, it seems to
work now.
I'll attach the boot messages and random recoverable errors below:
> PM: Adding info for No Bus:usbdev2.1
> ata3: SATA link down (SStatus 0 SControl 0)
> ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata4.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9
> ata4.00: hard resetting link
> ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.01: hard resetting link
> ata4.01: softreset failed (timeout)
> ata4.01: hard resetting link
> ata4.01: COMRESET failed (errno=-5)
> ata4.01: reset failed, giving up
> ata4.15: hard resetting link
> ata4.15: softreset failed (timeout)
> ata4.15: hard resetting link
> ata4.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata4.00: hard resetting link
> ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.01: hard resetting link
> ata4.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.02: hard resetting link
> ata4.02: softreset failed (timeout)
> ata4.02: hard resetting link
> ata4.02: COMRESET failed (errno=-5)
> ata4.02: reset failed, giving up
> ata4.15: hard resetting link
> ata4.15: softreset failed (timeout)
> ata4.15: hard resetting link
> ata4.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata4.00: hard resetting link
> ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.01: hard resetting link
> ata4.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.02: hard resetting link
> ata4.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.03: hard resetting link
> ata4.03: softreset failed (timeout)
> ata4.03: hard resetting link
> ata4.03: COMRESET failed (errno=-5)
> ata4.03: reset failed, giving up
> ata4.15: hard resetting link
> ata4.15: softreset failed (timeout)
> ata4.15: hard resetting link
> ata4.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata4.00: hard resetting link
> ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.01: hard resetting link
> ata4.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.02: hard resetting link
> ata4.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.03: hard resetting link
> ata4.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.04: hard resetting link
> ata4.04: softreset failed (timeout)
> ata4.04: hard resetting link
> ata4.04: COMRESET failed (errno=-5)
> ata4.04: reset failed, giving up
> ata4.15: hard resetting link
> ata4.15: softreset failed (timeout)
> ata4.15: hard resetting link
> ata4.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata4.00: hard resetting link
> ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.01: hard resetting link
> ata4.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.02: hard resetting link
> ata4.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.03: hard resetting link
> ata4.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.04: hard resetting link
> ata4.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.05: hard resetting link
> ata4.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata4.00: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32)
> ata4.00: configured for UDMA/100
> ata4.01: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata4.01: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.01: configured for UDMA/100
> ata4.02: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata4.02: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.02: configured for UDMA/100
> ata4.03: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata4.03: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.03: configured for UDMA/100
> ata4.04: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata4.04: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.04: configured for UDMA/100
> ata4: EH complete
> ACPI: PCI Interrupt 0000:02:03.0[A] -> GSI 25 (level, low) -> IRQ 23
(...)
> sata_sil24 0000:02:03.0: Applying completion IRQ loss on PCI-X errata fix
To be honest, those were enough boot errors for me to think that
some weird thing still prevented the disk array from working on the system it's supposed to be in (sil3124, but with everything else the same since I
moved it over from the sil3132 system where it booted fine: same cables,
same PMP, same SATA backplane, same drives).
Turns out however that the system continued to boot, and seems to be working
fine right now, outside of some exception frozen messages that it seems to
recover from:
> disk 1, wo:0, o:1, dev:sdb2
> ata4.04: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x2 frozen
> ata4.04: cmd 60/08:38:b7:2d:b3/00:00:6b:00:00/40 tag 7 cdb 0x0 data 4096 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata4.15: hard resetting link
> ata4.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata4.00: hard resetting link
> ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.01: hard resetting link
> ata4.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.02: hard resetting link
> ata4.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.03: hard resetting link
> ata4.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.04: hard resetting link
> ata4.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.05: hard resetting link
> ata4.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata4.00: configured for UDMA/100
> ata4.01: configured for UDMA/100
> ata4.02: configured for UDMA/100
> ata4.03: configured for UDMA/100
> ata4.04: configured for UDMA/100
> ata4: EH complete
> sd 4:0:0:0: [sdc] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 4:0:0:0: [sdc] Write Protect is off
> sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sd 4:1:0:0: [sdd] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 4:1:0:0: [sdd] Write Protect is off
> sd 4:1:0:0: [sdd] Mode Sense: 00 3a 00 00
> sd 4:1:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sd 4:2:0:0: [sde] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 4:2:0:0: [sde] Write Protect is off
> sd 4:2:0:0: [sde] Mode Sense: 00 3a 00 00
> sd 4:2:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sd 4:3:0:0: [sdf] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 4:3:0:0: [sdf] Write Protect is off
> sd 4:3:0:0: [sdf] Mode Sense: 00 3a 00 00
> sd 4:3:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sd 4:4:0:0: [sdg] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 4:4:0:0: [sdg] Write Protect is off
> sd 4:4:0:0: [sdg] Mode Sense: 00 3a 00 00
> sd 4:4:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sd 4:0:0:0: [sdc] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 4:0:0:0: [sdc] Write Protect is off
> sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sd 4:1:0:0: [sdd] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 4:1:0:0: [sdd] Write Protect is off
> sd 4:1:0:0: [sdd] Mode Sense: 00 3a 00 00
> sd 4:1:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sd 4:2:0:0: [sde] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 4:2:0:0: [sde] Write Protect is off
> sd 4:2:0:0: [sde] Mode Sense: 00 3a 00 00
> sd 4:2:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sd 4:3:0:0: [sdf] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 4:3:0:0: [sdf] Write Protect is off
> sd 4:3:0:0: [sdf] Mode Sense: 00 3a 00 00
> sd 4:3:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> sd 4:4:0:0: [sdg] 1953525168 512-byte hardware sectors (1000205 MB)
> sd 4:4:0:0: [sdg] Write Protect is off
> sd 4:4:0:0: [sdg] Mode Sense: 00 3a 00 00
> sd 4:4:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
> ata4.00: cmd 60/68:00:d7:d0:ba/00:00:6b:00:00/40 tag 0 cdb 0x0 data 53248 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata4.15: hard resetting link
> ata4.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata4.00: hard resetting link
> ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.01: hard resetting link
> ata4.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.02: hard resetting link
> ata4.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.03: hard resetting link
> ata4.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.04: hard resetting link
> ata4.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.05: hard resetting link
> ata4.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata4.00: configured for UDMA/100
> ata4.01: configured for UDMA/100
> ata4.02: configured for UDMA/100
> ata4.03: configured for UDMA/100
> ata4.04: configured for UDMA/100
> ata4: EH complete
This is by far the weirdest/most inconsistent hw problem I've worked on so
far, but I hope this info can help other and the reminder that upgrading
the SATA cards and PMP firmwares can help
Oh, and just to show how this testing has been "fun", the same system
that put out the 30 lines of temp errors and retries above, boots flawlessly
the next time:
> ata3: SATA link down (SStatus 0 SControl 0)
> ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata4.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9
> ata4.00: hard resetting link
> ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.01: hard resetting link
> ata4.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.02: hard resetting link
> ata4.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.03: hard resetting link
> ata4.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.04: hard resetting link
> ata4.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.05: hard resetting link
> ata4.05: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata4.00: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32)
> ata4.00: configured for UDMA/100
> ata4.01: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata4.01: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.01: configured for UDMA/100
> ata4.02: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata4.02: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.02: configured for UDMA/100
> ata4.03: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata4.03: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.03: configured for UDMA/100
> ata4.04: ATA-7: Hitachi HDS721010KLA330, GKAOA70F, max UDMA/133
> ata4.04: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.04: configured for UDMA/100
> ata4: EH complete
It looks like problems only happen on a cold boot (power off/on).
Once it inits/recovers and boots for real, things work fine on the next boot
if I do a warm reboot.
I'd feel better if it looked a bit more reliable on cold boots, but things
seem to work, so I'll put this on some dogy firmware (I'm going to blame
the drives at this point), which just doesn't work too well on the first
cold boot.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: sil24 PMP works with ST3500641AS but not HDS721010KLA330 (mostly solved)
2007-10-07 17:22 ` sil24 PMP works with ST3500641AS but not HDS721010KLA330 (mostly solved) Marc MERLIN
@ 2007-10-08 1:06 ` Tejun Heo
0 siblings, 0 replies; 10+ messages in thread
From: Tejun Heo @ 2007-10-08 1:06 UTC (permalink / raw)
To: Marc MERLIN; +Cc: linux-ide
Marc MERLIN wrote:
> It took many days of moving things around and trying, and I think I finally
> got to something that works.
Great.
>> PM: Adding info for No Bus:usbdev2.1
>> ata3: SATA link down (SStatus 0 SControl 0)
>> ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
>> ata4.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9
>> ata4.00: hard resetting link
>> ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> ata4.01: hard resetting link
>> ata4.01: softreset failed (timeout)
>> ata4.01: hard resetting link
>> ata4.01: COMRESET failed (errno=-5)
>> ata4.01: reset failed, giving up
>> ata4.15: hard resetting link
>> ata4.15: softreset failed (timeout)
>> ata4.15: hard resetting link
>> ata4.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
>> ata4.00: hard resetting link
>> ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> ata4.01: hard resetting link
>> ata4.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> ata4.02: hard resetting link
>> ata4.02: softreset failed (timeout)
>> ata4.02: hard resetting link
>> ata4.02: COMRESET failed (errno=-5)
>> ata4.02: reset failed, giving up
>> ata4.15: hard resetting link
>> ata4.15: softreset failed (timeout)
>> ata4.15: hard resetting link
>> ata4.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
>> ata4.00: hard resetting link
>> ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> ata4.01: hard resetting link
>> ata4.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> ata4.02: hard resetting link
>> ata4.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> ata4.03: hard resetting link
>> ata4.03: softreset failed (timeout)
>> ata4.03: hard resetting link
>> ata4.03: COMRESET failed (errno=-5)
>> ata4.03: reset failed, giving up
This is a known problem. While spinning each drive up, reset fails and
unsure of controller state, libata resets whole controller each time. I
missed it because my array is usually up all the time. I'll look into it.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2007-10-08 1:06 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-02 17:04 sil24 PMP works with ST3500641AS but not HDS721010KLA330 Marc MERLIN
2007-10-02 17:15 ` Marc MERLIN
2007-10-03 2:28 ` Marc MERLIN
2007-10-03 2:32 ` Marc MERLIN
2007-10-03 3:30 ` Tejun Heo
2007-10-03 5:59 ` Marc MERLIN
2007-10-03 6:38 ` Marc MERLIN
2007-10-03 14:08 ` Marc MERLIN
2007-10-07 17:22 ` sil24 PMP works with ST3500641AS but not HDS721010KLA330 (mostly solved) Marc MERLIN
2007-10-08 1:06 ` Tejun Heo
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).