Sorry, for repeating this question - but I need to give it one more chance to get solved before I throw those SATA disks out. Sometimes (usually not that often) when accessing my SATA disks I get this: hda: dma_timer_expiry: dma status == 0x24 hda: DMA interrupt recovery hda: lost interrupt This timeout occurs after some 15 seconds of halted activity on the drive. I have had this problem since day 1. I have lived in hope that kerenl updates would catch this problem but now I am on 2.6.3 and the problem is still there. Can anyone give me a hint on what might be causing this? I mean, could it be hardware failure (cables?), lousy chipset (VIA VT8237), configuration errors, kernel bugs etc.? thanks for listening. __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com
On Fri, 5 Mar 2004 16:13:25 -0800 (PST)
Johan Backlund
Sorry, for repeating this question - but I need to give it one more chance to get solved before I throw those SATA disks out.
Sometimes (usually not that often) when accessing my SATA disks I get this:
hda: dma_timer_expiry: dma status == 0x24 hda: DMA interrupt recovery hda: lost interrupt
It sounds like you're not using the VIA libata driver, but the old IDE driver. Get the latest update kernel or the update boot CD from the ftp site, it has a special VIA SATA driver. One drawback is that the disk will be called /dev/sda* instead of /dev/hda* The old driver often happens to work with SATA, but does not really handle all cable specific SATA error conditions correctly. -Andi
--- Andi Kleen
It sounds like you're not using the VIA libata driver, but the old IDE driver. Get the latest update kernel or the update boot CD from the ftp site, it has a special VIA SATA driver. One drawback is that the disk will be called /dev/sda* instead of /dev/hda*
My hero! ;o) Seriously, I have been trying to get some kind of feedback on whether I should see the drives as IDE or SCSI (through the libata driver). I have not been able to find any enlightening information on this like HOW-TO or something. Since most examples I have seen on the net indicates that people running 2.4.x use libata and people on 2.6.x use IDE I thought that was the right setup. Anyways, I have been trying most (if not all) 2.6.x releases from SuSE and even did one or two tries with the standard kernel - and I have had no luck. The drives are always picked up as IDE. Can I force the drives to go through the libata driver in any way? Since I do have other IDE hardware in there, I cannot disable IDE completely. hmm, maybe I can just remove the VIA IDE driver? FYI, my hardware is: MSI KT8 Master2 (VIA K8T800), 2xWestern Digital Caviar 120GB. cheers __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com
participants (2)
-
Andi Kleen
-
Johan Backlund