[Bugme-new] [Bug 9261] New: hpt37x limited to UDMA/33 due to 40-wire cable

[bugme-daemon at bugzilla.kernel.org]

http://bugzilla.kernel.org/show_bug.cgi?id=9261

           Summary: hpt37x limited to UDMA/33 due to 40-wire cable
           Product: IO/Storage
           Version: 2.5
     KernelVersion: 2.6.23
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Serial ATA
        AssignedTo: jgarzik at pobox.com
        ReportedBy: lkmlist at gmail.com


Most recent kernel where this bug did not occur: -/-

Distribution:
Gentoo

Hardware Environment:

Software Environment:
System uname: 2.6.23 i686 Intel(R) Celeron(R) CPU 2.66GHz
Timestamp of tree: Sun, 28 Oct 2007 21:50:01 +0000
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632)
[disabled]
ccache version 2.4 [enabled]
app-shells/bash:     3.2_p17
dev-lang/python:     2.4.4-r6
dev-python/pycrypto: 2.0.1-r6
dev-util/ccache:     2.4-r7
sys-apps/baselayout: 1.12.9-r2
sys-apps/sandbox:    1.2.18.1-r2
sys-devel/autoconf:  2.13, 2.61-r1
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.18-r1
sys-devel/gcc-config: 1.3.16
sys-devel/libtool:   1.5.24
virtual/os-headers:  2.6.22-r2
ACCEPT_KEYWORDS="x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=pentium4 -O2 -pipe -msse2 -mfpmath=sse -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"

Problem Description:

First of all: Does it look like a hardware defekt on the controller or is it a
bug? If you tent to say its a HW defekt, please let me know and close this bug.

When I connect a HDD to a certain port (Interface 3) of the Highpoint
RockedRaid 454 the kernel shows the following:

ata5.00: ATA-7: Maxtor 5A250J0, RAM51VV0, max UDMA/133
ata5.00: 490234752 sectors, multi 16: LBA48 
ata5.01: ATA-7: HDT722525DLAT80, V44OA96A, max UDMA/133
ata5.01: 488397168 sectors, multi 16: LBA48 
ata5.00: limited to UDMA/33 due to 40-wire cable
ata5.01: limited to UDMA/33 due to 40-wire cable
Find mode for 12 reports A81F442
Find mode for 12 reports A81F442
Find mode for DMA 66 reports 120C8242
Find mode for DMA 66 reports 120C8242
ata5.00: configured for UDMA/33
ata5.01: failed to IDENTIFY (I/O error, err_mask=0x2)
ata5.01: revalidation failed (errno=-5)
ata5: failed to recover some devices, retrying in 5 secs
ata5.01: failed to IDENTIFY (I/O error, err_mask=0x2)
ata5.01: revalidation failed (errno=-5)
ata5.01: limiting speed to UDMA/33:PIO3
ata5: failed to recover some devices, retrying in 5 secs
ata5.01: failed to IDENTIFY (I/O error, err_mask=0x2)
ata5.01: revalidation failed (errno=-5)
ata5.01: disabled
ata5: failed to recover some devices, retrying in 5 secs
ata5.00: failed to IDENTIFY (I/O error, err_mask=0x40)
ata5.00: revalidation failed (errno=-5)
ata5: failed to recover some devices, retrying in 5 secs
Find mode for 12 reports A81F442
Find mode for DMA 66 reports 120C8242
ata5.00: configured for UDMA/33
ata5: EH pending after completion, repeating EH (cnt=4)


Connecting the cable to another port (interface 4) works fine:

ata6: PATA max UDMA/100 cmd 0x0001a400 ctl 0x0001a002 bmdma 0x00019808 irq 19
ata6.00: ATA-7: Maxtor 5A250J0, RAM51VV0, max UDMA/133
ata6.00: 490234752 sectors, multi 16: LBA48 
ata6.01: ATA-7: HDT722525DLAT80, V44OA96A, max UDMA/133
ata6.01: 488397168 sectors, multi 16: LBA48 
Find mode for 12 reports A81F442
Find mode for 12 reports A81F442
Find mode for DMA 69 reports 12848242
Find mode for DMA 69 reports 12848242
ata6.00: configured for UDMA/100
ata6.01: configured for UDMA/100

All other ports (1, 2, 4) are working fine, only port 3 is buggy...

Steps to reproduce:
Connect UDM100 capable cable to interface 3 of the controller and boot.
Reproducable: Alway (with one or with both disks)

Full dmsg here:
http://olausson.name/temp/HPT374_failed
http://olausson.name/temp/HPT374_worked

Thanks and regards
Bjoern


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.