From owner-freebsd-stable@FreeBSD.ORG Sat Jun 13 02:30:53 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68BE4106566C for ; Sat, 13 Jun 2009 02:30:53 +0000 (UTC) (envelope-from kstewart@owt.com) Received: from smtp.owt.com (smtp.owt.com [64.146.239.50]) by mx1.freebsd.org (Postfix) with ESMTP id 89D4F8FC13 for ; Sat, 13 Jun 2009 02:30:52 +0000 (UTC) (envelope-from kstewart@owt.com) Received: from kstewart2.owt.com (kstewart2.owt.com [64.146.237.228]) (authenticated bits=0) by smtp.owt.com (8.13.8/8.13.8) with ESMTP id n5D2GlKQ017668; Fri, 12 Jun 2009 19:16:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=owt.com; s=default; t=1244859407; bh=MJ1T1BlolYPwH5mfDnV+C5qBBx+nTQGePCNoMtcpCLk=; h=From:To:Subject:Date:Cc:References:In-Reply-To:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=iaGJm1sV5JicG Gs/FmDf6/ThYb9AOYatCp3PMkzE19NcXy7PvRBemImWMsjPXwi8Rgfl8vhucKBZ+Jf0 QqbkDjZyDEjUgzRxusEIedUWUPjRelIadaM1A3jkZRqPV0q8snCLlVNIjP5IGZyCCin d1EySCvUaCZ7Yz30Xq61uPCo= From: Kent Stewart To: freebsd-stable@freebsd.org Date: Fri, 12 Jun 2009 19:16:46 -0700 User-Agent: KMail/1.9.10 References: <212AA509-6A5D-4D43-8B02-A31E636A8D40@airwired.net> <3a142e750906111641w73d991a7ld22ff9a9150404e0@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906121916.46729.kstewart@owt.com> Cc: Dan Allen , "Paul B. Mahol" Subject: Re: Something since June 8th clobbers my disk... 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: Sat, 13 Jun 2009 02:30:54 -0000 On Thursday 11 June 2009 06:33:24 pm Dan Allen wrote: > On 11 Jun 2009, at 5:41 PM, Paul B. Mahol wrote: > > Looks like boot(8) is problematic. > > Anything in /etc/src.conf or /etc/make.conf? > > I have never touched or created a src.conf. If there was one there, > it has been unmodified by me. > > I HAVE modified make.conf. Here is its contents: > > --- /etc/make.conf --- > > BATCH=yes > NO_PROFILE=yes > KERNCONF=DKA > USE_FORTRAN=yes > WITH_JADETEX=no > PERL_VERSION=5.8.9 > > --- > > My custom kernel named DKA has only three modifications from GENERIC: > > I commented out the following three lines: > > #cpu I486_CPU > #cpu I586_CPU > #makeoptions DEBUG="-g" > > I have run with such a kernel on many machines for many years now. > > However, my experiments have shown that the kernel build is not to > blame. > > Isn't boot part of the kernel build? Why would installing the kernel > not cause this problem? > > It is by installing the world via make installworld that my drive gets > munged. > > I obviously am missing something, but boot(8) sounds like it is in the > neighborhood of where the problem is. > > There were changes to /usr/src/sys/boot/i386/libi386/biosdisk.c and > biospnp.c that really look suspect to me. The order of your builds in previous messages had the kernel built on an old world. You are supposed to do the buildworld first and then, build and install the kernel. The classic way at this point is to boot into single user mode and do the installworld. Kent > > Dan > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html