From owner-freebsd-stable@FreeBSD.ORG Sun Jan 27 06:24:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E36C16A419; Sun, 27 Jan 2008 06:24:02 +0000 (UTC) (envelope-from joe@skyrush.com) Received: from shadow.wildlava.net (shadow.wildlava.net [67.40.138.81]) by mx1.freebsd.org (Postfix) with ESMTP id 3C6C513C455; Sun, 27 Jan 2008 06:24:02 +0000 (UTC) (envelope-from joe@skyrush.com) Received: from [10.1.2.160] (pawnee.wildlava.net [67.40.138.85]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shadow.wildlava.net (Postfix) with ESMTP id 53D888F435; Sat, 26 Jan 2008 23:24:01 -0700 (MST) Message-ID: <479C233B.3000708@skyrush.com> Date: Sat, 26 Jan 2008 23:22:51 -0700 From: Joe Peterson User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Jeremy Chadwick References: <479BAC09.7040505@freebsd.se> <20080126223750.GA8397@marshal.spacemarines.us> <479BC21D.10607@skyrush.com> <20080127035814.GB91290@eos.sc1.parodius.com> In-Reply-To: <20080127035814.GB91290@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Remco van Bekkum , Nikolaj Farrell , freebsd-stable@freebsd.org Subject: Re: ad8: TIMEOUT - WRITE_DMA errors UFS 7.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2008 06:24:02 -0000 Jeremy Chadwick wrote: >> If this is widespread, I think the chances re slim that it is a >> hardware problem in every case. > > I'm in definite agreement here. I think it might be worthwhile to note > what hardware we're all using, in case there's something similar between > our systems (chipset, disk vendor, etc.). > > My system is as follows; timeouts were reported during an rsync of data > from the ZFS stripe (ad8+ad10) to a UFS2 filesystem on ad6. System > eventually panic'd after remaining deadlocked (while kernel messages > about timeouts kept printing on the console for ad6 only) for 10-15 > minutes. > > * MB: Supermicro PDSMI+ (Intel ICH7-based) > * CPU: Intel Core 2 Duo E6600 > * RAM: Corsair CM2X1024-6400 DDR2, 2GB > * ad4: WD Caviar SE WD2000JD (boot/OS) > * ad6: Seagate Barracuda 7200.10 ST3500630AS > * ad8: WD Caviar SE16 WD5000AAKS (ZFS stripe) > * ad10: WD Caviar SE16 WD5000AAKS (ZFS stripe) > * All drives are hooked up to the ICH7. > * SMART stats showed no problems on any of the drives before or after. > * RELENG_7, i386, ULE scheduler. Mine is as follows: * MB: Tyan Trinity S2099 * CPU: Pentium 4, 2.4GHz * RAM: Crucial DDR, ECC, CL2.5, Unbuffered 2GB (1/2 PC2100, 1/2 PC2700) * ad0: Seagate ST3500630A 3.AAE (1 UFS2 boot, 1 ZFS pool) * ad1: Seagate ST3160812A 3.AAH (not used by FreeBSD) * Intel ICH4 UDMA100 controller * ATI Radeon RV280 9250 * Intel PRO/1000 NIC * 7.0-RC1, i386, ULE scheduler -Joe