Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux: Kernel

2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }'

 

 

Linux kernel RSS feed   Index | Next | Previous | View Threaded


mmokrejs at ribosome

May 1, 2008, 10:28 AM

Post #1 of 14 (4277 views)
Permalink
2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }'

Hi,
the pata_marvell drivers attempts to use UDMA mode to provide
access to my CompactFlash device attached to its IDE port.
I have MSI P35Neo2 motherboard with Marvell 88SE6111 chip providing
2 IDE ports and Intel ICH9R chip providing 6 SATA ports
(IDE/RAID/AHCI modes). During POST, Marvel controller reports
the CF disk is in UDMA-2 mode (and I cannot change it).
Linux kernel 2.6.24.5 reports during boot:

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


Unfortunately, the disk in a while gives:

ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata7.00: BMDMA stat 0x64
ata7.00: cmd ca/00:02:41:00:00/00:00:00:00:00/e0 tag 0 dma 1024 out
res 51/84:00:41:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY ERR }
ata7.00: error: { ICRC ABRT }
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: soft resetting link
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
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
ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata7.00: BMDMA stat 0x64
ata7.00: cmd ca/00:02:51:b4:07/00:00:00:00:00/e0 tag 0 dma 1024 out
res 51/84:00:51:b4:07/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY ERR }
ata7.00: error: { ICRC ABRT }
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: soft resetting link
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
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
ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata7.00: BMDMA stat 0x64
ata7.00: cmd ca/00:02:13:35:03/00:00:00:00:00/e0 tag 0 dma 1024 out
res 51/84:00:13:35:03/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY ERR }
ata7.00: error: { ICRC ABRT }
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: soft resetting link
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
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
ata7.00: limiting speed to UDMA/25:PIO4
ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata7.00: BMDMA stat 0x64
ata7.00: cmd ca/00:02:69:80:0a/00:00:00:00:00/e0 tag 0 dma 1024 out
res 51/84:00:69:80:0a/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY ERR }
ata7.00: error: { ICRC ABRT }
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: soft resetting link
ata7.00: configured for UDMA/25
ata7.01: configured for UDMA/33
ata7.00: configured for UDMA/25
ata7.01: configured for UDMA/33
ata7: EH complete
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




To get rid of the errors, I can use libata.dma=0 kernel
command-line parameter. Unfortunately, this sets all libata
devices to PIO4 mode. How can I set just this one? I tried
'libata.force=7.00:pio4' but it did not help.

'libata.force=1.00:pio4' does not set it immediately into PIO4
but at least leaves the SATA drives in UDMA mode and after
resets of the CompactFlash IDE disk it gets from UDMA/33 or 25
to PIO4.

