DMA timeout error

DMA timeout error

[Adam Sherman]

I have a VIA M6000 board with an ATA CompactFlash adaptor containing a
512MB SanDisk card.

I get the following error during boot:

hdb: dma_timer_expiry: dma status == 0x41
hdb: DMA timeout error
hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }

hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }

hdb: drive not ready for command
hdb: dma_timer_expiry: dma status == 0x41
hdb: DMA timeout error
hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }

hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }

hdb: drive not ready for command


Any ideas?

Thanks,

A.

Re: DMA timeout error

[Bartlomiej Zolnierkiewicz]

On Fri, 01 Oct 2004 14:56:42 -0400, Adam Sherman <adam@sherman.ca> wrote:
> I have a VIA M6000 board with an ATA CompactFlash adaptor containing a
> 512MB SanDisk card.
> 
> I get the following error during boot:
> 
> hdb: dma_timer_expiry: dma status == 0x41
> hdb: DMA timeout error
> hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
> 
> hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> 
> hdb: drive not ready for command
> hdb: dma_timer_expiry: dma status == 0x41
> hdb: DMA timeout error
> hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
> 
> hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> 
> hdb: drive not ready for command
> 
> Any ideas?

If this is a new CF capable of DMA but CF-to-IDE adapter doesn't support
DMA (most don't) then "ide=nodma" kernel command line parameter should
do the job.  It might be also bug in via82cxxx host driver.

Maybe DMA should be off by default for CF but it requires fixing almost
every IDE host driver and why punish good hardware.

Re: DMA timeout error

[Adam Sherman]

Bartlomiej Zolnierkiewicz wrote:
>>I have a VIA M6000 board with an ATA CompactFlash adaptor containing a
>>512MB SanDisk card.
>>
>>I get the following error during boot:
>>
>>hdb: dma_timer_expiry: dma status == 0x41
>>hdb: DMA timeout error
>>hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
> 
> 
> If this is a new CF capable of DMA but CF-to-IDE adapter doesn't support
> DMA (most don't) then "ide=nodma" kernel command line parameter should
> do the job.  It might be also bug in via82cxxx host driver.
> 
> Maybe DMA should be off by default for CF but it requires fixing almost
> every IDE host driver and why punish good hardware.

This makes quite a bit of sense seeing as it's a SanDisk "Ultra II" card.

beber@setibzh.com writes:
> add pci=noapic to your boot option

Since the hardware is not reachable from here, I can not test it until 
Monday. I'll note my results though.

Thanks,

A.

Re: DMA timeout error

[Beber]

add pci=noapic to your boot option
;)

Adam Sherman wrote:

> I have a VIA M6000 board with an ATA CompactFlash adaptor containing a
> 512MB SanDisk card.
>
> I get the following error during boot:
>
> hdb: dma_timer_expiry: dma status == 0x41
> hdb: DMA timeout error
> hdb: dma timeout error: status=0x58 { DriveReady SeekComplete 
> DataRequest }
>
> hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
>
> hdb: drive not ready for command
> hdb: dma_timer_expiry: dma status == 0x41
> hdb: DMA timeout error
> hdb: dma timeout error: status=0x58 { DriveReady SeekComplete 
> DataRequest }
>
> hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
>
> hdb: drive not ready for command
>
>
> Any ideas?
>
> Thanks,
>
> A.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

-- 
/* Beber : beber (AT) setibzh (DOT) com
* https://guybrush.ath.cx
* Using Mozilla Thunderbird on Gentoo Linux
* Rachel @ friends.paris
*/

DMA timeout error

[Pisch Tamás]

Hello,

I have four SATA disks, which I use in a RAID5 array. One
disk falls out from the RAID,
very often always with DMA timeout error. Always the same
disk, but I can recover the
RAID, so the disk isn't bad. I have a very similar server
configuration , and the
situation is similar to that. I think, maybe the falling out
disks have a little worse
physical parameters. I want to set them to a slower mode
than UDMA/133 (for example
UDMA/66), maybe it helps to prevent it from the error. My
question is: how can I do
that? I will modify the source code of the driver, if you
tell me, what I have to modify.
If you have a better idea about the solution, please let me
know. I use Debian Sarge.
I tried out both the built-in 2.4.27 and 2.6.8 kernels. I
tried out a lot of things, if
you need details, please ask me.
Thank you, in advance.

Best regards,

Tamás Pisch.



____________________________________________________________________________
Ingyenes hirdetés feladás az [origo] aprón!  Már több mint 180.000 ajánlat!
http://apro.origo.hu/