On Thu, 8 May 2003, David Ford wrote:
> hda: dma_timer_expiry: dma status == 0x24
> drivers/ide/ide-io.c:108: spin_lock(drivers/ide/ide.c:c04fb648) already
> locked by drivers/ide/ide-io.c/948
> drivers/ide/ide-io.c:990: spin_unlock(drivers/ide/ide.c:c04fb648) not locked
> hda: lost interrupt
> hda: dma_intr: bad DMA status (dma_stat=30)
> hda: dma_intr: status=0x50 { DriveReady SeekComplete }
>
> hda: dma_timer_expiry: dma status == 0x24
> drivers/ide/ide-io.c:108: spin_lock(drivers/ide/ide.c:c04fb648) already
> locked by drivers/ide/ide-io.c/948
> drivers/ide/ide-io.c:990: spin_unlock(drivers/ide/ide.c:c04fb648) not locked
> hda: lost interrupt
> hda: dma_intr: bad DMA status (dma_stat=30)
> hda: dma_intr: status=0x50 { DriveReady SeekComplete }
known problem, patch sent to alan some time ago(may be i should
resync/resend?) for this dma_timer_expiry have several problems:
calls DRIVER(drive)->error - the one above, it's called with lock from
ide_timer_expiry
calls ide_dma_end - the reason for called while not waiting messages,
it's called again in ide_timer_expiry
there is one more locking problem known to me - HDIO_DRIVE_RESET,
but can not find out how to fix it properly.
-- have fun, alex- 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/