From owner-freebsd-current@FreeBSD.ORG Mon Aug 13 05:03:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42AAE16A417 for ; Mon, 13 Aug 2007 05:03:35 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id 1754F13C469 for ; Mon, 13 Aug 2007 05:03:34 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1IKS5V-0000Gu-K1 for ; Mon, 13 Aug 2007 14:03:33 +0900 Message-ID: <46BFE620.8070906@fusiongol.com> Date: Mon, 13 Aug 2007 14:03:28 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL X-Abuse-Complaints: abuse@gol.com Subject: Promise SATA 300 TX4 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: Mon, 13 Aug 2007 05:03:35 -0000 >I tried to roll back to right before the above mentioned change >Karsten (well, I assume it was him :-) ) noted on IRC that it might >be the cause of the problems since I have a similar controller, though >not exactly the same one, but it didn't fix the timeouts for me. >For this server I have 3 disks in a graid3 (so no ZFS but the errors >are similar to what I have seen / heard about wrt. ZFS + ata use) and >I get timeouts several times a day which causes FreeBSD to loose >contact with one or more disks where I have to reboot before things >recover (usually FreeBSD panic's enough so the system reboots by >itself). I'm certain that the issue with this card isn't limited to ZFS. It's been seen before in the 6.x series too. I really would like to find out which code changes ruined the card's correct operation... if that could help the ata maintainer in some way. Unfortunately my csup-fu isn't that strong, otherwise I would send my source tree back to June 15th and analyse daily buildworlds from that date until I could pin-point the exact date and file changes that caused the problem all of us are seeing. Could someone teach me how to do csup rollbacks to a specific date in the source tree? If it's not obvious already, I'd really like to squash this bug.