Date: Wed, 26 Mar 2008 07:19:47 +0100 From: Gianni <gdoe6545@yahoo.it> To: Jeremy Chadwick <koitsu@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: ad0 READ_DMA TIMEOUT errors on install of 7.0-RELEASE Message-ID: <6BADAEBA-09F7-4348-ABA4-F78A4EDF2185@yahoo.it> In-Reply-To: <20080325084455.GA36520@eos.sc1.parodius.com> References: <EEA261A2-96D4-4FAB-8213-A5FD2F6233CF@yahoo.it> <20080322035212.GA15541@eos.sc1.parodius.com> <248F8C92-14F4-4FF8-94FE-2F220FFBE8FB@yahoo.it> <20080325084330.GA36390@eos.sc1.parodius.com> <20080325084455.GA36520@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25/mar/08, at 09:44, Jeremy Chadwick wrote: > > I re-read your mail -- sorry. You're using SATA. > > I'll update my Wiki page to state that the loader.conf DMA disable > trick > only works for PATA. > > In the interim, I recommend you contact Scott Long, especially if your > problem is easily repeatable. He's offered to help track this down. Thanks I'll try contacting Scott. In the meantime I think I have narrowed down the problem in my case to the on-board Promise SATA controller. My motherboard has 2 SATA controllers, one Promise and one Via and I have 2 sets of disks with gmirror RAID 1 - 2xSeagate Barracuda + 2xWD5000YS. atapci0: <Promise PDC20378 SATA150 controller> atapci1: <VIA 6420 SATA150 controller> The Western Digital disks were connected to the Promise controller and giving the READ_DMA TIMEOUT errors, I've now swapped the disks around so the Seagate ones are attached to the Promise controller and now these are reporting the errors. So it seems I can definitely exclude disk hardware problems. -Gianni
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6BADAEBA-09F7-4348-ABA4-F78A4EDF2185>