Date: Fri, 28 Jan 2005 15:03:06 +0100 From: "Norbert Koch" <NKoch@demig.de> To: "Matthias F. Brandstetter" <haimat@lame.at>, <freebsd-questions@freebsd.org> Subject: RE: READ_DMA timed out on Promise FastTrak100 Message-ID: <000001c50542$1755b340$4801a8c0@ws-ew-3.W2KDEMIG> In-Reply-To: <200501281357.39992.haimat@lame.at>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Ursprüngliche Nachricht----- > Von: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org]Im Auftrag von Matthias F. > Brandstetter > Gesendet am: Freitag, 28. Januar 2005 13:58 > An: freebsd-questions@freebsd.org > Betreff: Re: READ_DMA timed out on Promise FastTrak100 > > ---------- quoting list@mindling.com ---------- > > However, when I boot FreeBSD, the system reports READ_DMA errors on the > > second drive, and the array reports a degraded state. I can still mount > > it, and both drive lights flash when accessing the volume. > > I had similar problems with my SATA RAID controller, lots of DMA errors. > Looks like a bug in 5.3 -- or is it fixed now? > > I solved this issue in disabling DMA via sysctl... I am using a Promise FastTrak100 and I have no problems at all. I tried FreeBSD5.3 Release and the most current RELENG_5. So, no kernel bug, as far as I can tell. Norbert Koch
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000001c50542$1755b340$4801a8c0>