Date: 24 Apr 2005 16:38:06 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Cezar Fistik <cezar@arax.md> Cc: freebsd-questions@freebsd.org Subject: Re: Re[4]: WRITE_DMA problem again Message-ID: <44is2bzz9t.fsf@be-well.ilk.org> In-Reply-To: <843420889.20050424021338@arax.md> References: <1212701106.20050421194847@arax.md> <193906655.20050421220412@wanadoo.fr> <966265278.20050422121620@arax.md> <86ba954f05042210506af5395b@mail.gmail.com> <843420889.20050424021338@arax.md>
next in thread | previous in thread | raw e-mail | index | archive | help
Cezar Fistik <cezar@arax.md> writes: > Hello Kendall, > > Friday, April 22, 2005, 8:50:42 PM, you wrote: > > > Anyhow, my understanding is that the current work-around to this > > problem is to turn DMA off for your ata drives. I guess this can be > > done manually with the atacontrol command as I've been doing (though > > as you'll see in my message linked above, I apparently need to do it > > differently/sooner). I also understand that you can do so by setting > > hw.ata.ata_dma="0" in /boot/loader.conf . > > Yes, I saw this suggestion in other posts, too. Well, I gave it a try. > I disabled dma yesterday and today I got the following: > > Timecounter "TSC" frequency 498669235 Hz quality 800 > ad0: 8693MB <IBM-DJNA-370910/J74OA30K> [17662/16/63] at ata0-master PIO4 > ad0: TIMEOUT - WRITE_MUL retrying (2 retries left) LBA=1573151 > ad0: FAILURE - WRITE_MUL timed out > > That's something completely new. Does anyone know what that means? Like the symptoms you got with DMA enabled, it *probably* means you have *some* kind of hardware problem. The cable would be a likely candidate, but I'd definitely be making extra backups if I were you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44is2bzz9t.fsf>