From owner-freebsd-questions@FreeBSD.ORG Wed Mar 28 15:01:37 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ACCAE16A405 for ; Wed, 28 Mar 2007 15:01:37 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.7]) by mx1.freebsd.org (Postfix) with ESMTP id 88CD713C4C8 for ; Wed, 28 Mar 2007 15:01:37 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 23677 invoked from network); 28 Mar 2007 15:01:37 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 28 Mar 2007 15:01:36 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id AB2D828431; Wed, 28 Mar 2007 11:01:35 -0400 (EDT) To: "Don O'Neil" References: <001a01c76fe1$95bd89e0$0400020a@mickey> From: Lowell Gilbert Date: Wed, 28 Mar 2007 11:01:35 -0400 In-Reply-To: <001a01c76fe1$95bd89e0$0400020a@mickey> (Don O'Neil's message of "Mon\, 26 Mar 2007 13\:01\:47 -0700") Message-ID: <447it12z00.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.93 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Problems with SMP on 6.1-STABLE-200608 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2007 15:01:37 -0000 "Don O'Neil" writes: > I've been having problems with my server freezing up, having the #2 CPU > 'shut down', kernel panics, and all sorts of nastyness.... > > Originally I thought it was exim, or possibly bind, or bad hardware (mb, cpu > or memory)... I've swapped out the motherboard & CPU's & memory from an old > server that was running 4.11 ROCK SOLID for years... > > At first I thought the problem was solved, but now it's popping up again... > The 2nd CPU gets 'shut down', or kernel panics, esentially taking the system > offline. There are lots of things this could be, and I certainly wouldn't rule out hardware problems (power supply?). Figuring out the problems directly would certainly involve looking at more details than you're listing here. > If I install a single CPU (non-smp) kernel, then the system works fine... (I > did this on the old motherboard before I swapped it out, and it worked fine > too).. So I'm wondering if there is an SMP bug or problem I'm running into. > > I'm running 6.1-STABLE-200608, an ISO image I downloaded from the archives > when I built the box (NOT 6.1-RELEASE). The whole point of making releases is that it's much easier to support a small number of known reference software configurations. > I'm runining an Intel Serverworks motherboard with 2 1.4 GHz PIII's... The > problem only seems to show up under high load. I don't think I've heard of anything similar. I think there are a bunch of these boards out there. > I'm wondering what I should do here... > > I'm concerned about doing a binary upgrade to 6.2 won't fix the problem, and > I've tried using freebsd-update, but it complains about the version not > being compatible. > > If I do a binary upgrade from CD, will it also update the kernel sources so > I can build a new one? Will it complain about it not being compatible? It can give you the sources; that's a menu option during the install. That should work fine. > Is there a way to 'force' the ID of the system to be 6.1-RELEASE so that > freebsd-update will work? Well, yes, but there's a reason for the check, you know... > Will doing the 6.1-6.2 binary upgrade as posted by Colin also update the > kernel sources? I don't know what procedure he described, so I don't know. But if you update to 6.2-RELEASE, then it will be easy to get the right sources afterwards. Again, that is the advantage of having releases. > Would my best option really be to start over with a fresh install rather > than upgrade? (this would be painful) If it's that painful, you'd probably be well served to have a spare system to stage changes on. In addition to being good risk management, it saves you time, which is worth something too. > I'm going to try to test out 6.2 on the old MB/CPU combo to see if I can > re-create it under 6.2 as well before I do anything. As well as try doing an > upgrade on the bench from CD from 6.1-STABLE-200608 to 6.2-RELEASE... Since > this is a production server (and for months it was burned in with no > apparent issues) I only have 1 shot at this to do it right. > > Any help/recomendation would be appreciated. Good luck.