From: Peter Favrholdt <linux-ide@how.dk>
To: linux-ide@vger.kernel.org
Subject: sata_promise: port is slow to respond, reset failed
Date: Sun, 02 Sep 2007 13:12:42 +0200 [thread overview]
Message-ID: <46DA9AAA.3070808@how.dk> (raw)
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
next reply other threads:[~2007-09-02 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 11:12 Peter Favrholdt [this message]
2007-10-14 9:21 ` Bug is fixed in 2.6.23.1: sata_promise: port is slow to respond, reset failed Peter Favrholdt
2007-11-09 23:58 ` Correction " Peter Favrholdt
-- strict thread matches above, loose matches on Subject: below --
2007-09-02 15:11 Mikael Pettersson
2007-09-02 17:02 Mikael Pettersson
2007-09-02 23:04 ` Peter Favrholdt
2007-09-03 8:11 Mikael Pettersson
2007-09-03 11:59 ` Tomi Orava
2007-09-03 20:38 ` Peter Favrholdt
2007-09-04 8:14 ` Mikael Pettersson
2007-09-04 17:20 ` Peter Favrholdt
2007-09-04 18:47 ` Mikael Pettersson
2007-09-04 16:37 ` Chuck Ebbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46DA9AAA.3070808@how.dk \
--to=linux-ide@how.dk \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is 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).