READ_DMA interrupt was seen but timeout fired

[Derrick Ryalls]

Greetings list.


Today, I found this entry in my daily security mailings:

> ad4: WARNING - READ_DMA interrupt was seen but timeout fired LBA=169679214
> ad4: WARNING - READ_DMA interrupt was seen but timeout fired LBA=192145262
> ad4: WARNING - READ_DMA interrupt was seen but timeout fired LBA=207110586
> ad4: WARNING - READ_DMA interrupt was seen but timeout fired LBA=207488666
> ad4: WARNING - READ_DMA interrupt was seen but timeout fired LBA=236563382
> ad4: WARNING - READ_DMA interrupt was seen but timeout fired LBA=221053142
> ad4: WARNING - READ_DMA interrupt was seen but timeout fired LBA=222542714
> ad4: WARNING - READ_DMA interrupt was seen but timeout fired LBA=224089322

Doing a google search mentioned people seeing this with laptops coming
back from suspend mode.  The machine in question is my desktop running
5.3-STABLE FreeBSD 5.3-STABLE #0 and the hard drive is a 120gig SATA. 
My kernel is GENERIC + sound.

I haven't seen any other issues, no system slowdowns or anything, and
thus far I haven't seen anything on my Windows partition either.

The drive is just over 1 year old, could it be dying already?

Any suggestions would be appreciated.

-Derrick