From owner-freebsd-stable@FreeBSD.ORG Wed Jun 2 12:44:55 2004 Return-Path: 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 954BB16A4CE for ; Wed, 2 Jun 2004 12:44:55 -0700 (PDT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.252]) by mx1.FreeBSD.org (Postfix) with SMTP id 815BA43D5A for ; Wed, 2 Jun 2004 12:44:55 -0700 (PDT) (envelope-from scott.johnson@gmail.com) Received: by mproxy.gmail.com with SMTP id x43so8660cwb for ; Wed, 02 Jun 2004 12:44:55 -0700 (PDT) Received: by 10.11.122.66 with SMTP id u66mr506921cwc; Wed, 02 Jun 2004 12:44:55 -0700 (PDT) Message-ID: <3a74908904060212447504f567@mail.gmail.com> Date: Wed, 2 Jun 2004 14:44:55 -0500 From: Scott Johnson To: Ken Smith In-Reply-To: <20040602130608.GB17851@electra.cse.Buffalo.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <3a74908904060115436a22eef9@mail.gmail.com> <40BDCC33.3060906@web.de> <20040602130608.GB17851@electra.cse.Buffalo.EDU> cc: freebsd-stable@freebsd.org Subject: Re: panic on 4.10-STABLE boot w/SMP (same here) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 19:44:55 -0000 On Wed, 2 Jun 2004 09:06:08 -0400, Ken Smith wrote: > On Wed, Jun 02, 2004 at 02:46:43PM +0200, Kay Lehmann wrote: > > > I just wanted you to know that you are not alone. This happened to me, > > too. I get a similar error with a 4-stable-system from tonight. One > > difference is, that I have two 1600-MP's build in. > > 4.10-RELEASE worked fine for me, so it seems to be a real new problem. > > I just had it happen to me too... :-) > > Backing out to version 1.115.2.20 of src/sys/i386/i386/mp_machdep.c > seemed to take care of the problem, the machine booted with no other > changes needed. I have informed the person most likely to be able to > fix it. I'm running a build with version 1.115.2.22 right now. It looks like jhb submitted a fix for our problem. I'll send an update when my build is complete. -Scott