Where are the flags documented? linux/Documentation/ directory
contains almost nothing about pata_marvell. :(



00:1f.2 SATA controller: Intel Corporation 6 port SATA AHCI Controller (rev 02) (prog-if 01 [AHCI 1.0])
Subsystem: Micro-Star International Co., Ltd. Unknown device 7345
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 378
I/O ports at b000 [size=8]
I/O ports at ac00 [size=4]
I/O ports at a880 [size=8]
I/O ports at a800 [size=4]
I/O ports at a480 [size=32]
Memory at fbfff000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/4 Enable+
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA <?>
Capabilities: [b0] Vendor Specific Information <?>
Kernel driver in use: ahci

03:00.0 IDE interface: Marvell Technology Group Ltd. Unknown device 6121 (rev b1) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Marvell Technology Group Ltd. Unknown device 6121
Flags: bus master, fast devsel, latency 0, IRQ 16
I/O ports at cc00 [size=8]
I/O ports at c880 [size=4]
I/O ports at c800 [size=8]
I/O ports at c480 [size=4]
I/O ports at c400 [size=16]
Memory at fe9ffc00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [e0] Express Legacy Endpoint, MSI 00
Kernel driver in use: pata_marvell



BTW: Using the generic IDE drivers and forcing 'ide-all-generic=1'
in the kernel command-line makes the CompactFlash and DVD-ROM get
recognized as hda and hdb but I used to see similar drive errors.
Actually, these were even worse because I could not finish mkfs.ext3
for example.
Attachments: dmesg-2.6.24.5-default-nodma (26.2 KB)
  dmesg-2.6.24.5-default-pio4 (38.2 KB)


alan at lxorguk

May 1, 2008, 12:08 PM

Post #2 of 14 (4206 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

> To get rid of the errors, I can use libata.dma=0 kernel
> command-line parameter. Unfortunately, this sets all libata
> devices to PIO4 mode. How can I set just this one? I tried
> 'libata.force=7.00:pio4' but it did not help.

libata.dma=3 will stop DMA being used for CF devices (except those that
decide to pretend to be ATA classes). This one comes up a lot as many CF
adapters are simply not adequate for UDMA.

> Where are the flags documented? linux/Documentation/ directory
> contains almost nothing about pata_marvell. :(

The flags are all common across drivers.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


mmokrejs at ribosome

May 1, 2008, 2:24 PM

Post #3 of 14 (4195 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

Hi Alan,

Alan Cox wrote:
>> To get rid of the errors, I can use libata.dma=0 kernel
>> command-line parameter. Unfortunately, this sets all libata
>> devices to PIO4 mode. How can I set just this one? I tried
>> 'libata.force=7.00:pio4' but it did not help.
>
> libata.dma=3 will stop DMA being used for CF devices (except those that
> decide to pretend to be ATA classes). This one comes up a lot as many CF
> adapters are simply not adequate for UDMA.
>
>> Where are the flags documented? linux/Documentation/ directory
>> contains almost nothing about pata_marvell. :(
>
> The flags are all common across drivers.

Oh, please tell me where can I read more. ;-) What does the number
3 mean? How can I force certain parameters over ata7.00 device only?

Thanks!
Maritn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


jengelh at medozas

May 1, 2008, 4:51 PM

Post #4 of 14 (4180 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

On Thursday 2008-05-01 21:08, Alan Cox wrote:

>> To get rid of the errors, I can use libata.dma=0 kernel
>> command-line parameter. Unfortunately, this sets all libata
>> devices to PIO4 mode. How can I set just this one? I tried
>> 'libata.force=7.00:pio4' but it did not help.
>
>libata.dma=3 will stop DMA being used for CF devices (except those that
>decide to pretend to be ATA classes). This one comes up a lot as many CF
>adapters are simply not adequate for UDMA.

Perhaps the kernel could do this automatically once it sees the
status code?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


alan at lxorguk

May 2, 2008, 2:57 AM

Post #5 of 14 (4185 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

> >libata.dma=3 will stop DMA being used for CF devices (except those that
> >decide to pretend to be ATA classes). This one comes up a lot as many CF
> >adapters are simply not adequate for UDMA.
>
> Perhaps the kernel could do this automatically once it sees the
> status code?

We then hurt all the people with perfectly good working UDMA CF devices.
The kernel will eventually fall back from UDMA to PIO but it favours
working hardware by default.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


hancockr at shaw

May 2, 2008, 7:42 PM

Post #6 of 14 (4247 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

Alan Cox wrote:
>>> libata.dma=3 will stop DMA being used for CF devices (except those that
>>> decide to pretend to be ATA classes). This one comes up a lot as many CF
>>> adapters are simply not adequate for UDMA.
>> Perhaps the kernel could do this automatically once it sees the
>> status code?
>
> We then hurt all the people with perfectly good working UDMA CF devices.
> The kernel will eventually fall back from UDMA to PIO but it favours
> working hardware by default.

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..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


mmokrejs at ribosome

May 6, 2008, 5:44 AM

Post #7 of 14 (4174 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

Robert Hancock wrote:
> Alan Cox wrote:
>>>> libata.dma=3 will stop DMA being used for CF devices (except those that
>>>> decide to pretend to be ATA classes). This one comes up a lot as
>>>> many CF
>>>> adapters are simply not adequate for UDMA.
>>> Perhaps the kernel could do this automatically once it sees the
>>> status code?
>>
>> We then hurt all the people with perfectly good working UDMA CF devices.
>> The kernel will eventually fall back from UDMA to PIO but it favours
>> working hardware by default.
>
> 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 [at] nfssr) (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 SAct 0x0 SErr 0x0 action 0x2
ata7.00: BMDMA stat 0x64
ata7.00: cmd ca/00:02:5f:40:0a/00:00:00:00:00/e0 tag 0 dma 1024 out
res 51/84:00:5f:40:0a/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY ERR }
ata7.00: error: { ICRC ABRT }
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: soft resetting link
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
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
ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata7.00: BMDMA stat 0x64
ata7.00: cmd ca/00:04:63:3f:04/00:00:00:00:00/e0 tag 0 dma 2048 out
res 51/84:00:63:3f:04/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY ERR }
ata7.00: error: { ICRC ABRT }
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: soft resetting link
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
ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata7.00: BMDMA stat 0x64
ata7.00: cmd ca/00:04:63:3f:04/00:00:00:00:00/e0 tag 0 dma 2048 out
res 51/84:00:63:3f:04/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY ERR }
ata7.00: error: { ICRC ABRT }
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: soft resetting link
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
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
ata7.00: limiting speed to UDMA/25:PIO4
ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata7.00: BMDMA stat 0x64
ata7.00: cmd ca/00:0e:71:00:04/00:00:00:00:00/e0 tag 0 dma 7168 out
res 51/84:00:71:00:04/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY ERR }
ata7.00: error: { ICRC ABRT }
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: soft resetting link
ata7.00: configured for UDMA/25
ata7.01: configured for UDMA/33
ata7.00: configured for UDMA/25
ata7.01: configured for UDMA/33
ata7: EH complete
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
ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata7.00: BMDMA stat 0x64
ata7.00: cmd ca/00:02:47:80:07/00:00:00:00:00/e0 tag 0 dma 1024 out
res 51/84:00:47:80:07/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY ERR }
ata7.00: error: { ICRC ABRT }
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: soft resetting link
ata7.00: configured for UDMA/25
ata7.01: configured for UDMA/33
ata7.00: configured for UDMA/25
ata7.01: configured for UDMA/33
ata7: EH complete
sd 6:0:0:0: [sde] 1006992 512-byte hardware sectors (516 MB)
ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata7.00: BMDMA stat 0x64
ata7.00: cmd ca/00:02:41:80:08/00:00:00:00:00/e0 tag 0 dma 1024 out
res 51/84:00:41:80:08/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY ERR }
ata7.00: error: { ICRC ABRT }
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: soft resetting link
ata7.00: configured for UDMA/25
ata7.01: configured for UDMA/33
ata7.00: configured for UDMA/25
ata7.01: configured for UDMA/33
ata7: EH complete
ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata7.00: BMDMA stat 0x64
ata7.00: cmd ca/00:02:41:80:08/00:00:00:00:00/e0 tag 0 dma 1024 out
res 51/84:00:41:80:08/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY ERR }
ata7.00: error: { ICRC ABRT }
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: soft resetting link
ata7.00: configured for UDMA/25
ata7.01: configured for UDMA/33
ata7.00: configured for UDMA/25
ata7.01: configured for UDMA/33
ata7: EH complete
sd 6:0:0:0: [sde] Write Protect is off
sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata7.00: BMDMA stat 0x64
ata7.00: cmd ca/00:04:47:c2:01/00:00:00:00:00/e0 tag 0 dma 2048 out
res 51/84:00:47:c2:01/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY ERR }
ata7.00: error: { ICRC ABRT }
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: soft resetting link
ata7.00: configured for UDMA/25
ata7.01: configured for UDMA/33
ata7.00: configured for UDMA/25
ata7.01: configured for UDMA/33
ata7: EH complete
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



