From owner-freebsd-current@FreeBSD.ORG Tue Sep 27 09:10:46 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7DD916A41F for ; Tue, 27 Sep 2005 09:10:46 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from fep17.inet.fi (fep17.inet.fi [194.251.242.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAFD643D53 for ; Tue, 27 Sep 2005 09:10:45 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from [192.168.0.20] ([84.249.3.49]) by fep17.inet.fi with ESMTP id <20050927091044.RSJN10515.fep17.inet.fi@[192.168.0.20]>; Tue, 27 Sep 2005 12:10:44 +0300 Message-ID: <43390C99.3070006@pp.nic.fi> Date: Tue, 27 Sep 2005 12:10:49 +0300 From: Pertti Kosunen User-Agent: Mozilla Thunderbird 1.0.2 / FreeBSD 6.0-BETA5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eriksson References: <4F9C9299A10AE74E89EA580D14AA10A605F552@royal64.emp.zapto.org> In-Reply-To: <4F9C9299A10AE74E89EA580D14AA10A605F552@royal64.emp.zapto.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , =?ISO-8859-1?Q?S=F8ren?=, =?ISO-8859-1?Q?_Schmidt?= Subject: Re: "TIMEOUT - READ_DMA48 retrying" has suddenly started appearing (RELENG_6) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2005 09:10:47 -0000 Daniel Eriksson wrote: > I'm running RELENG_6 on two machines, one SMP and one UP (both using SCHED_4BSD). I cvsup/update the OS a few times a week, and after an update on Saturday (24/9) I've seen multiple "TIMEOUT - READ_DMA48 retrying" errors on both machines, causing all sorts of trouble (broken arrays, panics, ...). After a reboot the disks have come back to life and seem to work just fine. > > It could just be a coincidence and multiple disks on two separate machines have started to go bad, but since the disks are different models on different ATA/SATA controllers in different machines it could also be an indication that something has happened with FBSD. If it's a FBSD problem then the "offending" code was added some time between Monday 19/9 and Saturday 24/9. > > Is anyone else experiencing similar problems? I have had same problems with >UDMA100 since 5.3-RELEASE, UDMA66 works perfectly. Machine boots ok with higher modes, but some disk load triggers the timeouts. Problems just revisited after upgrade to 6.0-BETA5 because atacontrol mode syntax changed. cat /etc/rc.local #!/bin/sh atacontrol mode ad0 UDMA66 atacontrol mode ad4 UDMA66 atacontrol mode ad5 UDMA66 atacontrol mode ad6 UDMA66