Re: hdb: dma_timer_expiry: dma status == 0x64 [2.5.69]

From: Zephaniah E. Hull (warp@mercury.d2dc.net)
Date: Wed May 14 2003 - 08:47:04 EST


On Tue, May 13, 2003 at 09:48:13PM +0200, Maciej Soltysiak wrote:
> Hi,
>
> on 2.5.69-dj1 (so it's a 2.5.69-bk5 kernel) i found these two in my kernel
> log, which i have not seen before. There are just 2 occurences of that.
> Is that something about a hardware failure, or something else?

The first reaction is that this is a hardware thing.

EXCEPT.

I'm seeing it too, only with recent kernels.

May 14 07:43:43 agamemnon kernel: hda: dma_timer_expiry: dma status == 0x64
May 14 07:43:43 agamemnon kernel: hda: lost interrupt
May 14 07:43:43 agamemnon kernel: hda: dma_intr: bad DMA status (dma_stat=70)
May 14 07:43:43 agamemnon kernel: hda: dma_intr: status=0x50 { DriveReady SeekComplete }

Happens only with heavy disk IO, running 2.5.69-mm3, happened with a few
earlier kernels and sadly I don't remember which kernel it started on.

-- 
	1024D/E65A7801 Zephaniah E. Hull <warp@babylon.d2dc.net>
	   92ED 94E4 B1E6 3624 226D  5727 4453 008B E65A 7801
	    CCs of replies from mailing lists are requested.

<Electro> LordHavoc: i got black lines on stuff in realtime mode, i'll take a pic, and it runs slow <LordHavoc> this is why I LOVE ATI drivers, they're so creative with the geometry I give them... <LordHavoc> they turn a refined and very specific standard for the pixel by pixel handling of polygons into an interpretive artform


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



This archive was generated by hypermail 2b29 : Thu May 15 2003 - 22:00:51 EST