Re: dma error on boot with cf card

[Lennart Sorensen]

On Tue, Feb 05, 2008 at 06:52:29PM +0100, Marc Donner wrote:
> hi,
> 
> i have a problem using a cf card with an ide adapter. 
> using debian kernel 2.6.18-5 
> 
> on boot:
> Feb  5 17:38:06 kernel: hdd: max request size: 128KiB
> Feb  5 17:38:06 kernel: hdd: 2000880 sectors (1024 MB) w/2KiB Cache, 
> CHS=1985/16/63, UDMA(33)
> Feb  5 17:38:06 kernel:  hdd:<4>hdd: dma_timer_expiry: dma status == 0x41
> Feb  5 17:38:06 kernel: hdd: DMA timeout error
> Feb  5 17:38:06 kernel: hdd: dma timeout error: status=0x58 { DriveReady 
> SeekComplete DataRequest }
> Feb  5 17:38:06 kernel: ide: failed opcode was: unknown
> Feb  5 17:38:06 kernel: hdd: irq timeout: status=0xd0 { Busy }
> Feb  5 17:38:06 kernel: ide: failed opcode was: unknown
> Feb  5 17:38:06 kernel: ide1: reset timed-out, status=0xff
> Feb  5 17:38:06 kernel: hdd: status timeout: status=0xff { Busy }
> Feb  5 17:38:06 kernel: ide: failed opcode was: unknown
> Feb  5 17:38:06 kernel: hdd: drive not ready for command
> Feb  5 17:38:06 kernel: ide1: reset timed-out, status=0xff
> Feb  5 17:38:06 kernel: end_request: I/O error, dev hdd, sector 0
> Feb  5 17:38:06 kernel: Buffer I/O error on device hdd, logical block 0
> Feb  5 17:38:06 kernel: end_request: I/O error, dev hdd, sector 0
> Feb  5 17:38:06 kernel: Buffer I/O error on device hdd, logical block 0
> Feb  5 17:38:06 kernel:  unable to read partition table
> Feb  5 17:38:06 kernel: end_request: I/O error, dev hdd, sector 2000640
> Feb  5 17:38:06 kernel: Buffer I/O error on device hdd, logical block 250080
> Feb  5 17:38:06 kernel: end_request: I/O error, dev hdd, sector 2000640

Adapter doesn't support DMA, but controller and CF cards do.  To fix,
tell the system NOT to use dma on that interface.

Most IDE to CF adapters fail to connect the DMA pins correctly since it
was a fairly (3 or 4 years ago) revision to the CF spec to support DMA
at all.

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