From owner-freebsd-stable Fri Nov 8 20:10:48 2002 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 002D937B401 for ; Fri, 8 Nov 2002 20:10:46 -0800 (PST) Received: from greg.cex.ca (h24-207-26-100.dlt.dccnet.com [24.207.26.100]) by mx1.FreeBSD.org (Postfix) with SMTP id 48F3743E77 for ; Fri, 8 Nov 2002 20:10:41 -0800 (PST) (envelope-from gregw-freebsd-stable@greg.cex.ca) Received: (qmail 32606 invoked by uid 1001); 9 Nov 2002 04:10:59 -0000 Date: Fri, 8 Nov 2002 20:10:59 -0800 From: Greg White To: freebsd-stable@freebsd.org Subject: Re: SMP -STABLE kernel broken between Sunday and today? Message-ID: <20021108201059.A32588@greg.cex.ca> Mail-Followup-To: freebsd-stable@freebsd.org References: <20021108233236.M12539-100000@hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021108233236.M12539-100000@hub.org>; from scrappy@hub.org on Fri, Nov 08, 2002 at 11:38:44PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri Nov 11/08/02, 2002 at 11:38:44PM -0400, Marc G. Fournier wrote: > > This evening, in response to a crash of one of my servers, I did an CVSUP > of the -STABLE code and installed a new kernel ... upon rebooting, it > 'hung' at the point that of: > > SMP: AP CPU #1 Launched! > > according to the techs @ rackspace ... my previous kernel on that machine > worked fine (from Oct 12th), so something has changed ... but, I was just > thinking about it, and my machine at the office is running an SMP kernel > as well, as her last upgrade was based on sources from Sunday, November > 3rd ... Search the archives of this list, and thou shalt find that machdep.c has been broken for some hardware configurations for a few days now. Mostly, from the reports (and my own experience) it seems to be PPros that are affected. Go back to a rev 1.385.2.25 or older, and likely your problem will go away. Either that, or just run the old kernel until someone MFCs the correct fix. :) -- Greg White To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message