From owner-freebsd-stable@FreeBSD.ORG Sun Jul 24 18:13:00 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 783D716A41F for ; Sun, 24 Jul 2005 18:13:00 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id E773B43D48 for ; Sun, 24 Jul 2005 18:12:59 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.3/8.13.1) with SMTP id j6OICxnQ062068 for ; Sun, 24 Jul 2005 13:12:59 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Sun Jul 24 13:12:59 2005 Received: (from karl@localhost) by FS.denninger.net (8.13.3/8.13.1/Submit) id j6OICxLW062066 for freebsd-stable@freebsd.org; Sun, 24 Jul 2005 13:12:59 -0500 (CDT) (envelope-from karl) Date: Sun, 24 Jul 2005 13:12:59 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20050724181259.GA62041@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20050722001253.GA70277@FS.denninger.net> <20050722013605.U16902@fledge.watson.org> <20050722010611.GA72234@FS.denninger.net> <42E0F93E.7000108@commit.it> <20050722194009.GA95692@FS.denninger.net> <20050723214450.A61837@fledge.watson.org> <20050724020136.GA16783@FS.denninger.net> <20050724034334.GA90851@falcon.midgard.homeip.net> <20050724040055.GA18138@FS.denninger.net> <20050724175820.GA7735@falcon.midgard.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050724175820.GA7735@falcon.midgard.homeip.net> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: make -j as a stress test (was: Re: Quality of FreeBSD) [WARNING - 6.0-BETA1 still hosed!] 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 18:13:00 -0000 On Sun, Jul 24, 2005 at 07:58:20PM +0200, Erik Trulsson wrote: > On Sat, Jul 23, 2005 at 11:00:55PM -0500, Karl Denninger wrote: >> Should not there be an EXPLICIT note in the release notes for hardware that >> this chipset WILL NOT WORK PROPERLY? > > It does seem to work for many users, or there would be much complaints about > it on the mailing lists. There are more than a couple - how many people can't even BOOT? We've heard a few of those too..... For single-disk machines under light load, it appears to work - most of the time. > > Or perhaps better, the solution is to put the fix from 1.50 into ATA-NG, > > eh (and recommend for performance reasons to use something else in the > > release notes....) > > > > Finally, this begs an obvious further question - since my original PR was > > opened in February of this year, if there is a KNOWN incompatability with > > this chipset, why is the PR still open, rather than a response being > > posted back ("hardware unsupported") AND the driver flags/init for that > > chipset being either removed or a STRONG warning printed when it is > > identified on boot? > > > > That DOES appear to be the right choice, assuming the fixes that sos > > committed back in '03 can't be rolled forward into ATA-NG..... If they > > CAN, then how about it? I mean, c'mon - this change was all of three > > lines of code added, and one removed! > > As I said: You are already running with those fixes - and they apparently > don't fix your problems. > > Most likely the bug you have run into is difficult or impossible to > reproduce on other hardware than the particular combination you are using. Considering that I've had zero attempts at communication with me regarding the PR, except for one "me too" posted to it, and there has also been no note posted to the PR by any of the developers (e.g. "unable to reproduce"), an equally-likely scenario is that there has been no effort made to reproduce (and fix) it..... -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://homecuda.com Emerald Coast: Buy / sell homes, cars, boats! http://genesis3.blogspot.com Musings Of A Sentient Mind