From owner-freebsd-stable@FreeBSD.ORG Wed Jul 7 10:03:23 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8040F16A4CE for ; Wed, 7 Jul 2004 10:03:23 +0000 (GMT) Received: from hartley.mintel.co.uk (hartley.mintel.com [213.206.147.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93B2043D2F for ; Wed, 7 Jul 2004 10:03:22 +0000 (GMT) (envelope-from jason.thomson@mintel.com) Received: from [10.0.62.5] ([10.0.62.5])i67A2epb057777; Wed, 7 Jul 2004 11:02:40 +0100 (BST) (envelope-from jason.thomson@mintel.com) Message-ID: <40EBCA3F.2080404@mintel.com> Date: Wed, 07 Jul 2004 11:02:39 +0100 From: Jason Thomson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Charles Sprickman References: <40CD80F1.6020107@mintel.com> <20040706192152.D6269@shell.inch.com> <20040706183439.R24627@carver.gumbysoft.com> <20040707013959.GB1441@electra.cse.Buffalo.EDU> <20040706215914.K6269@shell.inch.com> In-Reply-To: <20040706215914.K6269@shell.inch.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) cc: freebsd-stable@freebsd.org cc: Ken Smith Subject: Re: 3ware 7506, FreeBSD 4.x, Maxtor Disks & SMART Problems. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2004 10:03:23 -0000 Charles Sprickman wrote: > On Tue, 6 Jul 2004, Ken Smith wrote: > > >>On Tue, Jul 06, 2004 at 06:35:27PM -0700, Doug White wrote: >> >> >>>There was a nasty bug just about as 4.10 went out the door with the twe >>>driver. I thought the fix went into the release, though. If you get a >>>chance you might try moving up to the -stable version of src/sys/dev/twe >>>and see if that fixes your issues in 4.10. >> >>It was actually the first thing we did as an Errata Notice. If you >>normally track the Security Fix branches you can use the same mechanism >>(cvsup to RELENG_4_10 in this case) to get the twe fix. See: >> >>ftp://ftp.freebsd.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-04:01.twe.asc > > > Excellent, next time I'm onsite I'll give it a try (the box is remote, and > last time it locked up hard). > > Thanks, > > Charles > > >>for the Errata Notice. The original patch (early May) didn't fix it for us... However, I have just updated and checked the sources again, and there were further changes after the patch that I applied. We still have two machines that exhibit this behaviour from time to time - I'll update them and see if that fixes it. If it doesn't, I will be able to get crashdumps. (We've also got SCSI disks in the machines in question). Thanks for the additional info. BTW on one occasion, we fixed the *symptoms* of our problem by repairing a disk that had bad sectors. (This didn't show up in error messages from the twe driver - only when we scanned the disk using Maxtor's PowerMax tools. After remapping the sector and rebuilding the array - the problem disappeared).