That doesn't look like a fix to me. I expect the CF device run in PIO4.
Or shall I really ignore these?

Martin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


alan at lxorguk

May 6, 2008, 6:08 AM

Post #8 of 14 (4252 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

> ata7.00: ATA-0: Delock 54111 512MB, Ver1.27, max UDMA/33
> ata7.00: 1006992 sectors, multi 0: LBA

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


mmokrejs at ribosome

May 6, 2008, 7:54 AM

Post #9 of 14 (4160 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

Alan Cox wrote:
>> ata7.00: ATA-0: Delock 54111 512MB, Ver1.27, max UDMA/33
>> ata7.00: 1006992 sectors, multi 0: LBA
>
> 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)

# 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
#
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


alan at lxorguk

May 6, 2008, 8:04 AM

Post #10 of 14 (4164 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

>
> ATA device, with non-removable media
> Model Number: Delock 54111 512MB
> Serial Number:
> Firmware Revision: Ver1.27

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

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


mmokrejs at ribosome

May 6, 2008, 9:24 AM

Post #11 of 14 (4151 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

Alan Cox wrote:
> O> /dev/sde:
>> ATA device, with non-removable media
>> Model Number: Delock 54111 512MB
>> Serial Number:
>> Firmware Revision: Ver1.27
>
> Does seem to think its ATA not CFA I guess you'll need to specify pio for
> that device specifically.

Sorry for my ignorance ... How?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


alan at lxorguk

May 6, 2008, 12:04 PM

Post #12 of 14 (4170 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

On Tue, 06 May 2008 18:24:39 +0200
Martin MOKREJŠ <mmokrejs [at] ribosome> wrote:

> Alan Cox wrote:
> > O> /dev/sde:
> >> ATA device, with non-removable media
> >> Model Number: Delock 54111 512MB
> >> Serial Number:
> >> Firmware Revision: Ver1.27
> >
> > Does seem to think its ATA not CFA I guess you'll need to specify pio for
> > that device specifically.
>
> Sorry for my ignorance ... How?

On a current kernel (Tejun only recently added this)

libata.force= ...

see Documentation/kernel-parameters.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


mmokrejs at ribosome

May 6, 2008, 4:42 PM

Post #13 of 14 (4139 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

Alan Cox wrote:
> On Tue, 06 May 2008 18:24:39 +0200
> Martin MOKREJŠ <mmokrejs [at] ribosome> wrote:
>
>> Alan Cox wrote:
>>> O> /dev/sde:
>>>> ATA device, with non-removable media
>>>> Model Number: Delock 54111 512MB
>>>> Serial Number:
>>>> Firmware Revision: Ver1.27
>>> Does seem to think its ATA not CFA I guess you'll need to specify pio for
>>> that device specifically.
>> Sorry for my ignorance ... How?
>
> 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 [at] vger/msg15454.html).
Currently I can only use libata.dma=0.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


alan at lxorguk

May 7, 2008, 12:25 AM

Post #14 of 14 (4137 views)
Permalink
Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' [In reply to]

> 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.

For the moment yes.

> Subject: 2.6.25: pata_marvell/ahci/libata regression: ata7: SATA link down (SStatus 0 SControl 300)

I have absolutely no idea about the AHCI link down case although some
patches did go into the tree for a similar looking report.

> 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 [at] vger/msg15454.html).
> Currently I can only use libata.dma=0.

Correct.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Linux kernel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.