From owner-freebsd-questions@FreeBSD.ORG Wed Mar 28 15:47:38 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 57EBF16A400 for ; Wed, 28 Mar 2007 15:47:38 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.freebsd.org (Postfix) with ESMTP id 3195213C45E for ; Wed, 28 Mar 2007 15:47:38 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from hymn05.u.washington.edu (hymn05.u.washington.edu [140.142.12.184]) by mxout3.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l2SFlb74025478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 28 Mar 2007 08:47:37 -0700 Received: from localhost (localhost [127.0.0.1]) by hymn05.u.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l2SFlbsm012606 for ; Wed, 28 Mar 2007 08:47:37 -0700 X-Auth-Received: from [192.55.52.4] by hymn05.u.washington.edu via HTTP; Wed, 28 Mar 2007 08:47:37 PDT Date: Wed, 28 Mar 2007 08:47:37 -0700 (PDT) From: youshi10@u.washington.edu To: freebsd-questions@freebsd.org In-Reply-To: <447it12z00.fsf@be-well.ilk.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PMX-Version: 5.3.0.289146, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2007.3.28.83636 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SUPERLONG_LINE 0.05, NO_REAL_NAME 0, __CP_MEDIA_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: Re: Problems with SMP on 6.1-STABLE-200608 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2007 15:47:38 -0000 On Wed, 28 Mar 2007, Lowell Gilbert wrote: > "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. Honestly I would probe around your motherboard a bit checking voltages (power supply) and/or heat dissipation, because those are the most likely cases if it _only_ fails under high load. Next thing to check would be RAM integrity. -Garrett