From owner-freebsd-stable@FreeBSD.ORG Sun Jul 24 04:30:20 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 5E6E216A420 for ; Sun, 24 Jul 2005 04:30:20 +0000 (GMT) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id E454B43D45 for ; Sun, 24 Jul 2005 04:30:19 +0000 (GMT) (envelope-from mike@sentex.net) Received: from pumice3.sentex.ca (pumice3.sentex.ca [64.7.153.26]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j6O4TkWE009721 for ; Sun, 24 Jul 2005 00:29:46 -0400 (EDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by pumice3.sentex.ca (8.13.3/8.13.3) with ESMTP id j6O4UIP7087403 for ; Sun, 24 Jul 2005 00:30:18 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3/8.13.3) with ESMTP id j6O4UHrt038445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 24 Jul 2005 00:30:17 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.1.2.0.20050724001440.06aac960@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Sun, 24 Jul 2005 00:32:31 -0400 To: freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20050721202234.GA62615@FS.denninger.net> References: <200507211803.j6LI34dV005050@ferens.net> <20050721194500.W9208@fledge.watson.org> <20050721192613.GA61902@FS.denninger.net> <6.2.1.2.0.20050721153750.0851fab0@64.7.153.2> <20050721202234.GA62615@FS.denninger.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 X-Scanned-By: MIMEDefang 2.51 on 64.7.153.26 Subject: Re: Quality of FreeBSD 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, 24 Jul 2005 04:30:20 -0000 At 04:22 PM 21/07/2005, Karl Denninger wrote: >ATA-NG (Soren's new code) is not (from what I understand) in the 5.x >codebase. No, but its quite different from what was in 4.x. >My understanding is that the 5.x code is a half-baked version of ATA-NG, >and IMHO it had no business going into a PRODUCTION release in the state >that it was pushed over. It works quite well for many people. It might be just half-baked for the controller you are using. Or perhaps the controller chipset is just half baked. Looks at some of the comments in the LINUX driver for example * After the IDENTIFY [PACKET] DEVICE step is complete, and a * device is known to be present, this function is called. * We apply two errata fixups which are specific to Silicon Image, * a Seagate and a Maxtor fixup. * * For certain Seagate devices, we must limit the maximum sectors * to under 8K. * * For certain Maxtor devices, we must not program the drive * beyond udma5. * * Both fixups are unfairly pessimistic. As soon as I get more * information on these errata, I will create a more exhaustive * list, and apply the fixups to only the specific * devices/hosts/firmwares that need it. * * 20040111 - Seagate drives affected by the Mod15Write bug are blacklisted * The Maxtor quirk is in the blacklist, but I'm keeping the original * pessimistic fix for the following reasons... * - There seems to be less info on it, only one device gleaned off the * Windows driver, maybe only one is affected. More info would be greatly * appreciated. >Given that we were all "strongly" encouraged to upgrade to 5.x for production >machines a few months ago it was a truly ugly surprise to find that current >production hardware which ran just fine on 4.x was hosed to the point of >unusability with 5.x as a consequence of serious (some would say CRITICAL) >driver issues. Why not stick with 4.x if it works for you. When you see that your particular device driver gets fixed then try it out on a test machine. It might never, it might next month. This is open source remember. If its very critical to use this particular bit of hardware, see if Soren has this hardware to even test on. You like the cards, why not send him one. He might be interested in fixing it when he has an actual card to test with. ---Mike