From owner-freebsd-stable@FreeBSD.ORG Thu Jan 19 23:44:59 2012 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 84FF2106566C; Thu, 19 Jan 2012 23:44:59 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173]) by mx1.freebsd.org (Postfix) with ESMTP id 514808FC0A; Thu, 19 Jan 2012 23:44:59 +0000 (UTC) Received: from [127.0.0.1] (proxy7.corp.yahoo.com [216.145.48.98]) by mrout3.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q0JNYGsR022503; Thu, 19 Jan 2012 15:34:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1327016056; bh=hXaVWLWwpGfHk7RpIKGHiJ371R+j3T+XA7pObZAxZGI=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=gDbjjoEfWz+8wOAaWZpTrYXZk/zTA6DjndOdBVXtJE89YVaz1NxSj1lXHDIPTnWwD o1mXllkcu954Z1VndUSpVsNWw85UdJgjyxkC6/41+jerjqgkywrbFR42r0pJa0SjUU rANI9O+Wq2rOwPY7dzv+xHpWhF1UEaqRFCN8Tw8M= From: Sean Bruno To: Dwayne MacKinnon In-Reply-To: <201201191706.46553.dmk@ncf.ca> References: <201201191706.46553.dmk@ncf.ca> Content-Type: text/plain; charset="UTF-8" Date: Thu, 19 Jan 2012 15:34:15 -0800 Message-ID: <1327016055.5907.4.camel@powernoodle-l7> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-stable@freebsd.org" Subject: Re: Odd reboot problems with 9.0-RELEASE i386 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: Thu, 19 Jan 2012 23:44:59 -0000 On Thu, 2012-01-19 at 14:06 -0800, Dwayne MacKinnon wrote: > Hi all, > > I recently upgraded my 8.2-RELEASE box to 9.0-RELEASE using the old-fashioned > cvsup way. I've run into a really strange situation. > > Everything went smoothly with the upgrade. I then deleted all my installed > ports and started reinstalling. I noticed the problem when trying to compile > openjdk6. > > The box would spontaneously reboot. All the time. > > So, I put the following into /etc/rc.conf. I'll repost here, it's entirely > possible I did something wrong: > > dumpdev="/dev/ada0s1b" # Device to crashdump to (device name, AUTO, or > NO). > dumpdir="/usr/crash/" # Directory where crash dumps are to be stored > > I made sure /usr/crash was created and had permissions wide open. Yet, I never > got any crash dumps (I recreated the reboot several times over.) > > I tried compiling a GENERIC kernel; that failed as well. So I got the DVD iso, > and copied over the /boot/kernel directory from it. > > Once I did that, i was able to compile a new GENERIC kernel no problem. (I > need to take out the pcn driver; I need le and pcn jumps it.) > > With the slightly-modified GENERIC kernel, the problem has disappeared. I've > compiled openjdk no problem. I tried recompiling my custom kernel and > reinstalled it; the problem reappeared. > > I've attached my kernel config file; there's nothing revolutionary about it. > It's almost identical to the one I used for 8.2-RELEASE, but based on the new > 9.0 GENERIC. Maybe someone here will find it useful. > > A cc would be appreciated as I don't follow -stable. > > Cheers, > DMK This sounds suspciously like a bug the ports team found on the the 9 RC series. I can't recall where it got fixed, but I'm pretty sure it did *not* make it to the release. You may have better luck with stable/9 instead of 9.0-RELEASE if you can do that. Sean