From owner-freebsd-ports@FreeBSD.ORG Mon Jan 17 23:39:16 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6ED5C16A4CE for ; Mon, 17 Jan 2005 23:39:16 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CEE843D54 for ; Mon, 17 Jan 2005 23:39:16 +0000 (GMT) (envelope-from inbox@kelleycows.com) Received: from [127.0.0.1] (c-24-30-114-40.we.client2.attbi.com[24.30.114.40]) by comcast.net (sccrmhc12) with ESMTP id <20050117233910012000or32e>; Mon, 17 Jan 2005 23:39:11 +0000 Message-ID: <41EC4CA7.4060609@kelleycows.com> Date: Mon, 17 Jan 2005 15:39:19 -0800 From: Christopher & Rachel Kelley User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <41EC2ED8.70400@kelleycows.com> <20050117225837.GB31708@xor.obsecurity.org> In-Reply-To: <20050117225837.GB31708@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-ports@freebsd.org Subject: Re: portsdb -U causes reboot with custom kernel, but not GENERIC X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 23:39:16 -0000 Kris Kennaway wrote: >On Mon, Jan 17, 2005 at 01:32:08PM -0800, Christopher & Rachel Kelley wrote: > > >>Using 4.11-RC2, or 4.11-STABLE portsdb -U works, ONLY if I use the >>GENERIC kernel. If I build the world & kernel and install (doing the >>appropriate mergemaster steps in single user) with my kernel >>configurarion, it reboots in the middle. >> >> > >This usually means bad hardware. portsdb -U exercises the disk very >hard if it's building an INDEX yourself, so it can provoke failures >from marginal hardware. > >Kris > > I had thought maybe flaky hardware was an issue, but then I can't understand why it would reliably work okay with a GENERIC kernel, and reliably fail with a custom kernel. Is there something in GENERIC that I unknowingly removed that lessens the load on the system? Is there a "good" way to test my system? I've run memtest86 on it with no problems, and since this is one of my hobby systems, I'm not adverse to a test that would wipe my FreeBSD installation. I was planning on wiping and reinstalling for 4.11-RELEASE anyways. Christopher