From owner-freebsd-current@FreeBSD.ORG Thu May 8 22:34:06 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D2A937B401 for ; Thu, 8 May 2003 22:34:06 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8F9643F93 for ; Thu, 8 May 2003 22:34:05 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0410.cvx40-bradley.dialup.earthlink.net ([216.244.43.155] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19E0W9-0004PH-00; Thu, 08 May 2003 22:34:03 -0700 Message-ID: <3EBB3275.CB107353@mindspring.com> Date: Thu, 08 May 2003 21:45:41 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Heiko Schaefer References: <20030508142234.GA1359@laptop.6bone.nl> <3908.1052404777@critter.freebsd.dk> <20030508172630.C79286@daneel.foundation.hs> <20030508174923.F79286@daneel.foundation.hs> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4c6f9c79303f2aa09ee3623d4a957c3a03ca473d225a0f487350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: data corruption with current (maybe sis chipset related?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 09 May 2003 05:34:06 -0000 Heiko Schaefer wrote: > > Terry mentioned that he explained it to Bosco, and that he had a patch to > > work around it in a different way. But that was from November, time has > > passed since then. > > a nice workaround would be great, of course. assuming terry knows what > he's doing, i'm sure such code would be preferrable to turning on these > options by default. but until then, turning them on sounds like the safest > bet to me. i'd sacrifice some speed for reliability anyday. and so far i > felt that freebsd always had that philosophy. It's Bosko's workaround. I have a binary patch with two .o's (machdep.o and locore.o) that I've given a couple of people who agreed not to disassemble it which contains a fix based on my understanding of the problem; it worked for them. Being binary, it's not really appropriate to -current any more. Bosko's is preferred, because it doesn't disclose the nature of the bug, so it's OK to pass around as source code. -- Terry