From owner-freebsd-current@FreeBSD.ORG Thu Aug 9 19:34:59 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 97AF416A417 for ; Thu, 9 Aug 2007 19:34:59 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.freebsd.org (Postfix) with ESMTP id 483F013C458 for ; Thu, 9 Aug 2007 19:34:58 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from zaphod.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 9EE751E8C1A; Thu, 9 Aug 2007 19:34:57 +0000 (UTC) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 7F86E1145C; Thu, 9 Aug 2007 21:34:57 +0200 (CEST) Date: Thu, 9 Aug 2007 21:34:57 +0200 From: "Simon L. Nielsen" To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Message-ID: <20070809193456.GE1124@zaphod.nitro.dk> References: <86r6mcpmcp.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86r6mcpmcp.fsf@ds4.des.no> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: alc@freebsd.org, freebsd-current@freebsd.org, "Karsten W. Schmidt / DLX ApS" Subject: Re: 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: Thu, 09 Aug 2007 19:34:59 -0000 On 2007.08.09 20:57:26 +0200, Dag-Erling Smørgrav wrote: > "Karsten W. Schmidt / DLX ApS" writes: > > [the usual problems with ZFS vs. Promise controllers, then] > > > > And with a bit of trial-and-error I found that the following is the one > > causing these errors. > > > > > > http://lists.freebsd.org/pipermail/cvs-src/2007-June/079930.html > > > > A kernel made before this gives no errors, and a kernel make right after > > this gives the errors. > > I'm not sure this is the root cause. If you search the -current > archives, you'll find that several people (including myself) were seeing > this already in April. Nevertheless, I've Cc:ed Alan, who might have an > idea. 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). [simon@eddie:system-CURRENT] dmesg | grep -E '^(ata|ad)' | grep -v '\[ITHREAD\]' atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 8.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xc880-0xc8ff,0xc400-0xc4ff mem 0xff4fe000-0xff4fefff,0xff4a0000-0xff4bffff irq 18 at device 4.0 on pci1 ata2: on atapci1 ata3: on atapci1 ata4: on atapci1 ata5: on atapci1 atapci2: port 0xcf00-0xcf3f,0xcfa0-0xcfaf,0xc800-0xc87f mem 0xff4fc000-0xff4fcfff,0xff480000-0xff49ffff irq 19 at device 8.0 on pci1 ata6: on atapci2 ata7: on atapci2 ata8: on atapci2 ad4: 305245MB at ata2-master SATA150 ad6: 305245MB at ata3-master SATA150 ad10: 305245MB at ata5-master SATA150 ad12: 35304MB at ata6-master SATA150 ad14: 35304MB at ata7-master SATA150 -- Simon L. Nielsen