Date: Thu, 13 Apr 2006 18:03:51 -0000 From: Martin Tournoy <carpetsmoker@gmail.com> To: "Anish Mistry" <mistry.7@osu.edu>, freebsd-questions@freebsd.org Subject: Re: DMA TIMEOUT Message-ID: <op.s7ykgpmeipwu61@carpetsmoker.ictwerkplaats.org> In-Reply-To: <200604131154.07097.mistry.7@osu.edu> References: <NGBBKBOMKLFOJCCDHPEOOEAIAAAB.freebsd@hyperconx.com> <200604131154.07097.mistry.7@osu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Apr 2006 15:53:57 -0000, Anish Mistry <mistry.7@osu.edu> wrote: > On Thursday 13 April 2006 07:47, Wil Hatfield wrote: >> > I had a similar situation under 6.0. My secondary drive would >> > throw DMA read >> > errors at bootup, adding several minutes to the boot process, so >> > I ran it in >> > PIO mode. The upgrade to 6.1 solved it, both drives work fine as >> > DMA now. >> >> Looks like the DMA errors are back in 6.1-RC with ATA or at least >> similar DMA errors. The new one froze my machine with an error like >> "Error while performing DMA_WRITE command". A new twist to the >> WRITE_DMA Timeouts of 5.4. I am starting to think that they aren't >> going to get the ATA issues all worked out anytime soon so they are >> changing the errors. ;-) >> >> And of course no automatic reboot on panic. > Do you have a backtrace? > Did you use a 80- or 40-ATA cable? If you've configured your drives to do UATA-66 or faster then FreeBSD (or any other OS for that matter) will crash if you connect a second drive...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.s7ykgpmeipwu61>