* sata_promise: port is slow to respond, reset failed
@ 2007-09-02 11:12 Peter Favrholdt
2007-10-14 9:21 ` Bug is fixed in 2.6.23.1: " Peter Favrholdt
0 siblings, 1 reply; 5+ messages in thread
From: Peter Favrholdt @ 2007-09-02 11:12 UTC (permalink / raw)
To: linux-ide
Hi,
I'm still experiencing the same "port is slow to respond" problem using
sata_promise in linux-2.6.22.6 with my Promise Technology, Inc. PDC40718
(SATA 300 TX4) (rev 02) and 4 Seagate 500GB ES drives:
Model Number: ST3500630NS
Firmware Revision: 3.AEE
(with 1.5/3.0Gbps jumper removed = 3.0Gbps)
After doing:
dd if=/dev/sda of=/dev/null bs=1M &
dd if=/dev/sdb of=/dev/null bs=1M &
dd if=/dev/sdc of=/dev/null bs=1M &
dd if=/dev/sdd of=/dev/null bs=1M &
it runs fine for a while, then:
[ 810.545909] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x1380000
action 0x2 frozen
[ 810.545923] ata1.00: cmd c8/00:00:00:33:e6/00:00:00:00:00/e1 tag 0
cdb 0x0 data 131072 in
[ 810.545926] res 40/00:28:00:00:00/00:00:00:00:00/40 Emask
0x4 (timeout)
[ 815.913113] ata1: port is slow to respond, please be patient (Status
0xff)
[ 820.590706] ata1: device not ready (errno=-16), forcing hardreset
[ 820.590716] ata1: hard resetting port
[ 826.137780] ata1: port is slow to respond, please be patient (Status
0xff)
[ 830.635488] ata1: COMRESET failed (errno=-16)
[ 830.635497] ata1: hard resetting port
[ 836.182563] ata1: port is slow to respond, please be patient (Status
0xff)
[ 840.680236] ata1: COMRESET failed (errno=-16)
[ 840.680245] ata1: hard resetting port
[ 846.227361] ata1: port is slow to respond, please be patient (Status
0xff)
[ 875.672028] ata1: COMRESET failed (errno=-16)
[ 875.672037] ata1: limiting SATA link speed to 1.5 Gbps
[ 875.672041] ata1: hard resetting port
[ 880.679454] ata1: COMRESET failed (errno=-16)
[ 880.679463] ata1: reset failed, giving up
[ 880.679466] ata1.00: disabled
[ 880.679480] ata1: EH complete
[ 880.679545] sd 0:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
[ 880.679550] end_request: I/O error, dev sda, sector 31863552
[ 880.679555] Buffer I/O error on device sda, logical block 3982944
[ 880.679561] Buffer I/O error on device sda, logical block 3982945
[ 880.679565] Buffer I/O error on device sda, logical block 3982946
[ 880.679569] Buffer I/O error on device sda, logical block 3982947
[ 880.679573] Buffer I/O error on device sda, logical block 3982948
[ 880.679578] Buffer I/O error on device sda, logical block 3982949
[ 880.679582] Buffer I/O error on device sda, logical block 3982950
[ 880.679586] Buffer I/O error on device sda, logical block 3982951
[ 880.679590] Buffer I/O error on device sda, logical block 3982952
[ 880.679594] Buffer I/O error on device sda, logical block 3982953
[ 880.680296] sd 0:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
[ 880.680301] end_request: I/O error, dev sda, sector 31863808
[ 880.680877] sd 0:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
[ 880.680882] end_request: I/O error, dev sda, sector 31863552
[ 880.681383] sd 0:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
[ 880.681388] end_request: I/O error, dev sda, sector 31863552
The "funny" thing is that it runs fine using linux-2.6.21-rc2 with
Mikael Pettersson's "1.5Gbps only" patch.
I have replaced the cables without any change. I'm quite sure this isn't
a hardware problem as I have uptime counting in months without any problems.
Here is the relevant part of dmesg (detecting drives):
[ 27.612125] scsi3 : sata_promise
[ 27.612214] ata1: SATA max UDMA/133 cmd 0xe0814380 ctl 0xe08143b8
bmdma 0x00000000 irq 19
[ 27.612274] ata2: SATA max UDMA/133 cmd 0xe0814280 ctl 0xe08142b8
bmdma 0x00000000 irq 19
[ 27.612334] ata3: SATA max UDMA/133 cmd 0xe0814200 ctl 0xe0814238
bmdma 0x00000000 irq 19
[ 27.612394] ata4: SATA max UDMA/133 cmd 0xe0814300 ctl 0xe0814338
bmdma 0x00000000 irq 19
[ 28.092787] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 28.143577] ata1.00: ATA-7: ST3500630NS, 3.AEE, max UDMA/133
[ 28.143626] ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 28.235153] ata1.00: configured for UDMA/133
[ 28.722457] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 28.770752] ata2.00: ATA-7: ST3500630NS, 3.AEE, max UDMA/133
[ 28.770800] ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 28.854011] ata2.00: configured for UDMA/133
[ 29.342135] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 29.389819] ata3.00: ATA-7: ST3500630NS, 3.AEE, max UDMA/133
[ 29.389867] ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 29.473081] ata3.00: configured for UDMA/133
[ 29.961812] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 30.012878] ata4.00: ATA-7: ST3500630NS, 3.AEE, max UDMA/133
[ 30.012926] ata4.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 30.104452] ata4.00: configured for UDMA/133
[ 30.104580] scsi 0:0:0:0: Direct-Access ATA ST3500630NS
3.AE PQ: 0 ANSI: 5
[ 30.104720] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors
(500108 MB)
[ 30.104780] sd 0:0:0:0: [sda] Write Protect is off
[ 30.104827] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 30.104841] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 30.104936] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors
(500108 MB)
[ 30.104992] sd 0:0:0:0: [sda] Write Protect is off
[ 30.105039] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 30.105051] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 30.105110] sda: unknown partition table
[ 30.123283] sd 0:0:0:0: [sda] Attached SCSI disk
[ 30.123389] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 30.123494] scsi 1:0:0:0: Direct-Access ATA ST3500630NS
3.AE PQ: 0 ANSI: 5
[ 30.123620] sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors
(500108 MB)
[ 30.123676] sd 1:0:0:0: [sdb] Write Protect is off
[ 30.123723] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 30.123735] sd 1:0:0:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 30.123823] sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors
(500108 MB)
[ 30.123878] sd 1:0:0:0: [sdb] Write Protect is off
[ 30.123925] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 30.123938] sd 1:0:0:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 30.123997] sdb: unknown partition table
[ 30.142694] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 30.142796] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 30.142897] scsi 2:0:0:0: Direct-Access ATA ST3500630NS
3.AE PQ: 0 ANSI: 5
[ 30.143025] sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors
(500108 MB)
[ 30.143080] sd 2:0:0:0: [sdc] Write Protect is off
[ 30.143127] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 30.143140] sd 2:0:0:0: [sdc] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 30.143225] sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors
(500108 MB)
[ 30.143279] sd 2:0:0:0: [sdc] Write Protect is off
[ 30.143326] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 30.143339] sd 2:0:0:0: [sdc] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 30.143396] sdc: unknown partition table
[ 30.154054] sd 2:0:0:0: [sdc] Attached SCSI disk
[ 30.154149] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 30.154257] scsi 3:0:0:0: Direct-Access ATA ST3500630NS
3.AE PQ: 0 ANSI: 5
[ 30.154381] sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors
(500108 MB)
[ 30.154437] sd 3:0:0:0: [sdd] Write Protect is off
[ 30.154484] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[ 30.154496] sd 3:0:0:0: [sdd] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 30.154580] sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors
(500108 MB)
[ 30.154635] sd 3:0:0:0: [sdd] Write Protect is off
[ 30.154682] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[ 30.154694] sd 3:0:0:0: [sdd] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 30.154753] sdd: unknown partition table
[ 30.169230] sd 3:0:0:0: [sdd] Attached SCSI disk
[ 30.169329] sd 3:0:0:0: Attached scsi generic sg3 type 0
I'll be happy to try any patches/suggestions.
Best regards,
Peter
^ permalink raw reply [flat|nested] 5+ messages in thread
* Bug is fixed in 2.6.23.1: sata_promise: port is slow to respond, reset failed
2007-09-02 11:12 sata_promise: port is slow to respond, reset failed Peter Favrholdt
@ 2007-10-14 9:21 ` Peter Favrholdt
2007-11-09 23:58 ` Correction " Peter Favrholdt
0 siblings, 1 reply; 5+ messages in thread
From: Peter Favrholdt @ 2007-10-14 9:21 UTC (permalink / raw)
To: linux-ide
Hi,
The problem is solved in 2.6.23.1 regarding the "port slow to respond"
issue.
I'm using sata_promise on Promise Technology, Inc. PDC40718 (SATA 300
TX4) (rev 02) and 4 Seagate 500GB ES drives.
Using 2.6.23.1 it is possible to run
dd if=/dev/sda of=/dev/null bs=1M &
dd if=/dev/sdb of=/dev/null bs=1M &
dd if=/dev/sdc of=/dev/null bs=1M &
dd if=/dev/sdd of=/dev/null bs=1M &
And it just runs perfectly to the end with no hickups :-)
Thank you very much :-)
Best regards,
Peter
Peter Favrholdt wrote:
> Hi,
>
> I'm still experiencing the same "port is slow to respond" problem using
> sata_promise in linux-2.6.22.6 with my Promise Technology, Inc. PDC40718
> (SATA 300 TX4) (rev 02) and 4 Seagate 500GB ES drives:
> Model Number: ST3500630NS
> Firmware Revision: 3.AEE
> (with 1.5/3.0Gbps jumper removed = 3.0Gbps)
>
> After doing:
>
> dd if=/dev/sda of=/dev/null bs=1M &
> dd if=/dev/sdb of=/dev/null bs=1M &
> dd if=/dev/sdc of=/dev/null bs=1M &
> dd if=/dev/sdd of=/dev/null bs=1M &
>
> it runs fine for a while, then:
>
> [ 810.545909] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x1380000
> action 0x2 frozen
> [ 810.545923] ata1.00: cmd c8/00:00:00:33:e6/00:00:00:00:00/e1 tag 0
> cdb 0x0 data 131072 in
> [ 810.545926] res 40/00:28:00:00:00/00:00:00:00:00/40 Emask
> 0x4 (timeout)
> [ 815.913113] ata1: port is slow to respond, please be patient (Status
> 0xff)
> [ 820.590706] ata1: device not ready (errno=-16), forcing hardreset
> [ 820.590716] ata1: hard resetting port
> [ 826.137780] ata1: port is slow to respond, please be patient (Status
> 0xff)
> [ 830.635488] ata1: COMRESET failed (errno=-16)
> [ 830.635497] ata1: hard resetting port
> [ 836.182563] ata1: port is slow to respond, please be patient (Status
> 0xff)
> [ 840.680236] ata1: COMRESET failed (errno=-16)
> [ 840.680245] ata1: hard resetting port
> [ 846.227361] ata1: port is slow to respond, please be patient (Status
> 0xff)
> [ 875.672028] ata1: COMRESET failed (errno=-16)
> [ 875.672037] ata1: limiting SATA link speed to 1.5 Gbps
> [ 875.672041] ata1: hard resetting port
> [ 880.679454] ata1: COMRESET failed (errno=-16)
> [ 880.679463] ata1: reset failed, giving up
> [ 880.679466] ata1.00: disabled
> [ 880.679480] ata1: EH complete
> [ 880.679545] sd 0:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
> [ 880.679550] end_request: I/O error, dev sda, sector 31863552
> [ 880.679555] Buffer I/O error on device sda, logical block 3982944
> [ 880.679561] Buffer I/O error on device sda, logical block 3982945
> [ 880.679565] Buffer I/O error on device sda, logical block 3982946
> [ 880.679569] Buffer I/O error on device sda, logical block 3982947
> [ 880.679573] Buffer I/O error on device sda, logical block 3982948
> [ 880.679578] Buffer I/O error on device sda, logical block 3982949
> [ 880.679582] Buffer I/O error on device sda, logical block 3982950
> [ 880.679586] Buffer I/O error on device sda, logical block 3982951
> [ 880.679590] Buffer I/O error on device sda, logical block 3982952
> [ 880.679594] Buffer I/O error on device sda, logical block 3982953
> [ 880.680296] sd 0:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
> [ 880.680301] end_request: I/O error, dev sda, sector 31863808
> [ 880.680877] sd 0:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
> [ 880.680882] end_request: I/O error, dev sda, sector 31863552
> [ 880.681383] sd 0:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
> [ 880.681388] end_request: I/O error, dev sda, sector 31863552
>
> The "funny" thing is that it runs fine using linux-2.6.21-rc2 with
> Mikael Pettersson's "1.5Gbps only" patch.
>
> I have replaced the cables without any change. I'm quite sure this isn't
> a hardware problem as I have uptime counting in months without any
> problems.
>
> Here is the relevant part of dmesg (detecting drives):
>
> [ 27.612125] scsi3 : sata_promise
> [ 27.612214] ata1: SATA max UDMA/133 cmd 0xe0814380 ctl 0xe08143b8
> bmdma 0x00000000 irq 19
> [ 27.612274] ata2: SATA max UDMA/133 cmd 0xe0814280 ctl 0xe08142b8
> bmdma 0x00000000 irq 19
> [ 27.612334] ata3: SATA max UDMA/133 cmd 0xe0814200 ctl 0xe0814238
> bmdma 0x00000000 irq 19
> [ 27.612394] ata4: SATA max UDMA/133 cmd 0xe0814300 ctl 0xe0814338
> bmdma 0x00000000 irq 19
> [ 28.092787] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 28.143577] ata1.00: ATA-7: ST3500630NS, 3.AEE, max UDMA/133
> [ 28.143626] ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
> [ 28.235153] ata1.00: configured for UDMA/133
> [ 28.722457] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 28.770752] ata2.00: ATA-7: ST3500630NS, 3.AEE, max UDMA/133
> [ 28.770800] ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
> [ 28.854011] ata2.00: configured for UDMA/133
> [ 29.342135] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 29.389819] ata3.00: ATA-7: ST3500630NS, 3.AEE, max UDMA/133
> [ 29.389867] ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
> [ 29.473081] ata3.00: configured for UDMA/133
> [ 29.961812] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 30.012878] ata4.00: ATA-7: ST3500630NS, 3.AEE, max UDMA/133
> [ 30.012926] ata4.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
> [ 30.104452] ata4.00: configured for UDMA/133
> [ 30.104580] scsi 0:0:0:0: Direct-Access ATA ST3500630NS
> 3.AE PQ: 0 ANSI: 5
> [ 30.104720] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors
> (500108 MB)
> [ 30.104780] sd 0:0:0:0: [sda] Write Protect is off
> [ 30.104827] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [ 30.104841] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 30.104936] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors
> (500108 MB)
> [ 30.104992] sd 0:0:0:0: [sda] Write Protect is off
> [ 30.105039] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [ 30.105051] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 30.105110] sda: unknown partition table
> [ 30.123283] sd 0:0:0:0: [sda] Attached SCSI disk
> [ 30.123389] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [ 30.123494] scsi 1:0:0:0: Direct-Access ATA ST3500630NS
> 3.AE PQ: 0 ANSI: 5
> [ 30.123620] sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors
> (500108 MB)
> [ 30.123676] sd 1:0:0:0: [sdb] Write Protect is off
> [ 30.123723] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
> [ 30.123735] sd 1:0:0:0: [sdb] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 30.123823] sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors
> (500108 MB)
> [ 30.123878] sd 1:0:0:0: [sdb] Write Protect is off
> [ 30.123925] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
> [ 30.123938] sd 1:0:0:0: [sdb] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 30.123997] sdb: unknown partition table
> [ 30.142694] sd 1:0:0:0: [sdb] Attached SCSI disk
> [ 30.142796] sd 1:0:0:0: Attached scsi generic sg1 type 0
> [ 30.142897] scsi 2:0:0:0: Direct-Access ATA ST3500630NS
> 3.AE PQ: 0 ANSI: 5
> [ 30.143025] sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors
> (500108 MB)
> [ 30.143080] sd 2:0:0:0: [sdc] Write Protect is off
> [ 30.143127] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> [ 30.143140] sd 2:0:0:0: [sdc] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 30.143225] sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors
> (500108 MB)
> [ 30.143279] sd 2:0:0:0: [sdc] Write Protect is off
> [ 30.143326] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> [ 30.143339] sd 2:0:0:0: [sdc] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 30.143396] sdc: unknown partition table
> [ 30.154054] sd 2:0:0:0: [sdc] Attached SCSI disk
> [ 30.154149] sd 2:0:0:0: Attached scsi generic sg2 type 0
> [ 30.154257] scsi 3:0:0:0: Direct-Access ATA ST3500630NS
> 3.AE PQ: 0 ANSI: 5
> [ 30.154381] sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors
> (500108 MB)
> [ 30.154437] sd 3:0:0:0: [sdd] Write Protect is off
> [ 30.154484] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
> [ 30.154496] sd 3:0:0:0: [sdd] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 30.154580] sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors
> (500108 MB)
> [ 30.154635] sd 3:0:0:0: [sdd] Write Protect is off
> [ 30.154682] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
> [ 30.154694] sd 3:0:0:0: [sdd] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 30.154753] sdd: unknown partition table
> [ 30.169230] sd 3:0:0:0: [sdd] Attached SCSI disk
> [ 30.169329] sd 3:0:0:0: Attached scsi generic sg3 type 0
>
> I'll be happy to try any patches/suggestions.
>
> Best regards,
>
> Peter
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bug is fixed in 2.6.23.1: sata_promise: port is slow to respond, reset failed
@ 2007-10-15 8:21 Mikael Pettersson
2007-10-15 17:55 ` Peter Favrholdt
0 siblings, 1 reply; 5+ messages in thread
From: Mikael Pettersson @ 2007-10-15 8:21 UTC (permalink / raw)
To: linux-ide, linux-ide
On Sun, 14 Oct 2007 11:21:13 +0200, Peter Favrholdt wrote:
> The problem is solved in 2.6.23.1 regarding the "port slow to respond"
> issue.
>
> I'm using sata_promise on Promise Technology, Inc. PDC40718 (SATA 300
> TX4) (rev 02) and 4 Seagate 500GB ES drives.
>
> Using 2.6.23.1 it is possible to run
>
> dd if=/dev/sda of=/dev/null bs=1M &
> dd if=/dev/sdb of=/dev/null bs=1M &
> dd if=/dev/sdc of=/dev/null bs=1M &
> dd if=/dev/sdd of=/dev/null bs=1M &
>
> And it just runs perfectly to the end with no hickups :-)
That's very good to hear.
However, I don't see how the sata_promise changes from 2.6.22 to 2.6.23
can explain this. The only functional changes there are a critical fix
for FastTrack TX4200 (not your card), and support for SATA hotplugging
(not happening here).
So I'm suspecting something in libata core might have changed to fix this.
Just to make sure, what's the numerical PCI IDs for your card?
(No big deal, but I'd like to know what the error was.)
/Mikael
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bug is fixed in 2.6.23.1: sata_promise: port is slow to respond, reset failed
2007-10-15 8:21 Mikael Pettersson
@ 2007-10-15 17:55 ` Peter Favrholdt
0 siblings, 0 replies; 5+ messages in thread
From: Peter Favrholdt @ 2007-10-15 17:55 UTC (permalink / raw)
To: Mikael Pettersson; +Cc: linux-ide
Hi
Mikael Pettersson wrote:
> However, I don't see how the sata_promise changes from 2.6.22 to 2.6.23
> can explain this. The only functional changes there are a critical fix
> for FastTrack TX4200 (not your card), and support for SATA hotplugging
> (not happening here).
>
> So I'm suspecting something in libata core might have changed to fix this.
>
> Just to make sure, what's the numerical PCI IDs for your card?
01:08.0 0180: 105a:3d17 (rev 02)
Subsystem: 105a:3d17
Flags: bus master, 66MHz, medium devsel, latency 72, IRQ 19
I/O ports at a400 [size=128]
I/O ports at a800 [size=256]
Memory at e9024000 (32-bit, non-prefetchable) [size=4K]
Memory at e9000000 (32-bit, non-prefetchable) [size=128K]
[virtual] Expansion ROM at 300a0000 [disabled] [size=32K]
Capabilities: [60] Power Management version 2
Best regards,
Peter
^ permalink raw reply [flat|nested] 5+ messages in thread
* Correction Re: Bug is fixed in 2.6.23.1: sata_promise: port is slow to respond, reset failed
2007-10-14 9:21 ` Bug is fixed in 2.6.23.1: " Peter Favrholdt
@ 2007-11-09 23:58 ` Peter Favrholdt
0 siblings, 0 replies; 5+ messages in thread
From: Peter Favrholdt @ 2007-11-09 23:58 UTC (permalink / raw)
To: linux-ide
Hi,
I previously wrote this issue was fixed by upgrading to 2.6.23.1
There were some mails on this list regarding a workaround for an Asic
bug and of course I'm looking forward to trying it :-)
Anyway here goes for completeness:
* 2.6.23.1 completed dd-stress tests as described earlier (these same
tests would always make 2.6.22.9 fail before completing even a single run)
* after 21 days and 8 hours normal operation, one sata channel froze
while doing checkarray with the following dmesg output (only md/sata
stuff - rest deleted):
01:06:02 kernel: [1843824.893109] md: data-check of RAID array md0
01:06:02 kernel: [1843824.893117] md: minimum _guaranteed_ speed: 1000
KB/sec/disk.
01:06:02 kernel: [1843824.893121] md: using maximum available idle IO
bandwidth (but not more than 200000 KB/sec) for data-check.
01:06:02 kernel: [1843824.893126] md: using 128k window, over a total of
488386496 blocks.
01:06:02 mdadm: RebuildStarted event detected on md device /dev/md0
01:15:30 kernel: [1844393.053517] ata1.00: exception Emask 0x0 SAct 0x0
SErr 0x1380000 action 0x2 frozen
01:15:30 kernel: [1844393.053533] ata1.00: cmd
25/00:00:00:1e:e6/00:04:01:00:00/e0 tag 0 cdb 0x0 data 524288 in
01:15:30 kernel: [1844393.053535] res
40/00:28:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
01:15:35 kernel: [1844398.420543] ata1: port is slow to respond, please
be patient (Status 0xff)
01:15:40 kernel: [1844403.098409] ata1: device not ready (errno=-16),
forcing hardreset
01:15:40 kernel: [1844403.098420] ata1: hard resetting port
01:15:46 kernel: [1844408.645861] ata1: port is slow to respond, please
be patient (Status 0xff)
01:15:50 kernel: [1844413.144653] ata1: COMRESET failed (errno=-16)
01:15:50 kernel: [1844413.144663] ata1: hard resetting port
01:15:56 kernel: [1844418.691270] ata1: port is slow to respond, please
be patient (Status 0xff)
01:16:00 kernel: [1844423.189228] ata1: COMRESET failed (errno=-16)
01:16:00 kernel: [1844423.189237] ata1: hard resetting port
01:16:06 kernel: [1844428.736687] ata1: port is slow to respond, please
be patient (Status 0xff)
01:16:35 kernel: [1844458.193217] ata1: COMRESET failed (errno=-16)
01:16:35 kernel: [1844458.193228] ata1: limiting SATA link speed to 1.5 Gbps
01:16:35 kernel: [1844458.193231] ata1: hard resetting port
01:16:40 kernel: [1844463.201458] ata1: COMRESET failed (errno=-16)
01:16:40 kernel: [1844463.201468] ata1: reset failed, giving up
01:16:40 kernel: [1844463.201472] ata1.00: disabled
01:16:40 kernel: [1844463.201483] ata1: EH pending after completion,
repeating EH (cnt=4)
01:16:40 kernel: [1844463.201491] ata1: exception Emask 0x10 SAct 0x0
SErr 0x1390002 action 0x2 frozen
01:16:40 kernel: [1844463.201495] ata1: hotplug_status 0x80
01:16:40 kernel: [1844463.201506] ata1: hard resetting port
01:16:46 kernel: [1844469.148300] ata1: port is slow to respond, please
be patient (Status 0xff)
01:16:50 kernel: [1844473.226345] ata1: COMRESET failed (errno=-16)
01:16:50 kernel: [1844473.226355] ata1: hard resetting port
01:16:56 kernel: [1844479.173709] ata1: port is slow to respond, please
be patient (Status 0xff)
01:17:00 kernel: [1844483.252279] ata1: COMRESET failed (errno=-16)
01:17:00 kernel: [1844483.252289] ata1: hard resetting port
01:17:06 kernel: [1844489.199287] ata1: port is slow to respond, please
be patient (Status 0xff)
01:17:35 kernel: [1844518.245767] ata1: COMRESET failed (errno=-16)
01:17:35 kernel: [1844518.245778] ata1: limiting SATA link speed to 1.5 Gbps
01:17:35 kernel: [1844518.245782] ata1: hard resetting port
01:17:40 kernel: [1844523.293460] ata1: COMRESET failed (errno=-16)
01:17:40 kernel: [1844523.293469] ata1: reset failed, giving up
01:17:40 kernel: [1844523.293476] ata1: EH pending after completion,
repeating EH (cnt=3)
01:17:40 kernel: [1844523.293485] ata1: exception Emask 0x10 SAct 0x0
SErr 0x1390002 action 0x2 frozen
01:17:40 kernel: [1844523.293488] ata1: hotplug_status 0x80
01:17:40 kernel: [1844523.293500] ata1: hard resetting port
01:17:46 kernel: [1844529.240746] ata1: port is slow to respond, please
be patient (Status 0xff)
01:17:50 kernel: [1844533.319339] ata1: COMRESET failed (errno=-16)
01:17:50 kernel: [1844533.319349] ata1: hard resetting port
01:17:56 kernel: [1844539.266172] ata1: port is slow to respond, please
be patient (Status 0xff)
01:18:00 kernel: [1844543.344817] ata1: COMRESET failed (errno=-16)
01:18:00 kernel: [1844543.344827] ata1: hard resetting port
01:18:06 kernel: [1844549.291715] ata1: port is slow to respond, please
be patient (Status 0xff)
01:18:35 kernel: [1844578.338834] ata1: COMRESET failed (errno=-16)
01:18:35 kernel: [1844578.338846] ata1: limiting SATA link speed to 1.5 Gbps
01:18:35 kernel: [1844578.338849] ata1: hard resetting port
01:18:41 kernel: [1844583.385996] ata1: COMRESET failed (errno=-16)
01:18:41 kernel: [1844583.386006] ata1: reset failed, giving up
01:18:41 kernel: [1844583.386012] ata1: EH pending after completion,
repeating EH (cnt=2)
01:18:41 kernel: [1844583.386021] ata1: exception Emask 0x10 SAct 0x0
SErr 0x1390002 action 0x2 frozen
01:18:41 kernel: [1844583.386024] ata1: hotplug_status 0x80
01:18:41 kernel: [1844583.386036] ata1: hard resetting port
01:18:46 kernel: [1844589.333287] ata1: port is slow to respond, please
be patient (Status 0xff)
01:18:51 kernel: [1844593.411414] ata1: COMRESET failed (errno=-16)
01:18:51 kernel: [1844593.411424] ata1: hard resetting port
01:18:56 kernel: [1844599.358702] ata1: port is slow to respond, please
be patient (Status 0xff)
01:19:01 kernel: [1844603.436851] ata1: COMRESET failed (errno=-16)
01:19:01 kernel: [1844603.436862] ata1: hard resetting port
01:19:07 kernel: [1844609.384125] ata1: port is slow to respond, please
be patient (Status 0xff)
01:19:36 kernel: [1844638.430836] ata1: COMRESET failed (errno=-16)
01:19:36 kernel: [1844638.430848] ata1: limiting SATA link speed to 1.5 Gbps
01:19:36 kernel: [1844638.430851] ata1: hard resetting port
01:20:41 kernel: [1844703.571175] ata1: COMRESET failed (errno=-16)
01:20:41 kernel: [1844703.571185] ata1: reset failed, giving up
01:20:41 kernel: [1844703.571192] ata1: EH pending after 5 tries, giving up
01:20:41 kernel: [1844703.571245] sd 0:0:0:0: [sda] Result:
hostbyte=0x00 driverbyte=0x08
01:20:41 kernel: [1844703.571249] sd 0:0:0:0: [sda] Sense Key : 0xb
[current] [descriptor]
01:20:41 kernel: [1844703.571255] Descriptor sense data with sense
descriptors (in hex):
01:20:41 kernel: [1844703.571258] 72 0b 00 00 00 00 00 0c 00 0a
80 00 00 00 00 00
01:20:41 kernel: [1844703.571265] 00 00 00 00
01:20:41 kernel: [1844703.571268] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
01:20:41 kernel: [1844703.571271] end_request: I/O error, dev sda,
sector 31858176
01:20:41 kernel: [1844703.571343] sd 0:0:0:0: rejecting I/O to offline
device
01:20:41 kernel: [1844703.571349] sd 0:0:0:0: rejecting I/O to offline
device
01:20:41 kernel: [1844703.571413] ata1: EH complete
01:20:41 kernel: [1844703.572352] sd 0:0:0:0: [sda] Result:
hostbyte=0x01 driverbyte=0x00
01:20:41 kernel: [1844703.572358] end_request: I/O error, dev sda,
sector 31859200
01:20:41 kernel: [1844703.572375] sd 0:0:0:0: rejecting I/O to offline
device
01:20:41 kernel: [1844703.572378] sd 0:0:0:0: rejecting I/O to offline
device
01:20:41 kernel: [1844703.572381] sd 0:0:0:0: rejecting I/O to offline
device
01:20:41 kernel: [1844703.572387] md: super_written gets error=-5,
uptodate=0
01:20:41 kernel: [1844703.572390] raid5: Disk failure on sda, disabling
device. Operation continuing on 3 devices
01:20:41 kernel: [1844703.572827] ata1.00: detaching (SCSI 0:0:0:0)
01:20:41 kernel: [1844703.573155] sd 0:0:0:0: [sda] Synchronizing SCSI cache
01:20:41 kernel: [1844703.573347] sd 0:0:0:0: [sda] Result:
hostbyte=0x04 driverbyte=0x00
01:20:41 kernel: [1844703.573353] sd 0:0:0:0: [sda] Stopping disk
01:20:41 kernel: [1844703.573519] sd 0:0:0:0: [sda] START_STOP FAILED
01:20:41 kernel: [1844703.573522] sd 0:0:0:0: [sda] Result:
hostbyte=0x04 driverbyte=0x00
01:20:48 kernel: [1844711.027697] md: md0: data-check done.
01:20:48 kernel: [1844711.128915] RAID5 conf printout:
01:20:48 kernel: [1844711.128924] --- rd:4 wd:3
01:20:48 kernel: [1844711.128927] disk 0, o:0, dev:sda
01:20:48 kernel: [1844711.128930] disk 1, o:1, dev:sdd
01:20:48 kernel: [1844711.128933] disk 2, o:1, dev:sdc
01:20:48 kernel: [1844711.128935] disk 3, o:1, dev:sdb
01:20:48 kernel: [1844711.157764] RAID5 conf printout:
01:20:48 kernel: [1844711.157774] --- rd:4 wd:3
01:20:48 kernel: [1844711.157778] disk 1, o:1, dev:sdd
01:20:48 kernel: [1844711.157782] disk 2, o:1, dev:sdc
01:20:48 kernel: [1844711.157784] disk 3, o:1, dev:sdb
01:20:49 mdadm: Fail event detected on md device /dev/md0, component
device /dev/sda
01:20:49 mdadm: RebuildFinished event detected on md device /dev/md0
Best regards,
Peter
Peter Favrholdt wrote:
> The problem is solved in 2.6.23.1 regarding the "port slow to respond"
> issue.
>
> I'm using sata_promise on Promise Technology, Inc. PDC40718 (SATA 300
> TX4) (rev 02) and 4 Seagate 500GB ES drives.
>
> Using 2.6.23.1 it is possible to run
>
> dd if=/dev/sda of=/dev/null bs=1M &
> dd if=/dev/sdb of=/dev/null bs=1M &
> dd if=/dev/sdc of=/dev/null bs=1M &
> dd if=/dev/sdd of=/dev/null bs=1M &
>
> And it just runs perfectly to the end with no hickups :-)
>
> Thank you very much :-)
>
> Best regards,
>
> Peter
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2007-11-09 23:58 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-09-02 11:12 sata_promise: port is slow to respond, reset failed Peter Favrholdt
2007-10-14 9:21 ` Bug is fixed in 2.6.23.1: " Peter Favrholdt
2007-11-09 23:58 ` Correction " Peter Favrholdt
-- strict thread matches above, loose matches on Subject: below --
2007-10-15 8:21 Mikael Pettersson
2007-10-15 17:55 ` Peter Favrholdt
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).