From owner-freebsd-stable Tue Nov 5 12:23:44 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 851DF37B401 for ; Tue, 5 Nov 2002 12:23:43 -0800 (PST) Received: from symbion.srrc.usda.gov (symbion.srrc.usda.gov [199.133.86.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7535F43E6E for ; Tue, 5 Nov 2002 12:23:42 -0800 (PST) (envelope-from gjohnson@srrc.ars.usda.gov) Received: from node1.cluster.srrc.usda.gov (localhost [127.0.0.1]) by symbion.srrc.usda.gov (8.12.6/8.12.6) with ESMTP id gA5KNfjI086265 for ; Tue, 5 Nov 2002 14:23:41 -0600 (CST) (envelope-from glenn@node1.cluster.srrc.usda.gov) Received: (from glenn@localhost) by node1.cluster.srrc.usda.gov (8.12.6/8.12.6/Submit) id gA5KNf94086264 for stable@FreeBSD.ORG; Tue, 5 Nov 2002 14:23:41 -0600 (CST) Date: Tue, 5 Nov 2002 14:23:41 -0600 From: Glenn Johnson To: stable@FreeBSD.ORG Subject: machdep.c problem [was Re: SMP broken on PPro] Message-ID: <20021105202341.GA86211@node1.cluster.srrc.usda.gov> References: <20021104230032.GA3217@node1.cluster.srrc.usda.gov> <20021105105146.GB57295@HAL9000.homeunix.com> <20021105201738.GA86056@node1.cluster.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021105201738.GA86056@node1.cluster.srrc.usda.gov> User-Agent: Mutt/1.5.1i 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 Tue, Nov 05, 2002 at 02:17:38PM -0600, Glenn Johnson wrote: > The problem on -STABLE is with /sys/i386/i386/machdep.c, revision > 1.385.2.26. I am not smart enough to know exactly what is wrong > with the diff but reverting back to revision 1.385.2.25 of > /sys/i386/i386/machdep.c fixes the problem. > > Apparently, the problem is BIOS specific so that explains why I only > saw it on one of my machines (the oldest) and not the others. This > would also explain why other people have not seen the problem. At > this point I would say that the problem really has nothing to do with > SMP, it just so happened that I experienced the problem on an SMP > machine. Should I file a PR on this, even though I do not know what the fix is? -- Glenn Johnson USDA, ARS, SRRC Phone: (504) 286-4252 New Orleans, LA 70124 e-mail: gjohnson@srrc.ars.usda.gov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message