I suspect they meant fall back on seeing the ABRT/ICRC error combination 
- which it does, eventually. Falling back on one occurrence would be too 
aggressive, though, as they can happen once in a blue moon, so there's 
little reason to slow down a working setup forever because of it..
--

Hi, sorry for the delay. I gave it it shot instead of using libata.dma=0:

Linux version 2.6.24.5-default (root@nfssrv) (gcc version 4.1.2 (Gentoo 4.1.2 p1.1)) #1 SMP Thu May 1 13:45:06 Local time zone must be set--see zic m
Command line: root=/dev/sde1 libata.dma=3 udev
...
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:03:00.0 to 64
scsi6 : pata_marvell
scsi7 : pata_marvell
ata7: PATA max UDMA/100 cmd 0xcc00 ctl 0xc880 bmdma 0xc400 irq 16
ata8: PATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc408 irq 16
BAR5:00:02 01:7F 02:22 03:CA 04:00 05:00 06:00 07:00 08:00 09:00 0A:00 0B:00 0C:07 0D:00 0E:00 0F:00 
ata7.00: ATA-0: Delock 54111 512MB, Ver1.27, max UDMA/33
ata7.00: 1006992 sectors, multi 0: LBA 
ata7.01: ATAPI: ATAPI   DVD D  DH16D2P, HP57, max UDMA/33
ata7.00: configured for UDMA/33
ata7.01: configured for UDMA/33
ata7.00: configured for UDMA/33
ata7.01: configured for UDMA/33
ata7: EH complete
BAR5:00:02 01:7F 02:22 03:CA 04:00 05:00 06:00 07:00 08:00 09:00 0A:00 0B:00 0C:07 0D:00 0E:00 0F:00 
scsi 6:0:0:0: Direct-Access     ATA      Delock 54111 512 Ver1 PQ: 0 ANSI: 5
sd 6:0:0:0: [sde] 1006992 512-byte hardware sectors (516 MB)
sd 6:0:0:0: [sde] Write Protect is off
sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 6:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sd 6:0:0:0: [sde] 1006992 512-byte hardware sectors (516 MB)
sd 6:0:0:0: [sde] Write Protect is off
sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 6:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
 sde: sde1
sd 6:0:0:0: [sde] Attached SCSI disk
sd 6:0:0:0: Attached scsi generic sg4 type 0
scsi 6:0:1:0: CD-ROM            ATAPI    DVD D  DH16D2P   HP57 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 6:0:1:0: Attached scsi CD-ROM sr0
sr 6:0:1:0: Attached scsi generic sg5 type 5
...
ata7.00: exception Emask 0x0 S...
[ message continues ]

For some reason your CF card seems to think it is an ATA device not a CFA
device. What does the identify data for it look like (hdparm -I)


Alan
--

# hdparm -I /dev/sde

/dev/sde:

ATA device, with non-removable media
        Model Number:       Delock 54111 512MB                      
        Serial Number:      
        Firmware Revision:  Ver1.27 
Standards:
        Likely used: 4
Configuration:
        Logical         max     current
        cylinders       999     999
        heads           16      16
        sectors/track   63      63
        --
        bytes/track: 32256      bytes/sector: 512
        CHS current addressable sectors:    1006992
        LBA    user addressable sectors:    1006992
        device size with M = 1024*1024:         491 MBytes
        device size with M = 1000*1000:         515 MBytes 
Capabilities:
        LBA, IORDY(may be)(cannot be disabled)
        Buffer size: 1.0kB      bytes avail on r/w long: 4
        Standby timer values: spec'd by Vendor
        R/W multiple sector transfer: Max = 1   Current = 0
        DMA: mdma0 mdma1 mdma2 udma0 *udma1 udma2 
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4 
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Security: 
                supported
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
                supported: enhanced erase
#
--

Does seem to think its ATA not CFA I guess you'll need to specify pio for
that device specifically.

Alan
--

Sorry for my ignorance ... How?
--

On Tue, 06 May 2008 18:24:39 +0200

On a current kernel (Tejun only recently added this)

libata.force= ...

see Documentation/kernel-parameters.txt
--

Good, but as I have said, I am using 2.6.24.5 or below. According
to Google the patch was included in 2.6.25-rc3 so I am out of luck.

My original post:
http://www.gossamer-threads.com/lists/linux/kernel/914136?page=last

<quote>
I tried 'libata.force=7.00:pio4' but it did not help.
</quote>


And, nobody has so far asnwered my post with
Subject: 2.6.25: pata_marvell/ahci/libata regression: ata7: SATA link down (SStatus 0 SControl 300)

Basically, I cannot boot with 2.6.25. So I am stuck. Please
push the libata.force patch into 2.6.24 tree
(http://www.mail-archive.com/linux-ide@vger.kernel.org/msg15454.html).
Currently I can only use libata.dma=0.

--

I have absolutely no idea about the AHCI link down case although some

Correct.

Alan
--